Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site burl.UUCP Path: utzoo!linus!decvax!harpo!eagle!mhuxt!mhuxi!mhuxa!houxm!hocda!spanky!burl!rcj From: rcj@burl.UUCP Newsgroups: net.cog-eng Subject: Re: expert/novice interface in one program Message-ID: <300@burl.UUCP> Date: Thu, 25-Aug-83 16:56:26 EDT Article-I.D.: burl.300 Posted: Thu Aug 25 16:56:26 1983 Date-Received: Sat, 27-Aug-83 16:56:22 EDT References: <1989@utcsrgv.UUCP> Organization: Western Electric, Burlington, NC Lines: 47 I like to use the following approach for a program called (for example) auas (Arithmetic Unit microcode ASsembler): $ auas auas [-B bfile] [-D dfile] [-d] [-e] [-L lfile] [-l] [-m] [-p] [-y] infile (For verbose description of switches, type "auas -e") $ auas -e auas [-B bfile] [-D dfile] [-d] [-e] [-L lfile] [-l] [-m] [-p] [-y] infile -B bfile optional MICA output file name, default is au..b -D dfile put microcode debug information in -d put microcode debug information in au..d -e explanation of switches -L lfile save (normally temporary) listing file in -l save (normally temporary) listing file in au..l -m save (normally temporary) MICA input file in au..m -p run only preprocessor; do not run MICA -y YACC debug option +++++++++++++++++++++++++++++++++++ Another thing that I would like to see more of is SCCS's help feature. If you do something wrong, it will give you a reference to a verbose help text, thusly: $ get -e s.pds_insert ERROR [s.pds_insert]: writable `pds_insert' exists (ge4) $ help ge4 ge4: "writable `...' exists" For safety's sake, SCCS won't overwrite an existing g-file if it's writable. If you don't need the g-file, remove it and rerun the get command. +++++++++++++++++++++++++++++ That's enough suggestions for one article, -- The MAD Programmer -- 919-228-3814 (Cornet 291) alias: Curtis Jackson ...![ floyd sb1 mhuxv ]!burl!rcj