[comp.os.os2.programmer] guidelines for command line arguments?

dedina@cup.portal.com (Michael J Dedina) (03/31/91)

I'm writing the command-line invocation user-interace portion of a new OS/2
application (i.e., argument and options processing).  Being somewhat
new to the OS/2 world (and the DOS world for that matter), I would
like to know if there are any standards or conventions for what
invocation lines should look like under OS/2.  For example, when invoking
program "foo", should slashes be used to specify options?:
       foo filename /opt1 /opt2
or should unix-like dashes be used?   Should I allow options to be intermixed
with arguments?
       foo /opt1 filename1 /opt2 filename2
Should blanks be allowed liberally?
       foo filename  /  opt1 /opt2/opt3
How should values for options be specified?
       foo filename /opt1(opt1value)
How about subobtions?
       foo filename /opt1(/opt1b(opt1bvalue))
Etcetera.

I would like to make the application fit in with the "style" of OS/2 but
its not clear to me that there is a clearly defined style.

-Mike Dedina
dedina@cup.portal.com