hal commands should use linux standard option syntax and be consistent

[diekhans]

The hal commands use some kind of command line parser that is inconsistent with linux commands.

for instance --coverage=PantheraLeo returns an error
Also, you shouldn't have to care if a command is written in C++, C, or python, or FORTRAN. They
should all be the same.

[p.s. I am volunteering to help with a lot of this build and use cleanup, just want to file ticket, not point fingers]

[glennhickey]

Hi Mark,

Adding support for --option=val in addition to --option val, may end up
being a fairly minor change to CLParser::parseOptions()
(hal/api/impl/halCLParser.cpp), for whatever that's worth.

-Glenn

On Mon, Oct 6, 2014 at 7:29 AM, Mark Diekhans [email protected]
wrote:

The hal commands use some kind of command line parser that is inconsistent
with linux commands.

for instance --coverage=PantheraLeo returns an error
Also, you shouldn't have to care if a command is written in C++, C, or
python, or FORTRAN. They
should all be the same.

[p.s. I am volunteering to help with a lot of this build and use cleanup,
just want to file ticket, not point fingers]

—
Reply to this email directly or view it on GitHub
#23.