X-Trace-PostClient-IP:	68.147.131.211
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Command line wildcard expansion under Win2K
Organization:	Systematic Software
Message-ID:	<10gk3v8v7m52k5pi41205gd902jbruq7pj@4ax.com>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1030130095126 DOT 2797A-100000 AT is> <3e394a9a DOT sandmann AT clio DOT rice DOT edu>
X-Newsreader:	Forte Agent 1.92/32.572
MIME-Version:	1.0
Lines:	53
Date:	Fri, 31 Jan 2003 09:28:25 GMT
NNTP-Posting-Host:	24.71.223.147
X-Complaints-To:	abuse AT shaw DOT ca
X-Trace:	news2.calgary.shaw.ca 1044005305 24.71.223.147 (Fri, 31 Jan 2003 02:28:25 MST)
NNTP-Posting-Date:	Fri, 31 Jan 2003 02:28:25 MST
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

On Thu, 30 Jan 2003 09:54:02 CST, Charles Sandmann
<sandmann AT clio DOT rice DOT edu> wrote:

>> > So, if you use any upper case characters on your input you may be
>> > surprised.  I believe this is the behavior which is non-intuitive.
>> 
>> Could you please state explicitly, with examples, what is non-intuitive 
>> about this, and what alternative behavior would be more intuitive?
>
>Okay, lets go back to my examples:
>
>"A.vec" exists (A upper case):
>
>C:\>djecho a*.vec A*.vec A*.VEC a*.VEC
>a.vec A.vec A*.VEC a*.VEC                    (current behavior)
>a.vec A.vec A.vec a.vec                      (intuitive behavior)
>
>In other words, act as if you had passed these strings to the 
>"dir" command.
>
>"B.VEC" exists (all upper case):
>
>C:\>djecho b*.vec B*.vec b*.VEC B*.VEC
>b.VEC B*.vec b*.VEC B.VEC                    (current behavior)
>b.vec b.vec b.vec B.VEC                      (intuitive behavior)
>
>In other words, I think forcing an exact match on any upper case
>characters is not intuitive - that all matches should be case
>insensitive - at least as an option.  The case of what is returned
>above is not important - but the fact that it finds a match.
>
>> > matching and still be able to return the lowercased names when 
>> > appropriate.
>> 
>> Sorry, I'm not sure I understand this (I think there's a typo in this 
>> sentence): what would you like to be able to do?
>
>I think this behavior should be decoupled from FNCASE.

Maybe glob could support more options e.g. FNCASE=[NYBUL] where
default is currently really U respect upper insensitive lower, L
means respect lower insensitive upper, N means respect none
insensitive both upper and lower, Y (or B) means respect both
upper and lower insensitive none; OSLT. 

Thanks. Take care, Brian Inglis 	Calgary, Alberta, Canada
-- 
Brian DOT Inglis AT CSi DOT com 	(Brian dot Inglis at SystematicSw dot ab dot ca)
    fake address		use address above to reply
abuse AT aol DOT com tosspam AT aol DOT com abuse AT att DOT com abuse AT earthlink DOT com 
abuse AT hotmail DOT com abuse AT mci DOT com abuse AT msn DOT com abuse AT sprint DOT com 
abuse AT yahoo DOT com abuse AT cadvision DOT com abuse AT shaw DOT ca abuse AT telus DOT com 
abuse AT ibsystems DOT com uce AT ftc DOT gov				spam traps

- Raw text -