Re: readline extension status?

You can't force someone not to make something that's compatible with your software - it's outside the scope of the software license. #include is nothing, unless it's actually compiled against and linked with GPL'd code. Behind this same #include there could be a BSD readline clone. Zeev At 15:30 28/12/2000, Stanislav Malyshev wrote:

KK>> Writing the code is usually not the problem, but linking againt KK>> it can be according to the GNU party line, if I understand that KK>> properly. You'd not be able to distribute any precompiled KK>> modules or PHP binaries with such code. Since LGPL explicitly notices allowing _linking_ to protected libraries as one of it's main goals, I guess GPL explicily prohibits making non-GPL programs that are compatible with GPL libraries - under "derived work" clause (You use headers, right? So it's derived work). I remember RMS writing about it somewhere, but don't recall the URL. Somewhere under "Philosophy" part of gnu.org (unfortunately, I can't reach www.gnu.org now, so I can look for the URL later). Yes, it seems too harsh, but as RMS said once, "GPL is not a Mr. Nice Guy". -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115 -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net

-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/