guidelines for command line arguments?

Thread View: comp.os.os2.programmer

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Michael J Dedina Sat, 30 Mar 1991 18:33

#2497

Author: Michael J Dedina
Date: Sat, 30 Mar 1991 18:33

25 lines
1429 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads