[ntp:hackers] -d/--debug-level -> -d/--inc-debug-level?

TSG tglassey at earthlink.net
Tue Nov 18 20:27:03 UTC 2008


Brian Utterback wrote:
> I'm sorry, but that seems broken to me. Flags are case-sensitive. What 
> point is there in having two different flags that do the same thing?
>
> On a more platform centric note, Solaris' architecture rules for 
> command line flags prohibit flags that optionally take a value.
>   
Brian's right - the flags need to be simple and not something that 
allows people to create logs with unknown levels of logging in them. Any 
and all setting of the LOG LEVEL or DEBUG LEVEL characteristics should 
be straight forward and NEVER dependent on the previous setting level.
> Steve Kostecke wrote:
>   
>> Danny Mayer said:
>>
>>     
>>> Harlan Stenn wrote:
>>>       
>>>> I was noticing that the debug switches are:
>>>>
>>>>  -d   --debug-level	"Increas output debug message level"
>>>>  -D   --set-debug-level	"Set the output debug message level"
>>>>         
>> Do these options produce the same out put for the same debug level?
>>
>>     
>>>> I was thinking it would make more sense if the long-option flag was
>>>> either:
>>>>
>>>>  --inc-debug-level
>>>>
>>>> or
>>>>
>>>>  --incr-debug-level
>>>>
>>>> Does anybody care enough about this to comment?
>>>>         
>>> ... you are going to have them make them shorter.
>>>       
>> We should have one case insensitive debug option:
>>
>> -d / -D / --debug
>>
>> The user should be able to specify multiple debug options (e.g. -d or -d
>> -d or -dddd) to increase the level or an arbitrary debug level (e.g. -d
>> 4 or -D 6 or --debug=7).
>>
>>     
>
>   
> ------------------------------------------------------------------------
>
>
> Internal Virus Database is out of date.
> Checked by AVG - http://www.avg.com 
> Version: 8.0.175 / Virus Database: 270.9.0/1779 - Release Date: 11/10/2008 7:53 AM
>
>   



More information about the hackers mailing list