RE: [PHP-DEV] readline extension status?

JM>> have the byte code in, as was previously stated) then we would JM>> be forced the separated the code from the PHP codebase and JM>> distribute it under GPL or some compatible licience and enable JM>> compiling as a shared module as default (there by not GPL code JM>> is in PHP) this is not to say we need to disable static JM>> compiling but that must be up to the end user to abuse the JM>> licience (Maybe somthing for PEAR??). I don't see how separating offending code and GPLing it would help. Then we have another piece of GPL code which cannot be used with PHP. Though, we might double-license offending pieces of code, maybe that would solve it? -- Stanislav Malyshev, Zend Products Engineer stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115