Derick Rethans wrote:
On Wed, 7 Apr 2004, Adam Dickmeiss wrote:
Worth considering. That means taking it out from php-src as well, I suppose.
Yes
Should documentation move away from phpdoc also?
No :)
regards,
Derick
I intent to move it, when time permits. After Easter
Wez Furlong wrote:
I'd like to merge ext/yaz source (not config.m4) from HEAD to PHP4
branch (which I assume would be in 4.3.6, when out). That's bad carma,
right?
Unless it fixes some critical major bad bugs, no, you're not allowed
to merge from HEAD.
FWIW, the YAZ API in PHP5 is
I'd like to merge ext/yaz source (not config.m4) from HEAD to PHP4
branch (which I assume would be in 4.3.6, when out). That's bad carma,
right?
FWIW, the YAZ API in PHP5 is completely backwards compatible with that
of PHP4. I have now for more than a year built separate Debian packages
for
Christian Stocker wrote:
Just as an update to this question
According to Adam, the stream-wrapper support in ext/xsl seems to have
the same possibilities as the schemes support in the former sablotron
extension. But he will further look into it and keep us/me updated
about the outcome ;)
Hi,
we miss the scheme facility from PHP4's XSLT extension. So, we are
making a new one for PHP5's XSL extension, i.e. interfacing libXSLT's
xsltRegisterExtModuleFunction. If nobody else have done it/is doing it
we'd like to contribute.
-- Adam
--
PHP Internals - PHP Runtime Development
Christian Stocker wrote:
On 10/31/03 11:23 AM, Adam Dickmeiss wrote:
Hi,
we miss the scheme facility from PHP4's XSLT extension. So, we are
making a new one for PHP5's XSL extension, i.e. interfacing libXSLT's
xsltRegisterExtModuleFunction. If nobody else have done it/is doing
it we'd like
Andi Gutmans wrote:
[snip]
This issue is definitely not a reason to stop rolling out RC's nor betas.
Enabling the XML extensions by default is the right decision because
this is an important technology which almost every PHP user will need.
I do think it's a good idea though to have a --disable
We're using the XSLT Sablotron in PHP4 in production. I cannot find the
XSLT in latest CVS, but I see that ext/xsl appeared some time ago. Does
this mean that Sablotron XSLT is dead in PHP5?
One extremly useful feature we used in Salotron PHP/XSLT was the ability
to register scheme handlers.
.
--with-libxml-dir could be moved to acinclude.m4 as well. It
is a global thing tied to the m4 macro PHP_SETUP_LIBXML.
-- Adam
Adam Dickmeiss mailto:[EMAIL PROTECTED] http://www.indexdata.dk
Index Data T: +45 33410100 Mob.: 212 212 66
--
PHP Internals - PHP Runtime Development Mailing
before the beta. What do
people think?
-Sterling
--
Good judgement comes from experience, and experience comes from
bad judgement.
- Fred Brooks
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
Adam Dickmeiss
Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
--
Adam Dickmeiss mailto:[EMAIL PROTECTED] http://www.indexdata.dk
Index Data T: +45 33410100 Mob.: 212 212 66
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
libxml:)
-- Adam
Andi
At 04:22 PM 26/6/2003 +0300, Zeev Suraski wrote:
At 16:09 26/06/2003, Adam Dickmeiss wrote:
On Thu, Jun 26, 2003 at 03:53:09PM +0300, Zeev Suraski wrote:
FWIW, that's one of the key reasons I think we should default to use the
bundled libxml, and only use the system
Latest PHP5, ext/config.m4, checks for 1.0.18 of later. But the
PHP_ARG_WITH and AC_MSG_ERROR says 1.0.3 is needed.
-- Adam
--
Adam Dickmeiss mailto:[EMAIL PROTECTED] http://www.indexdata.dk
Index Data T: +45 33410100 Mob.: 212 212 66
--
PHP Internals - PHP Runtime
On Wed, May 28, 2003 at 03:15:32PM +0200, Per Lundberg wrote:
On Wed, 2003-05-28 at 14:52, Adam Dickmeiss wrote:
cannot find the OO PHP script. Did you attach it?
Sorry. I'm obviously doing too many things at one time. Here it is,
attached to this email.
I see the almost same error
14 matches
Mail list logo
