[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reading NI TDMS files

From: Sergei Steshenko
Subject: Re: Reading NI TDMS files
Date: Thu, 20 Dec 2007 00:44:56 -0800 (PST)

--- David Bateman <address@hidden> wrote:

> Michael Goffioul wrote:
> > On 12/19/07, John W. Eaton <address@hidden> wrote:
> >> OK, I think you are misunderstanding my statement above.  I'm talking
> >> about a case where distribution does happen.  Whether the parts are
> >> distributed together or separately, the result is the same (they are
> >> distributed, and linked together, so the GPL does not permit it).
> >>
> >> But I think I see what the misunderstanding may be.  It seems that you
> >> are thinking of the case of the METIS library, and whether it is OK
> >> for you to link that with your copy of Octave in the privacy of your
> >> own organization.  I'm thinking of a case where someone writes a
> >> plug-in for Octave, specifically with the intent of linking to a
> >> proprietary module, that they would not be allowed to distribute if it
> >> were all (Octave, the plug-in, and the proprietary code) linked
> >> together, but they try to get around this by distributing them
> >> separately and expecting that the user link them together in the end.
> > 
> > I - personally - find this unfortunate as it indeed limits the area of
> > applications for octave. More specifically, it prevents anybody to
> > bridge octave with any GPL-incompatible software
> > (at least in the most efficient way, using oct-files). The first example
> > that comes to my mind (although I'm not an expert at all in that
> > area) is bridging octave with instrumentation softwares like LabView,
> > which are usually proprietary. But if the GPL is written like that,
> > just let it be...
> > 
> > I'm just happy that Sun released Java under GPL, otherwise my java
> > package would be a clear violation of the GPL license.
> > 
> > Moreover, shouldn't the packages located in the "nonfree" directory
> > of octave-forge be removed?
> > 
> > Michael.
> Use a mex-file, then you can say it was for matlab and still link
> against Octave (tongue in cheek).. Seriously, I think the fact that we
> can use mex-files in Octave makes all of this argument moot..
> D.
> _______________________________________________
> Help-octave mailing list
> address@hidden

Let me generalize your point.

There is an interface, like the one of mex files or of TDMS files.

There is a piece of software which knows to talk through the interface.

There are users who free to do whatever they want in the privacy of their
homes/offices as long as they do not redistribute the software against
the terms of the software license.


Applications From Scratch:

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]