Background: Suppose I have the following obviously-incorrect PHP:
try{
$vtest = '';
print(array_pop($vtest));
}catch(Exception $exx){}
For it to work with array_pop, $vtest should obviously be an array, not a string. Nevertheless, when I run this code the Warning is exhibited. I don't want that, I just want the code to fail silently.
Question: Is there something special about PHP try-catch compared to other languages that cause this not to work?
Disclaimer: Just for reference, it is true there are other ways to handle this situation in PHP, but these are undesirable. The goal here is to avoid:
The "at-sign" trick:
$vtest = '';
print(@array_pop($vtest)); // <-- would like to avoid this
Type Casting:
$vtest = '';
$vtest = (array)$vtest;
print(array_pop($vtest));
The only way I can think of would be to do the following:
Of course if you just want to do this silently you could just do the following since you don't need to catch any exception:
Warnings and notices are not technically exceptions in PHP. To catch an exception it has to be explicitly thrown, and many of the built-in libraries of functions do not throw exceptions (mostly because they were written before PHP supported exceptions).
It would have been nice if somehow exceptions were built on top of the existing notice/warning/error framework but perhaps that is asking too much.
You can catch such errors when you convert every error to an exception. I have set up a little error-handling environment. Just test it - it will work.
A warning will always be produced by the code you provided but you can use set_error_handler to dictate how the warning is handled; i.e. you can cause it to throw an exception. Furthermore, you can use restore_error_handler to return to default error handling when your done.