Lately I've been writing scripts for an application with it's own lighter weight scripting language and a Perl API. The proprietrary language uses syntax such as
, etc. Even in Perl scripts, we have to use some of their language to specify filters (like what to/not to run against) in the proprietary language format in a special comment block at the top. So, lately, even in Perl I've found myself writing 'and' instead of '&&" and ditto for 'or'. I'm not as fast to use 'not' instead of '!', but it's tempting. One benefit is for our non-programming users, they can make more sense of the Perl code.$model like /pattern/ $IPaddress in [ 192.168.0.0/24, 192.168.1.0/24 ] and $IPaddress not in + [ 192.168.0.1/32, 192.168.1.1/32]
My question is what's the risk/harm in using them like this? There's the low precedence that allows them to work, but I haven't been bitten by that yet (that I know of).
Elda Taluta; Sarks Sark; Ark Arks
My deviantART gallery
In reply to Thoughts on using and, or, and not over && || !? by Argel
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |