Sender: crough45 AT amc DOT de
Message-Id: <97May28.142340gmt+0100.16647@internet01.amc.de>
Date: Wed, 28 May 1997 13:27:43 +0100
From: Chris Croughton <crough45 AT amc DOT de>
Mime-Version: 1.0
To: mdruiter AT cs DOT vu DOT nl
Cc: djgpp AT delorie DOT com
Subject: Re: (Another) BASH-bug? Or feature? 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Ruiter de M wrote:

> I have noticed the following behaviour of the latest BASH-port version:

Do you mean it's different in previous versions, or just that is the
one you're using?  (Incidentally, 'latest' can be ambiguous, due to
net lag; it's helpful if you can state the version number, then we can
check immediately if our versions are the one you mean.)

> bash$ ls */PLUGIN/OPT
> ls: No such file or directory */PLUGIN/OPT (ENOENT) (or alike)
> bash$ ls */plugin/opt
> rx/plugin/opt

That seems to be correct to me.  Granted that DOS isn't case-sensitive,
but bash and ls are Unix utilities and so are likely to differentiate.  
The gcc port is also case-sensitive - if you say

  $ gcc fred.c

it's compiled as C, whereas

  $ gcc fred.C

is compiled as C++ (the same sort of thing with .s and .S, the latter 
is put through the preprocessor before being passed to the assembler).

If your complaint is that previous versions of the bash port didn't 
behave the same, then in my opinion you have a good point and it may
be a bug.  If it's that you don't like the way bash treats case 
differences then you may also have a good point but it's a different 
one and not necessarily a bug.

Chris