foo($x,$y) if verbose; $handle= open($fname) or die;
But the if can certainly be written first, also. If an operator were being programmed/adjusted by setting contextual variables, then you would have to put those first.
Using ordinary function call syntax, the recommendation is to put the positional parameters first and the named parameters last, but you don't have to.$+case_sensitive = False; if $name1 gt $name2 { ...
You could write a macro to put operator adverbs first, using a keyword or something. That would be consistant with the syntax for 'if' used as a statement, and with 'given'. Something like: under :authority<AKC> { if $fido after $scooter { ... } }
Ah, but that moves it out from the whole statement, not still attached to the expression. I'm sure some syntax could be devised. If you want to continue to muse about it, I'll collect it as a use case for what macros need to be capable of, and will try it as an example when that part is being fleshed out.—John
In reply to Re^2: my new article, "A Romp Through Infinity"
by John M. Dlugosz
in thread my new article, "A Romp Through Infinity"
by John M. Dlugosz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |