> Suggest we comment out the file and see what happens.
>
> To prevent having to modify all the Makefile/VS files,
> I'd recommend we just change the file to be a one line comment
> that says '// Removed due to non-LGPL/static license. See
> STR# . Original in svn r.'
>
On 07/20/11 02:11, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> Pretty sure the others would have no impact.
>
> I think adding new methods is OK. (But see above!)
> Does it change the size of the class though?
No changes in size, just adding code.
Changing the return value
On 07/20/11 03:14, Albrecht Schlosser wrote:
> On 20.07.2011 10:04, MacArthur, Ian (SELEX GALILEO, UK) wrote:
> Agreed, but then we might have to maintain "dead" code, and given the
> "complexity" of all that #if HAVE_something stuff, i'd like to remove
> it for all times...
Suggest we comment
On 20.07.2011 11:11, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>
> These sound like useful additions to me...
>
>> A few questions:
>>
>> a) Does (1) break the ABI (by changing the return value
>> from void to int)?
>
> I think it does, but I am usually wrong about ABI stuff..
Yes, I'm pretty
On 20.07.2011 10:04, MacArthur, Ian (SELEX GALILEO, UK) wrote:
>> My concern (as a commercial developer that releases
>> static builds) is not whether the code is used,
>> but that it's in the lib at all.
...
>> Still though, it should be "fixed", by which
>> I mean eith
Manolo,
Have you seen this post over in fltk.opengl?
http://www.fltk.org/newsgroups.php?gfltk.opengl+v:1461
This looks like something you might understand better than I do!
SELEX Galileo Ltd
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company re
These sound like useful additions to me...
> A few questions:
>
>a) Does (1) break the ABI (by changing the return value
> from void to int)?
I think it does, but I am usually wrong about ABI stuff..
> Pretty sure the others would have no impact.
I think adding new methods is OK.
> My concern (as a commercial developer that releases
> static builds) is not whether the code is used,
> but that it's in the lib at all.
>
> True: if the code is not called, it shouldn't
> appear in the linked executables by optimization.
> And legally I ima
