Req #14640 [Opn->Wfx]: Support "{@$foo}" and "{@$foo['bar']}" syntax

Edit report at http://bugs.php.net/bug.php?id=14640&edit=1 ID: 14640 Updated by: jani@php.net Reported by: mfischer at guru dot josefine dot at Summary: Support "{@$foo}" and "{@$foo['bar']}" syntax -Status: Open +Status: Wont fix Type: Feature/Change Request -Package: Feature/Change Request +Package: Scripting Engine problem Operating System: Any PHP Version: 4.1.0 Block user comment: N Private report: N New Comment: Hell no, rather get rid of @ altogether. Previous Comments: ------------------------------------------------------------------------ [2003-08-11 16:10:48] destes at ix dot netcom dot com what sorts of errors aren't being suppressed now? If the variable doesn't exist, nothing is output, and in a function context, FALSE is returned. I don't see the need... perhaps you could explain it? ------------------------------------------------------------------------ [2001-12-21 08:21:43] mfischer at guru dot josefine dot at $ php -q <? error_reporting(E_ALL); echo "{@$array['key']}"; ?> <br /> <b>Parse error</b>: parse error, expecting T_STRING' or T_VARIABLE' or `T_NUM_STRING' in <b>-</b> on line <b>2</b><br /> -(2) : Parse error - parse error, expecting T_STRING' or T_VARIABLE' or `T_NUM_STRING' $ php -q <? error_reporting(E_ALL); echo "{@$foo}\n"; ?> <br /> <b>Warning</b>: Undefined variable: foo in <b>-</b> on line <b>2</b><br /> -(2) : Warning - Undefined variable: foo {@} Would be nice to support the @ operator in those cases too. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/bug.php?id=14640&edit=1