Bug #14094 Updated: Documentation for @new is missing
| From: | mfischer@php.net | Date: | Mon, 10 Jun 2002 10:50:42 +0000 |
| Subject: | Bug #14094 Updated: Documentation for @new is missing | ||
| References: | 1 | Groups: | php.bugs php.doc |
| Request: | Send a blank email to php-bugs+get-10008@lists.php.net to get a copy of this message | ||
ID: 14094
Updated by: mfischer@php.net
Reported By: mfischer@guru.josefine.at
-Status: Open
+Status: Closed
Bug Type: Documentation problem
PHP Version: 4.0.6
New Comment:
This bug has been fixed in CVS. You can grab a snapshot of the
CVS version at http://snaps.php.net/. In case this was a
documentation
problem, the fix will show up soon at http://www.php.net/manual/.
In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites.
Thank you for the report, and for helping us make PHP better.
Again me ...
Previous Comments:
------------------------------------------------------------------------
[2001-11-17 17:01:46] mfischer@guru.josefine.at
The documentation about classes/objects misses that you actually can
prevent exposing errors in the constructor by using @new.
And, it should also mentioned that you can't use the '@' operator with
&new.
$obj = @new classname; // ok, works
$obj = @&new classname; // parser error
&new classname is a special case, therefore you can't "mute" it.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=14094&edit=1