Darren New <dne### [at] sanrrcom> wrote:
> somebody wrote:
> > 2) Don't release code which is based on or interfacing with GPL'ed code.
>
> How come I can write code that interfaces with Linux without violating the
> GPL, but I can't write a plug-in for GCC without violating the GPL?

You're beginning to run into contradictions there.  Weren't you the one saying
the GPL doesn't enforce this behaviour?  That the measures taken are exactly
because the GPL alone would allow for closed plugins?

Other than that, you're right.  I believe gcc developers see plugins in the same
light as dynamic libs:  app + libs form a larger work and if one of the
components is GPL, the other should follow or not use it at all.

Post a reply to this message