News for hackers. Stuff that matters.
Re:Five reasons why the PHP silence operator @ should be avo... by cfinke on Thursday January 10, 2013 @11:45AM (#5037948)
One reason to use it: to silence functions that generate warnings when the falsy return value would suffice.

http://php.net/manual/en/function.parse-url.php

5.3.3 Removed the E_WARNING that was emitted when URL parsing failed.

Re:Five reasons why the PHP silence operator @ should be avo... by josephscott on Thursday January 10, 2013 @01:02PM (#5038537)
A logical first step would be to fix all of those functions in PHP that end up requiring the use of @. Once that is done then we could move forward with removing all @ use.
Re:Five reasons why the PHP silence operator @ should be avo... by juan_juarez on Thursday January 10, 2013 @01:27PM (#5038730)
Next step, remove all PHP use.
Re:Five reasons why the PHP silence operator @ should be avo... by mikey_p on Thursday January 10, 2013 @03:30PM (#5039544)
Another one that I ran into at the same time as parse_url is that passing NULL to urldecode would throw a notice, which was simpler to @ away then check first since it always returned an empty string anyway.
Re:Five reasons why the PHP silence operator @ should be avo... by josephscott on Thursday January 10, 2013 @04:47PM (#5039994)
According to the changelog for parse_url that is no longer the case for 5.3.3 and up.