On 5/11/06, Ralph Schindler <[EMAIL PROTECTED]> wrote:
> possible to determine the context of a T_TRY token, but nonetheless,
> it's bad practice to have functions named the same as reserved words
Thats a matter of opinion. I think its bad practice to think up a
method name that is less conci
> In case you miss it, this discussion is about breakages within the
> same major version.
I am talking strictly from a Major Release standpoint, which is why I
titled it PHP6 compiler features...
...
My understanding is that this type of change would be slightly massive
undertaking to the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Sean Coates wrote:
>> In any event, I'm just trying to indicate that others may also face
>> issues if they have PHP4 apps with these sorts of keywords in them.
>
> "try" has been a reserved word (documented) since Fri Oct 1 08:07:16
> 2004 UTC:
> In any event, I'm just trying to indicate that others may also face
> issues if they have PHP4 apps with these sorts of keywords in them.
"try" has been a reserved word (documented) since Fri Oct 1 08:07:16
2004 UTC:
http://cvs.php.net/viewcvs.cgi/phpdoc/en/appendices/reserved.xml?view=diff&r1=1
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Pierre wrote:
> On 5/11/06, Jasper Bryant-Greene <[EMAIL PROTECTED]> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: RIPEMD160
>>
>> Just to add my 2c, I am currently trying to migrate a legacy PHP4
>> application to PHP5
>
> In case you mi
On 5/11/06, Jasper Bryant-Greene <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Just to add my 2c, I am currently trying to migrate a legacy PHP4
application to PHP5
In case you miss it, this discussion is about breakages within the
same major version.
--Pierre
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Just to add my 2c, I am currently trying to migrate a legacy PHP4
application to PHP5, and one of the huge hurdles is a set of classes
representing a group of tasks, each class having a method called try().
These classes are used in over 100,000 l
Precisely. The point I was trying to make is that there should be fewer
restrictions on method names of classes so that developers that are
maintaining some distributable classes can keep the API clean. I've
found myself in a situation where instead of using a method call
isset(), I must use
Antony, I believe Ralph was using isset() and unset() purely
as arbitrary examples, e.g:
class TestReservedKeywordMethods
{
function unset() { echo "unset"; }
function echo() { echo "echo"; }
function empty() { echo "empty"; }
}
$test = new TestReservedKeywordMethods();
__isset() and __unset() methods are what you're looking for.
They are available since 5.1.0.
See http://www.php.net/manual/en/language.oop5.overloading.php
On 10.05.2006 21:28, Ralph Schindler wrote:
Architectural restrictions aside, is it far off to ask if something like
this could be possibl
Architectural restrictions aside, is it far off to ask if something like
this could be possible in PHP6:
value))
return false;
else
return true;
}
public function unset()
{
$this->value = 0;
}
}
$test = new TestReservedKeywordMethods()
11 matches
Mail list logo
