AM>> Keeping this in sync will might be a pain. We're currently syncing
AM>> the NetBSD stuff (mainly by christos), over to OpenBSD as well (as well
AM>> as submitting back our security patches to it).
Not sure about this. Currently modifications from NetBSD CVS to
PHP-compatible code include different makefile (for obvious reasons), one
library function that is NetBSD-specific so has to be re-implemented (in
some 4 lines of code) and 3-4 lines of changes to include other
non-necessary NetBSD-specific ones. So in most cases "cvs update" would
keep us in sync :)
AM>> Would it be better if this were spun off as a separate library
AM>> release (perhaps synced to/from NetBSD versions, but with distinct
AM>> versions), as desire for the separate lib grows?
Separate lib would require seriously more work, because we need to make it
"works for all", not just "works for PHP". It can be done in stages,
though. Problem here is that full-blown library requires proper configure,
installation, etc. - for which I'd probably need help in some way. Making
in-tree solution is much simpler - though I do recognize that full-scale
library would be better.
AM>> Yeah, there is a loss of functionality. Some readline programs
AM>> that use v4.x simply dont compile due to the functions not being there
AM>> (yafc), but christos says that he is gunning for full readline compat,
AM>> which should be excellent.
There's now some 4-5 variables and at least one function that is in
readline and used by PHP, but is not in libedit. For now, we can ifdef
around it, and wait when Coding Guys catch up.
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
