I've started coding this up, and the "," syntax for list creation looks very
doable. The meaning of the "," depends on the context, as already noted,
but the contexts are absolutely unambiguous so it is always possible to
assign the correct meaning.
[sounds good]
However, I want to circle back around to the discussion of the
short-circuited AND. We can't eliminate the usage on IF/WHEN, etc., but on
the other hand, there are certainly contexts where an and operator that uses
short-circuit logic might be useful. One could argue that an OR version
could also be useful. I don't believe this is possible for XOR, since the
result always depends on both values. Are there any operator combinations
that would make sense? Doubling up obviously doesn't work because && and ||
are already operators.
Just thinking about the AND case for the moment, the short circuit 'bail out
early' is (apart from the very different level of the structure/syntax)
much the same as
if x then if y then ...
whereas the OR case with bail out early is the current syntax:
if x, y then ...
I think you're asking for a more expression-like version of the first.
Not keep on tripling-up, which is one possibility. Hmm, maybe:
if x +& y then ...
but perhaps one ought to add some similar bail-out-OR operator too. Maybe
'-|'? :-)
Mike
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Oorexx-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
