> However - if you want to sell software under a closed licence you will > need to be carefull to avoid 'linking' with gpl'd code. > The problem is that 'linking' as used in the gpl seems to refer to C > programming - and is an unclear term when refering to php.
Yeah...that's really what I'm wondering. If I have my own code, but make function calls and the like to script libraries licensed under the GPL, does it mean my code will have to be GPL'd as well? It's not dynamically linking binary code in. I've read the GPL faq and it's very vague here. It considers interpreted programs "data", but doesn't consider cases the that "data" is licensed under the GPL. Say, for instance, that I use a GPL'd library that provides a class called myGPLClass. If I create instances of myGPLClass in my own scripts, does that make my code in violation of the GPL? Damn, I need a law degree ;-). John -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
