4 ms·
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 ht
by cfinke 14y ago
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 http://php.net/manual/en/function.parse-url.php
5.3.3 Removed the E_WARNING that was emitted when URL parsing failed.
- josephscott 14y agoA 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.
- juan_juarez 14y agoNext step, remove all PHP use.
- mikey_p 14y agoAnother 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.
- josephscott 14y agoAccording to the changelog for parse_url that is no longer the case for 5.3.3 and up.