nemesis wrote:
> Darren New <dne### [at] sanrrcom> wrote:
>> Let's look at a couple of scenarios:
> 
> You're an evil man. ;)

Another couple of thoughts, on the way in which having plug-ins tied to GCC 
output seems strange...

For one: I can hire you to write a plug-in for me, never distribute the 
plug-in, but distribute executable code produced by the plug-in. I can't, 
however, find that you've already anticipated my need, created a proprietary 
plug-in, buy it from you, and distribute the executable output. I actually 
have to hire you *before* you write the plug-in to do that.

For two: I could write a plug-in that does source transformations of various 
kinds, write my source code using that plug-in, compile it, distribute the 
executables *and* source but not the plug-in. I'd be complying with all the 
terms of the licenses, but you'd still not be able to compile the code and 
come up with the executable.

Both of these are predicated on the fact that I can GPL my code and still 
never distribute it if I don't want to. I'm pretty sure that works out.

-- 
   Darren New, San Diego CA, USA (PST)
   "Ouch ouch ouch!"
   "What's wrong? Noodles too hot?"
   "No, I have Chopstick Tunnel Syndrome."

Post a reply to this message