Re: planning future BC Breaks - was Re: [PHP-DEV] fatal static call in php 6.0?

From: Date: Fri, 26 May 2006 02:08:01 +0000
Subject: Re: planning future BC Breaks - was Re: [PHP-DEV] fatal static call in php 6.0?
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15  Groups: php.internals 
Request: Send a blank email to internals+get-23677@lists.php.net to get a copy of this message
Hello Zeev, actually there is a student working on a pre-processor for his summer of code project. And that will most likely cover versioning, too. best regards marcus Friday, May 26, 2006, 4:06:00 AM, you wrote: > I read it as if it was declare() ;) > I agree with Pierre that the best way to handle BC break is not to > introduce it, but since that's not always 100% possible, this may > make sense. Of course, it'll only work with stuff that is > syntax-compliant with the currently running PHP version, but that > covers most BC breakage. > Zeev > At 04:57 26/05/2006, Alan Knowles wrote: >>actaully it should have been declare() - as I think the syntax for that >>almost works already, but yes, code doesnt get compiled if it's inside a >>block. >> >>Regards >>Alan >> >>Zeev Suraski wrote: >> > At 03:57 26/05/2006, Alan Knowles wrote: >> >> Can we start concentrating on finding a real solution to BC breaks >> >> rather than throwing them out there and everyone complaining? >> >> >> >> define(php5) { >> >> stuff that breaks in php6 >> >> } >> >> define(php6) { >> >> stuff that doesnt work in PHP5 >> >> } >> > >> > What's the semantics of that? The code inside doesn't get executed if >> > it's not the define()'d PHP version? >> > >> > Zeev Best regards, Marcus

« previous php.internals (#23677) next »