>
> > That's okay, but I would like to standardize on the execution of the
>
> program name, with no args, to return a short usage string. I guess a
> > very few programs might not take to that convention (but I'll have to
> > be convinced), but most (if not all) could be converted to do that.
>
> Two cases in point are mged and burst (which is my current interest as
> a test case for my proposal). Both jump into a terminal-grabbing
> process with no args, but I would change them to no-arg usage (argc ==
> 1) such as:
>
> $ mged -g | -c [...options...]
>
> $ burst -g | -b [...options...]
>
> where the '-g' option is GUI and the other is command line oriented...
>
Just my 2 cents, but I would be definitely opposed to any convention that
didn't have the gui coming up by default when someone typed "mged". Also,
most or all of our proc-db and shapes programs will output a default .g
file when no arguments are supplied.
You mentioned terminal-grabbing - is this causing a problem in some way?
CY
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
