Re: Big blow to proprietary linking nonsense.

[7]

RJack the stupid 1 wrote:

>> 
>>> The following decision probably settles most questions touching
>>> upon copyright law and dynamically linking to open source code and
>>> vice versa. Simply placing a hook in GPL source code to call
>>> independent proprietary drivers or libraries is fully protected by
>>> 17 USC sec. 117. Simply dynamically calling GPL code doesn't
>>> involve copyright questions at all.
>> 
>> Nope.
>> 
>> 'Simply placing a hook' is no different to saying embedding
>> irrespective of how that embedding was achieved.
>> 
>> Once proprietary code is embedded into GPL'd code the whole product
>> now has two incompatible licenses. And you may be violating both
>> licenses.
>> 
>> As for the embedded GPL, you can use it for your own private use
>> under the terms of the GPL. But you can't distribute it if it
>> violates the GPL. You can distribute after you remove the GPL'd code
>> and/or substitute it with your own code, or remove the embedded
>> proprietary code, or re-license the proprietary code with one that is
>> compatible with the GPL license.
>> 
> 
> Placing (embedding) a "jmp" or "call" instruction to code


blearghhh! Technicalities.


> residing in a
> seperate place in memory is trivial requiring only a few bytes and does
> not change the creative aspects of a program since it is a purely
> functional and utilitarian addition. Purely functional aspects of
> a computer program are not protected by copyright due to the dichotomy
> of expression and function.
> 
> Sincerely,
> RJack :)


If only you were even close oh stupid 1.

You should consult a software engineer about the numerous methods of
embedding before handing out judicial reviews on public usenet.