Hi Zeev,
Zeev Suraski mailto:[EMAIL PROTECTED] wrote on Thursday, August 25, 2005 7:37
PM:
Fatal error: Only variables can be passed by reference in
/xxx/www/wiki/includes/SpecialSpecialpages.php on line 68:
aeaeciaobsoee
It appears to be due to a genuine fix for bug #31525.
On Thu, 25 Aug 2005, Michael Sims wrote:
Derick Rethans wrote:
I implemented that (except I dropped the _ERROR part for
E_RECOVERABLE_ERROR as I found it too long). The patch is here:
http://files.derickrethans.nl/patches/e_fatal-20050825.diff.txt
Any comments?
Since this new
On Fri, 26 Aug 2005, Sonke Ruempler wrote:
Hi Zeev,
Zeev Suraski mailto:[EMAIL PROTECTED] wrote on Thursday, August 25, 2005
7:37
PM:
Fatal error: Only variables can be passed by reference in
/xxx/www/wiki/includes/SpecialSpecialpages.php on line 68:
aeaeciaobsoee
It
Fair enough Wez :)
On Thu, 2005-08-25 at 20:34 -0400, Wez Furlong wrote:
In some environments you *need* to run a zts enabled PHP.
People that run in those environments can heed the warnings about
potential stability issues, evaluate them, and decide whether it makes
sense for their
At 03:34 26/08/2005, Wez Furlong wrote:
In some environments you *need* to run a zts enabled PHP.
People that run in those environments can heed the warnings about
potential stability issues, evaluate them, and decide whether it makes
sense for their application.
I don't see any compelling need
On Fri, 26 Aug 2005 09:12:51 +0200 (CEST)
[EMAIL PROTECTED] (Derick Rethans) wrote:
On Fri, 26 Aug 2005, Sonke Ruempler wrote:
Hi Zeev,
Zeev Suraski mailto:[EMAIL PROTECTED] wrote on Thursday, August
25, 2005 7:37 PM:
Fatal error: Only variables can be passed by reference in
On Thu, 25 Aug 2005, Andi Gutmans wrote:
At 06:00 AM 8/25/2005, Edin Kadribasic wrote:
Derick Rethans wrote:
And how can you possibly argue that this more complex than all the other
OO crap that people are suggesting here
I belive that we should do our best to filter out this storm
comments at the end of this mail
tex
-Original Message-
From: Makoto Tozawa [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 25, 2005 4:47 PM
To: Tex Texin
Cc: 'Andrei Zmievski'; [EMAIL PROTECTED]; 'PHP
Developers Mailing List'
Subject: Re: [PHP-DEV] Re: PHP Unicode support
Makoto,
ok, thanks. Now I see. You are saying that the multi-byte extension took the
opposite approach and made existing str*() byte oriented and the mb_str*()
character oriented.
So we have:
s2m) Migration from singlebyte to multibyte: change code that needs character
units to use mb*()
Tex Texin wrote:
I guess the way to think about it, is the FORM's accept-charset tells
the user agent the encodings the server accepts. In the POST to the
server, the user agent is telling the server the encodings it
accepts, and it is not resending the forms' accept-charset attribute.
People
Derick Rethans wrote:
Since this new error level is being created, I have a suggestion for
another type of error I would very much like to see changed from
fatal to recoverable. The error I'm referring to is attempting to
call a method on a non-object. This used to be a E_WARNING a long
Marcus Boerger wrote:
Hello Christian,
Thursday, August 25, 2005, 12:17:25 PM, you wrote:
Jochem Maas wrote:
I would see this as a optional addition to the syntax of interfaces...
i.e. everything works as before but you can add default function bodies
which would behave as if it was
I don't think __call/__get/__set should be resolving visibility.
Maybe that's the difference. It's main purpose is to allow exposing a
dynamic public interface.
I understand exactly where he was going with this, and I just don't
think PHP is the right place to do it.
Andi
At 02:55 AM
Zeev Suraski wrote:
Umm, that's not exactly an option, not before 5.1 proves itself stable
(as far as architecture goes - the changes between 5.0 and 5.1 are as
substantial as the changes between 4.x and 5.0 were). PHP 5.0 is
deployed on roughly 5% of the userbase, including most of the new
On Thu, 25 Aug 2005, Ilia Alshanetsky wrote:
I think there is a good reason for this patch making its way into PHP
5.1 and 5.0, any chance relevant RMs could be convinced to allow it? :-)
Patch for 5.1 is here:
http://files.derickrethans.nl/patches/e_recoverable_error-php-5.1-20050826.diff.txt
On Aug 26, 2005, at 5:55 AM, Derick Rethans wrote:
I'm just arguing that the current way that setters and getters are
implemented is broken. Instead of keeping a broken behavior I would
like
to see it fixed.
Derick,
It is not broken its incomplete. PHP doesn't really have an
Yes.
Makoto
Tex Texin wrote:
Makoto,
ok, thanks. Now I see. You are saying that the multi-byte extension took the
opposite approach and made existing str*() byte oriented and the mb_str*()
character oriented.
So we have:
s2m) Migration from singlebyte to multibyte: change code that needs
Hello Andi,
Friday, August 26, 2005, 3:39:08 AM, you wrote:
At 06:00 AM 8/25/2005, Edin Kadribasic wrote:
Derick Rethans wrote:
And how can you possibly argue that this more complex than all the other
OO crap that people are suggesting here
I belive that we should do our best to filter
Michael Sims wrote:
Derick Rethans wrote:
Since this new error level is being created, I have a suggestion for
another type of error I would very much like to see changed from
fatal to recoverable. The error I'm referring to is attempting to
call a method on a non-object. This used to be
Hello Andi,
Saturday, August 27, 2005, 12:52:38 AM, you wrote:
At 11:32 AM 8/26/2005, Marcus Boerger wrote:
I don't see why the __get/__set/__isset/__unset methods themselves
can't check if the property exists and throw an exception if it
doesn't. I always do that in all my examples...
http://downloads.php.net/zeev/php-5.0.5RC2.tar.gz
http://downloads.php.net/zeev/php-5.0.5RC2.tar.bz2
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Zeev Suraski wrote:
http://downloads.php.net/zeev/php-5.0.5RC2.tar.gz
http://downloads.php.net/zeev/php-5.0.5RC2.tar.bz2
PEAR is successfully updated to 1.3.6 with XML_RPC 1.4.0
Greg
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
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
creating scripts/phpize
creating scripts/man1/phpize.1
sed: can't read ./scripts/man1/phpize.1.in: No such file or directory
23 matches
Mail list logo
