Fixed in CVS. (just noticed that I could have just merged the
config.m4 back from head rather than re-investigating it, oh well.)
--Wez.
On 8/28/05, Wez Furlong <[EMAIL PROTECTED]> wrote:
> Thanks for checking; I'm working on a fix now.
>
> --Wez.
>
> On 8/26/05, Mike Robinson <[EMAIL PROTECTE
On Sun, 2005-08-28 at 16:23 +0200, Steph wrote:
> 'Replace'? Code written for ext/xmlrpc won't work with ext/xmlrpci. Will
> ext/xmlrpc be available in PECL, given that it doesn't appear to have an
> active maintainer?
Sure it'll be in PECL, just like dio, crack, yaz, and the other half
dozen or
Thanks for checking; I'm working on a fix now.
--Wez.
On 8/26/05, Mike Robinson <[EMAIL PROTECTED]> wrote:
> On my woody box, configure finished fine but with...
>
> Generating files
> updating cache ./config.cache
> creating ./config.status
> creating php5.spec
> creating main/build-defs.h
> cr
I've got a compile failure (FREETYPE_MAJOR and _MINOR undeclared) on
OS X with a config that works with 5.0.4 - should I report it here or
in bugs?
Marcus
--
Marcus Bointon
Synchromedia Limited: Putting you in the picture
[EMAIL PROTECTED] | http://www.synchromedia.co.uk
--
PHP Internals - P
At 16:23 28.08.2005, you wrote:
'Replace'? Code written for ext/xmlrpc won't work with ext/xmlrpci. Will
ext/xmlrpc be available in PECL, given that it doesn't appear to have an
active maintainer?
I'm well aware of ext/xmlrpc's limitations, haven't tried the new (but
necessary) pecl/xmlrpci ye
'Replace'? Code written for ext/xmlrpc won't work with ext/xmlrpci. Will
ext/xmlrpc be available in PECL, given that it doesn't appear to have an
active maintainer?
I'm well aware of ext/xmlrpc's limitations, haven't tried the new (but
necessary) pecl/xmlrpci yet, and have the tiny issue that a
Hi, David,
On Sunday 28 August 2005 10:18, David Kingma | jool.nl wrote:
> If you replace the te following lines:
>
> "("php"|"\"php\""|"\'php\'"){WHITESPACE}*">" { HANDLE_NEWLINES(yytext,
> yyleng);
> if (CG(short_tags) || yyleng>2) { /* yyleng>2 means it's not
Stanislav Malyshev wrote:
DR>>If it returns false, the engine can throw an error on the line where
DR>>it was used, not inside the __get() method itself, as that doesn't
DR>>help debugging your code (as you don't usually know where it was
DR>>called from).
That I understand. However, you sti
DR>>Problem 1 is the least of the 3 problems, but introducing the keyword
DR>>also helps solving the other two.
Strangely enough it is the agument I happen to hear most. I think it's not
PHP problem at all.
DR>>If I'm not wrong, __isset() checks if something is *set* not if it's
DR>>available
Johannes Schlueter wrote:
Hi Sara,
On Sunday 28 August 2005 00:02, Sara Golemon wrote:
+"
And what's with or any other processing instruction? Even
so others than xml are rarely used it would imho be a great wtf factor if
At a sidenote: If you output xml you anyways neet to set t
OG>>This is a valid argument. PHP has always been the BORG language that
OG>>assimilates every positive aspect of other languages. Nowadays PHP users
Who said multiple inheritance is positive aspect?
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/ +972-3-613
11 matches
Mail list logo
