Re: [PHP-DEV] Method inheritance and parent classes

2006-08-04 Thread Marian Kostadinov
use self::build() or A::build() for that case 2006/8/4, Christian Weiske <[EMAIL PROTECTED]>: Hello all, I recently had a problem that could be solved, but in an ugly way: Class B extended Class A. Both classes define a method with the same name. B called A's constructor, and A called $this->

RE: [PHP-DEV] Long awaited line directive

2006-08-04 Thread Andi Gutmans
Hi Marcus, I'm still trying to figure out whether this patch might have some far reaching affects which we're not thinking of. For example, debuggers would not work with this and would need some serious changes. Also, there might be something inside Zend which expects the filename to be "correct".

Re: [PHP-DEV] Method inheritance and parent classes

2006-08-04 Thread Richard Lynch
On Fri, August 4, 2006 11:46 am, Christian Weiske wrote: > I recently had a problem that could be solved, but in an ugly way: > Class B extended Class A. Both classes define a method with the same > name. B called A's constructor, and A called $this->method(). This > executed B::method(), not A::me

Re: [PHP-DEV] Method inheritance and parent classes

2006-08-04 Thread Jason Sweat
On 8/4/06, Christian Weiske <[EMAIL PROTECTED]> wrote: I suggest changing the behavior of php to never call methods of classes that are added by subclasses, only own ones or inherited ones. Thus rendering the entire Template Method design pattern useless? http://home.earthlink.net/~huston2/dp/

[PHP-DEV] Method inheritance and parent classes

2006-08-04 Thread Christian Weiske
Hello all, I recently had a problem that could be solved, but in an ugly way: Class B extended Class A. Both classes define a method with the same name. B called A's constructor, and A called $this->method(). This executed B::method(), not A::method() as you would expect it. build(); }

Re: [PHP-DEV] PHP 4.4.3 released

2006-08-04 Thread Derick Rethans
On Fri, 4 Aug 2006, Joe Orton wrote: > On Thu, Aug 03, 2006 at 10:19:38AM +0200, Derick Rethans wrote: > ... > > Release Announcement: http://www.php.net/release_4_4_3.php > > substr_compare() is not in 4.4.x so: > > "Fixed offset/length parameter validation inside the substr_compare() > functi

Re: [PHP-DEV] PHP 4.4.3 released

2006-08-04 Thread Joe Orton
On Thu, Aug 03, 2006 at 10:19:38AM +0200, Derick Rethans wrote: ... > Release Announcement: http://www.php.net/release_4_4_3.php substr_compare() is not in 4.4.x so: "Fixed offset/length parameter validation inside the substr_compare() function." should not be listed here. Regards, joe --

[PHP-DEV] CVS Account Request: sinosteeltradingco

2006-08-04 Thread Mr. Huang Tianwen
for sending of bulk mails -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

RE: [PHP-DEV] RfC: rethink OO inheritance strictness

2006-08-04 Thread Soenke Ruempler
Hi, Just one question: Is there a real need to break BC in a minor version (5.1 => 5.2 is minor from a PHP users's, at least my POV) ? Can't this be done in 6.0? -soenke -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php

[PHP-DEV] [PATCH] MAX_LENGTH_OF_LONG, and possible buffer overflows

2006-08-04 Thread Matt W
Hi there, OK, so overflows aren't very likely with MAX_LENGTH_OF_LONG set to 20, but I found 3 places I think you'll want to change. :-) Also, can MAX_LENGTH_OF_LONG be changed to be accurate on 32-bit platforms? Is setting it to (sizeof(long) > 4 ? 20 : 11) acceptable? If MAX_LENGTH_OF_LONG is

Re: [PHP-DEV] RfC: rethink OO inheritance strictness

2006-08-04 Thread Derick Rethans
On Thu, 3 Aug 2006, Rasmus Lerdorf wrote: > Pierre wrote: > > > > On 8/3/06, Derick Rethans <[EMAIL PROTECTED]> wrote: > > > > > > In this particular case I think it should be possible to mark > > > certain internal > > > > methods as strict and keep userspace methods loose. > > > > > > But I w

Re: [PHP-DEV] RfC: rethink OO inheritance strictness

2006-08-04 Thread Lukas Smith
Derick Rethans wrote: - Add a new flag to methods (at the implementation level) that will allow to flag them as 'strict' - In case such a strict method is improperly overridden - error out (E_ERROR) - In case a non-strict method is improperly overridden - emit E_STRICT i am fine with tha