Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:16724
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:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=fNLkYpQTN4balcg0PLGv0zJj7i3t9TBseZ/MpoAPisuOaKhk70obenCWUAW6UfMgD91IjdS5q2ne7XvD7TGaqDYlE8sUcwEy4Po3OIn9X/85RL3V5P2UA/coWNF/TKQxSGiAZBI7Xf2p7xxVB/gEu9xUKV92t55Kfwpv+AL/y00=
Message-ID: <a440ea0805061604524646389a@mail.gmail.com>
Date: Thu, 16 Jun 2005 12:52:44 +0100
Reply-To: Nelson Menezes <flying.mushroom@gmail.com>
To: Johannes Schlueter <johannes@php.net>
Cc: internals@lists.php.net, Sebastian Mendel <lists@sebastianmendel.de>
In-Reply-To: <200506161126.44054.johannes@php.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <FE.11.20931.54730B24@pb1.pair.com>
	<42B13E9A.7080706@php-tools.net> <95.E7.20931.05441B24@pb1.pair.com>
	<200506161126.44054.johannes@php.net>
Subject: Re: [PHP-DEV] forward compatibility "public" in 4.4
From: flying.mushroom@gmail.com (Nelson Menezes)

I completely agree. This (or any other "public-in-4.4" solution) would
only create an extra branch to maintain for both developers and users;
no one can expect all of the PHP 4.x base to go 4.4, and code with
"public" that "supports php 4 and 5" would actually break in 4.<4 and
still would be:

- unable to use PHP 5=20
- subject to the other PHP 4/5 issues

Besides, the point of E_STRICT seems to be to _enforce_ best practices
-- and if you care about this matter, considering all members as
"public" is probably defying the concept anyway.


On 6/16/05, Johannes Schlueter <johannes@php.net> wrote:
> On Thursday 16 June 2005 11:27, Sebastian Mendel wrote:
> > > I guess, this will more likely produce an error message like this:
> > >
> > > Parse error: syntax error, unexpected T_PUBLIC, expecting T_STRING in
> > > public.php on line 2
>=20
> right
>=20
> > > So I'm strongly against this change. If you want to run PHP4 code in
> > > PHP5, disable E_STRICT.
>=20
> +1
>=20
> > id dont know, but isnt there a difference between where the keywords ar=
e
> > placed?
>=20
> No, it's a parser keyword and a keyword can't be used as a function name.
>=20
> > and if it is so, then this would also be a candidate for
> >
> > "NOTICE: 'public' is a keyword in PHP 5" in php 4.4
>=20
> No. No "errors" for "forward compatibility".
>=20
> johannes
>=20
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20
>=20


--=20
Nelson Menezes
flying.mushroom@gmail.com