> If a third party is willing to violate the GPL, the presence of a > plug-in infrastructure will _not_ make their job significantly easier.
The issue isn't the ease in which it violates the GPL, but the ease in which you can show it *is* a violation! If there's no plug-in and you link directly with GCC, there's no question that such code is covered by the GPL. If you use a plug-in, there *is* such a question and people might well believe it is *not* a GPL violation. > It is very easy for us to make code developed using plug-ins to be > covered by the GPL. They will be using GCC header files, after all. I don't want to turn this into a legal discussion, but there is some legal ambiguity about that statement too.
