[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: proposal - command-line option checking
From: |
Harlan Stenn |
Subject: |
Re: proposal - command-line option checking |
Date: |
Thu, 14 Dec 2006 05:45:32 +0000 |
I understand and agree with the coding standards, and it would be nice
if, for example, each invoked "configure" noted which options it did
anything with, and if the parent "configure" process noted usage it
should not be all that hard to have the top-level "configure" process
write a note saying that a supplied option was not used.
Granted, this would happen after all the work was done (and time spent),
but it would still be useful.
H
- proposal - command-line option checking, Steven G. Johnson, 2006/12/13
- Re: proposal - command-line option checking, Paul Eggert, 2006/12/14
- Re: proposal - command-line option checking,
Harlan Stenn <=
- Re: proposal - command-line option checking, Benoit Sigoure, 2006/12/14
- Re: proposal - command-line option checking, Ed Hartnett, 2006/12/14
- Re: proposal - command-line option checking, Ralf Wildenhues, 2006/12/14
- note of thanks to Ralf in the netCDF RELEASE notes..., Ed Hartnett, 2006/12/14
- Re: proposal - command-line option checking, Matthew Woehlke, 2006/12/14
- Re: proposal - command-line option checking, Bob Friesenhahn, 2006/12/14
- Re: proposal - command-line option checking, Matthew Woehlke, 2006/12/14
- Re: proposal - command-line option checking, Ralf Wildenhues, 2006/12/14
- Re: proposal - command-line option checking, Matthew Woehlke, 2006/12/14
- Re: proposal - command-line option checking, Steven G. Johnson, 2006/12/14