Everyone here should know the 'or' statemens, usually glued to an die() command:
$foo = bar() or die('Error: bar function return false.');
The most of the times we see something like:
mysql_query('SELECT ...') or die('Error in during the query');
However, i cant understand how exactly that 'or' statement works.
I would like to throw a new exception instead of die(), but:
try{ $foo = bar() or throw new Exception('We have a problem here');
Doesnt work, and neither
$foo = bar() or function(){ throw new Exception('We have a problem here'); }
The only way i found to do that is this horrible thought:
function ThrowMe($mess, $code){ throw new Exception($mess, $code); } try{ $foo = bar() or ThrowMe('We have a problem in here', 666); }catch(Exception $e){ echo $e->getMessage(); }
But there is a way to throw a new exception directly after the 'or' statement?
Or this kind of structure is mandatory (i dont liek the ThrowMe function at all):
try{ $foo = bar(); if(!$foo){ throw new Exception('We have a problem in here'); } }catch(Exception $e){ echo $e->getMessage(); }
Edit: what i want is really to avoid the use of an if() check every potential dangerous operation i do, for example:
#The echo $e->getMessage(); is just an example, in real life this have no sense! try{ $foo = bar(); if(!$foo){ throw new Exception('Problems with bar()'); } $aa = bb($foo); if(!$aa){ throw new Exception('Problems with bb()'); } //...and so on! }catch(Exception $e){ echo $e->getMessage(); } #But i relly prefer to use something like: try{ $foo = bar() or throw new Exception('Problems with bar()'); $aa = bb($foo) or throw new Exception('Problems with bb()'); //...and so on! }catch(Exception $e){ echo $e->getMessage(); } #Actually, the only way i figured out is: try{ $foo = bar() or throw new ThrowMe('Problems with bar()', 1); $aa = bb($foo) or throw new ThrowMe('Problems with bb()', 2); //...and so on! }catch(Exception $e){ echo $e->getMessage(); } #But i'll love to thro the exception directly instead of trick it with ThrowMe function.
or
is just a logical operator, and it's analogous to ||
.
The common trick of
mysql_query() or die();
could just as well be written
mysql_query() || die();
What happens here is the "logical or" operator (whichever you choose) is trying to determine if either operand evaluates to TRUE. This means the operands must be expressions that can be cast as a boolean.
So, the reason
bar() or throw new Exception();
is illegal, is because
(boolean)throw new Exception();
is also illegal. In essence, the process of throwing an exception doesn't generate a return value for the operator to check.
But calling a function does generate a return value for the operator to check (no explicit return value will result int the function returning NULL
which casts as FALSE
) which is why it works for you when you wrap exception throwing in a function.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With