octave-maintainers
[Top][All Lists]
Advanced

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

Re: Avoid global pointers in dae


From: Carlo De Falco
Subject: Re: Avoid global pointers in dae
Date: Sun, 14 Aug 2016 00:14:57 +0000

On 14 Aug 2016, at 02:11, Carlo de Falco <address@hidden> wrote:

> 
> On 14 Aug 2016, at 01:17, Carnë Draug <address@hidden> wrote:
> 
>> On 13 August 2016 at 06:30, Francesco Faccio
>> <address@hidden> wrote:
>>> [...]
>>> Since I don't own copiright, I would like to know if it's ok to change the
>>> interface of that base class.
>>> 
>> 
>> The ability to change the code is one of the main points behind GPL.
>> So yes, you can change the source.
>> 
>> Just beware that if the interface is public you should try to keep
>> backwards compatibility.  I grepped all of the Octave Forge for DAEFunc
>> and all of its subclasses [1] but couldn't find it being used so you
>> should be fine.
>> 
>> Carnë
>> 
>> [1] http://octave.org/doxygen/4.1/d9/d83/classDAEFunc.html
> 
> Francesco,
> 
> As Carnë's answer shows, your question is ill posed and leads to 
> misunderstandings:
> 
> of course you can change the source, the GPL license grants you this right,
> the real question would be whether that change would be accepted by Octave
> developers in the main repository or not.

To make this more clear, who holds copyright is pointless and referring to that
in your question is distracting.

The question is a technical question about the class design and functionality, 
not 
a legal question about licenses and copyright.

> c.




reply via email to

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