Darren New wrote:

> somebody wrote:
>> GPL neither protects, nor restricts the rights of anyone using any other
>> license.
> 
> It does so by preventing you from using a different license. The GPL
> prevents you from linking code with a different license to GPLed code. The
> MIT license doesn't.
> 
> If you can't see that, then I'm not sure what the problem is.
> 
>> Maybe so, but that's irrelevant. The author can pick any license that he
>> wants.
> 
> Unless he's authoring a plug-in for GCC.

You can make a BSD-licensed plug-in for GCC, but the combination of both
when run would be GPL.

Why does it even matter then?

Because a commercial company can take a single function (that doesn't
interact with gcc) from the BSD plugin and use it on its closed-source
program.

Post a reply to this message