|
From: | David Bateman |
Subject: | Re: Further on MEX |
Date: | Tue, 06 Jan 2009 23:18:20 +0100 |
User-agent: | Mozilla-Thunderbird 2.0.0.17 (X11/20081018) |
Aravindh Krishnamoorthy wrote:
From Octave's point of view accepting that the Octave MEX ABI doesn't invoke the GPL, might be considered as weakening the protection of Octave under the GPL.There are certainly risks in accepting a MEX like ABI for Octave that doesn't fall under the GPL, though it would expose any of liboctave or liboctinterp. However I believe it would be a selling point for Octave in certain circumstancesWould you please explain the risk in the point above?
For the developer of a proprietary MEX file, can they be sure that a previous developer of Octave might consider that the MEX ABI exclusion might be illegitimate and take independent action against the MEX file developer.
Frankly, the moment we included the MEX API in the core of Octave itself and set the precedence that the MEX API effectively didn't invoke the GPL, at that point there was good grounds for protection of any proprietary distribution of MEX files for use with Octave.
D. -- David Bateman address@hidden 35 rue Gambetta +33 1 46 04 02 18 (Home) 92100 Boulogne-Billancourt FRANCE +33 6 72 01 06 33 (Mob)
[Prev in Thread] | Current Thread | [Next in Thread] |