Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23736 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 42145 invoked by uid 1010); 28 May 2006 01:05:41 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 42130 invoked from network); 28 May 2006 01:05:41 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 May 2006 01:05:41 -0000 X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:38500] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 34/67-17316-367F8744 for ; Sat, 27 May 2006 21:05:40 -0400 Received: from baumbart.mbo (dslb-084-063-013-138.pools.arcor-ip.net [84.63.13.138]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id ED60D35C1DC; Sun, 28 May 2006 03:05:36 +0200 (CEST) Date: Sun, 28 May 2006 03:03:50 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <962070645.20060528030350@marcus-boerger.de> To: Andi Gutmans Cc: Zeev Suraski , internals@lists.php.net, Pavlo Shelyazhenko In-Reply-To: <7.0.1.0.2.20060527173708.03b3bd18@zend.com> References: <138663365.20060514205903@marcus-boerger.de> <038d01c676f8$ab9b3380$6602a8c0@foxbox> <44685D24.2000801@php.net> <1147708994.14148.23.camel@notebook.local> <16710545416.20060515202714@marcus-boerger.de> <1147721541.14148.47.camel@notebook.local> <4468DB43.1020005@emini.dk> <7.0.1.0.2.20060515194051.02b32ef8@zend.com> <1148496966.19173.79.camel@notebook.local> <454303585.20060524213714@marcus-boerger.de> <44765279.8000601@akbkhome.com> <7.0.1.0.2.20060526040633.086814a0@zend.com> <4476608C.6070503@akbkhome.com> <7.0.1.0.2.20060526050422.08680c20@zend.com> <1376291629.20060526040801@marcus-boerger.de> <7.0.1.0.2.20060526120130.03c51060@zend.com> <772458214.20060527001909@marcus-boerger.de> <7.0.1.0.2.20060527173708.03b3bd18@zend.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] planning future BC Breaks - was Re: [PHP-DEV] fatal static call in php 6.0? From: helly@php.net (Marcus Boerger) Hello Andi, i for one think it might be a solution to at least lower the pain of version differences. Which is the reason why i liked the proposal from the beginning and took mentorship. best regards marcus Sunday, May 28, 2006, 2:39:21 AM, you wrote: > I think a preprocessor is one of the worst things that can ever happen to PHP. > It can be done as a Summer of Code project for academic reasons but I > would never be in favor of adding it to PHP. I think there's very > little use in a language like PHP and it will lead to the same > maintenance/debugging problems as with C. > If someone really needs a pre-processor then they should use it in > their private environment and can even use cpp if they want. > I can't believe Marcus that you are in favor of something like this. > In any case, it doesn't matter. Nothing can stop the student from > doing something like this and dumping it in pecl or something, but > I'd never want to see a pre-processor in PHP itself. > Andi > At 03:19 PM 5/26/2006, Marcus Boerger wrote: >>Hello Zeev, >> >> actually there was plenty of discussion prior to selecting the summer >>of code projects. Nonetheless we will see how it will work out. For example >>#line can easily be aded to the lexer already and doesn't >>require a full blown preprocessor. Versioning is very different since it >>should either be a real preprocessor and thus not doing any harm to php >>or it is a language feature and then a bunch of stuff probably has to be >>changed. Though maybe even then it is a simple additional state in the >>lexer - those tools can be so easy. >> >>Anyway you might want to contact the student. >> >>marcus >> >>Friday, May 26, 2006, 11:04:30 AM, you wrote: >> >> > Yeah I heard, but it doesn't mean it'll become a part of the language >> > (doesn't mean that it would not, but as usual, no discussion ;). >> >> > What Alan suggested is already a part of the language, bares no >> > additional overhead (both CPU cycles and brain cycles), and also >> > (least important point) is very easy to implement. >> >> > Zeev >> >> >> >> > At 05:08 26/05/2006, Marcus Boerger wrote: >> >>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 >> >> >> >> >>Best regards, >> Marcus >> >>-- >>PHP Internals - PHP Runtime Development Mailing List >>To unsubscribe, visit: http://www.php.net/unsub.php Best regards, Marcus