I had similar thoughts, but I found that using '&' on both ends made things
more understandable to the "normal" user. That is, the symmetry of using &
on both the caller and receiver side connected these very firmly and only
required explaining one piece of syntax. I'm hesitant to use the excuse of
"it looks like C" as a reason not to use this. It would be understandable to
people who already know C and easier to explain to those who don't.
I agree that using the same notation at both ends is good. But '&' is so
particularly irksome .. the whole point of REX was to avoid the need for
EXEC's '&' ... so it's doubly abrasive :-).
'*' at both ends would make just as much sense to the C programmer, too.
Or .. how about simple parentheses -- as already used in PARSE for a similar
purpose, for example? [I think we also considered CALL (foo) a,b once,
to allow call by a variable name.]
Mike
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
