From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,8d472879e3f609e0 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-08 20:48:23 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!cyclone.bc.net!snoopy.risq.qc.ca!chi1.webusenet.com!news.webusenet.com!cyclone1.gnilink.net!spamkiller2.gnilink.net!nwrdny02.gnilink.net.POSTED!53ab2750!not-for-mail From: Hyman Rosen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Case sensitivity (was Re: no title) References: <20619edc.0306021018.6ee4dd09@posting.google.com> <1054649187.11497@master.nyc.kbcfp.com> <20619edc.0306031034.6a2f5f25@posting.google.com> <1054666439.685312@master.nyc.kbcfp.com> <1054735867.264510@master.nyc.kbcfp.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: Date: Mon, 09 Jun 2003 03:48:22 GMT NNTP-Posting-Host: 162.84.224.133 X-Complaints-To: abuse@verizon.net X-Trace: nwrdny02.gnilink.net 1055130502 162.84.224.133 (Sun, 08 Jun 2003 23:48:22 EDT) NNTP-Posting-Date: Sun, 08 Jun 2003 23:48:22 EDT Xref: archiver1.google.com comp.lang.ada:38842 Date: 2003-06-09T03:48:22+00:00 List-Id: Frank J. Lhota wrote: > Needless to say, this can create problems when porting Unix code > to a case-insensitive OS. Why? If the first check succedes, then the file is there, and if it fails, the second check will fail as well. What's the problem?