[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: Re: calling octave from C
From: |
ustaudinger |
Subject: |
AW: Re: calling octave from C |
Date: |
Thu, 19 Nov 2009 20:26:06 +0100 |
Am in the train, therefore top posting ...
in reply to ur question, it is neither for .m nor perl files forbidden to
distribute them as closed source when they do not include or directly reference
GPL software. If these files provide some logic on their own they can be
distributed via a different license.
However, as far as i understand, any pytave script has to use pytave libraries
in its code, which then means that ur code directly calls these specific
functions, which means further that ur program needs these libraries and then
of course that u need to distribute (when u want to) ur code via gpl.
Fact is that pytave is written in python as well and can be seen as a library
that ur python/pytave scripts use.
In any case, the question is propably better directed to the fsf indeed.
Kind regards,
Ulrich
-- Urspr. Mitt. --
Betreff: Re: calling octave from C
Von: Judd Storrs <address@hidden>
Datum: 19.11.2009 18:56
On Thu, Nov 19, 2009 at 5:48 AM, Jaroslav Hajek <address@hidden> wrote:
> Still, David's position is probably in agreement with FSF's:
> http://www.gnu.org/licenses/gpl-faq.html#IfInterpreterIsGPL
>
> so if this is of real interest to you, I'd suggest you ask the FSF
How can forbidding non-GPL python files be justified while
simultaneously allowing use of non-GPL m-files? How does the GPL
choose to favor one interpreted language over another?
--judd
_______________________________________________
Help-octave mailing list
address@hidden
https://www-old.cae.wisc.edu/mailman/listinfo/help-octave
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- AW: Re: calling octave from C,
ustaudinger <=