Re: forward compatibility "public" in 4.4

From: Date: Wed, 15 Jun 2005 17:53:57 +0000
Subject: Re: forward compatibility "public" in 4.4
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-16699@lists.php.net to get a copy of this message
Rasmus Lerdorf wrote:
What was the reasoning again for not having var be a synonym for public in PHP5? It is a bit annoying that a simple PHP4 class using var throws a notice in PHP5 when there is technically nothing wrong with it. -Rasmus I personally don't support "forward compatibility" as well. Especially when talking about a php 4.x tree, which has to be "downward" compatible as well. Introducing a new synonym allowing to develop "upward" compatible php code at least breaks this rule. On the other hand I don't believe that this synonym would help in any way to produce good perfoming "pre-php5" code.
Why not make PHP5 not complaining about those php4 "var" definitions at all? Maybe a new error level for "deprecated" keywords (and function calls) would be helpful? mike -- mike peter bretz metropolis ag / entwicklung email: m.bretz@metropolis-ag.de heinestraße 72 phone: +49-7121-348-120 d-72762 reutlingen fax: +49-7121-348-111 http://www.metropolis-ag.de/ metropolis ag. creating social internetworks.

« previous php.internals (#16699) next »