Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23751
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=KMVZsJxnqbb1iSKVdNOk+t0v8pCR9ikWVY4kaORCsXMl2mlwY1vXxMriSdlZLl0szsDRwB0Vmw/Jjm96qXOGMQHHZj1P8FApcM6jpzYVso1EeriUi3kGAR3xXR2oxyshvmjU2PsaIrE+WKor5kb3SjDtYXScvUj6YrcbKrZlwQs=
Message-ID: <43b5c44e0605280926k6886d4f2o25c331ff3a07a009@mail.gmail.com>
Date: Sun, 28 May 2006 18:26:38 +0200
To: "Marcus Boerger" <helly@php.net>
Cc: "Christian Schneider" <cschneid@cschneid.com>, internals@lists.php.net
In-Reply-To: <6610529674.20060528114142@marcus-boerger.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <138663365.20060514205903@marcus-boerger.de>
	<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>
	<962070645.20060528030350@marcus-boerger.de>
	<4A.00.38460.00959744@pb1.pair.com>
	<6610529674.20060528114142@marcus-boerger.de>
Subject: Re: [PHP-DEV] planning future BC Breaks - was Re: [PHP-DEV] fatal static call in php 6.0?
From: wcandillon@gmail.com ("William Candillon")

I think that a macro will be a very nice and powerful solution to this
problem but according to me it needs to be done by an external tool.

Regards,

William

On 5/28/06, Marcus Boerger <helly@php.net> wrote:
> Hello Christian,
>
>   what you propose would mean a lot of changes to the php code and
> and the zend engine. The pre processor to allow this will be written
> as an extension and that extension will have no impact on anybody
> that doens't like it simply becuase you can disable extensions.
>
> best regards
> marcus
>
> Sunday, May 28, 2006, 10:01:58 AM, you wrote:
>
> > Marcus Boerger wrote:
> >>   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.
>
> > We don't need a full-blown preprocess for that. The much simpler versio=
n
> > switch proposed earlier would do. And this while introducing only 10% o=
f
> > the debugging knightmares of a full preproc.
>
> > But then again I'm even wary of a version switch as it could lead to
> > code like
>
> > class A
> > {
>
> > declare(> php4)
> > {
> >         static function foo() { ... }
> > }
>
> > declare(<=3D php4)
> > {
> >         function foo() { ...}
> > }
>
> > }
>
> > which raises copy/paste issues.
>
> > I'd much rather see less incompatibilities introduced into PHP in an
> > attempt to make PHP a language is was never meant to be ;-)
>
> > - Chris
>
>
>
>
> Best regards,
>  Marcus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>


--=20
William Candillon
Telecom Lille Student
E-mail: wcandillon@elv.enic.fr
Tel: +33(0) 6 67 99 13 16
CV: http://wcandillon.netcv.org
Resume: http://wcandillon.en.netcv.org