Message-Id:	<4.2.0.58.19990917114245.00a40d20@hal.nt.tuwien.ac.at>
X-Sender:	tony AT dictator DOT nt DOT tuwien DOT ac DOT at
X-Mailer:	QUALCOMM Windows Eudora Pro Version 4.2.0.58
Date:	Fri, 17 Sep 1999 11:59:37 +0200
To:	djgpp AT delorie DOT com
From:	Anton Helm <tony AT dictator DOT nt DOT tuwien DOT ac DOT at>
Subject:	Re: Command line parameters
In-Reply-To:	<Pine.SUN.3.91.990916132237.7952J-100000@is>
References:	<37DFFEB8 DOT D89EE9D AT agcs DOT com>
Mime-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

At 01:23 PM 9/16/99 +0200, you wrote:
 >

BTW, I recently had annother problem with commandline parameters.
One of the users of my programs sent an email that commandline
switches that used to be lower case are "somehow" converted to
uppercase and lead to an error (the program checks the switches
in a case sensitive way).

Several hours (and 2 dozen emails...) later (Did you ever have a user
who told you the truth about what he actually did ???) I finally found 
the following:

1) He was using Norton Commander v5.0 when he was calling the program.
2) He first typed the switches with the wrong case and got an error.
3) Afterwards he typed the switches in the correct case and the program executed
    correctly.
    (Everything OK so far, this is expected behavior.)
4) He used the Norton Commander's command history to execute the program again.
    Here's the problem:
    NC doesn't store subsequent duplicates of commands in the history. 
    When storing something into the history NC obviously makes a _caseinsensitive_
    string compare, so it doesn't store the latest command because it thinks that
    it is already there.

This is not actually DJGPP related but kept me debugging for some time ...
As NC is very common in the DOS-world I think some others might have seen 
strange behavior too.

Tony

- Raw text -