I've always been partial to using the left square bracket or left curly brace when I can't use the left parenthesis. They have a similar "feel"
without conflicting with normal command syntax. Brian Nielsen On Thu, 31 Aug 2006 13:52:52 -0500, Mike Walter <[EMAIL PROTECTED]> wrote: >I wrote a command that sends commands on to another system for processin g. > This command is named (for historical and compatibility reasons) "RO". >The "other system's" command may have its own imbedded parenthesis. >Meanwhile, "RO" has its own options. > >Typical VM commands have options following an open parenthesis. Up unti l >now I've been using double close-parentheses, such as: > > RO some other system command operands ( some other system comman d >options )) RO's own options > >That DOES work, but looks rather "inelegant" to my eyes. Perhaps someon e >having experience with other systems might have a more elegant solution? >Obviously, a vertical bar (Pipe's default stage separator) is a >nonstarter. > >TIA, >Mike Walter >Hewitt Associates >Any opinions expressed herein are mine alone and do not necessarily >represent the opinions or policies of Hewitt Associates. > >The information contained in this e-mail and any accompanying documents >may contain information that is confidential or otherwise protected >from disclosure. If you are not the intended recipient of this message, >or if this message has been addressed to you in error, please >immediately alert the sender by reply e-mail and then delete this messag e, >including any attachments. Any dissemination, distribution or other use of >the contents of this message by anyone other than the intended recipient >is strictly prohibited. > >
