Re: Why does PHP have __toString() and not just toString()

From: Date: Tue, 12 Apr 2005 12:26:53 +0000
Subject: Re: Why does PHP have __toString() and not just toString()
References: 1 2 3  Groups: php.general 
Request: Send a blank email to php-general+get-212902@lists.php.net to get a copy of this message
Rory Browne wrote:
I was wondering that as well. While I was at it, I wondered why not use __to_str(), as per the PHP coding guidelines.
because that's *against* php coding guidelines :) You should have a look at the guidelines for METHOD-naming, which is part of the OOP part. It states that for method names, the camelcaps convention is used (aka "studly caps") - tul
While I'm at it, why is grass green, and milk white? On Apr 12, 2005 10:27 AM, Richard Davey <rich@launchcode.co.uk> wrote:
Hello Tim, Tuesday, April 12, 2005, 10:07:44 AM, you wrote: TB> I'm wondering, why does the toString() of classes have two underscored TB> preceding it [e.g. __toString()], as opposed to Java's normal toString()? TB> What's the purpose of the two underscores in PHP's classes? The short answer: Because PHP isn't Java. The long answer: Two underscores denote what PHP refers to as a "magic method". You shouldn't have your own functions with the same names (unless you require that magical functionality). Have a look in the PHP manual under the "Magic Methods" section for more info / examples. Best regards, Richard Davey -- http://www.launchcode.co.uk - PHP Development Services "I do not fear computers. I fear the lack of them." - Isaac Asimov -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php


« previous php.general (#212902) next »