Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!wuarchive!julius.cs.uiuc.edu!rpi!uwm.edu!psuvax1!rutgers!cbmvax!uunet!mcrware!mwca!bill
From: bill@mwca.UUCP (Bill Sheppard)
Newsgroups: comp.sys.atari.st
Subject: Re: case insensitivity in TOS
Summary: Further discussion
Message-ID: <1786@mwca.UUCP>
Date: 16 Jan 91 18:17:11 GMT
References: <1991Jan12.023029.20022@convex.com> <2807@atari.UUCP> <1991Jan15.141034.24275@cs.dal.ca>
Organization: Microware Systems Corp., Santa Clara, CA
Lines: 18

Regarding case sensitivity of GEMDOS...

At work I use both OS-9 and Unix. OS-9 is not case sensitive, although
filenames will contain both upper and lower case in directory listings
("SOURCE" == "Source" == "source"). Unix, of course, is case sensitive.
I prefer the OS-9 method (employee bias notwithstanding) because it allows
me to use capitals where organization/convention calls for (directory names
in caps, for example), but still makes it easy to specify filenames. Besides,
I don't think it would be very good procedure to have both the file
"stuff.txt" and "Stuff.txt" in the same directory. Perhaps there would be
an easy patch to TOS to not have filenames converted to uppercase when
written to the directory sector, but still have "open" calls use uppercase
when comparing filenames for matches...
-- 
################################################################################
#  Bill Sheppard  --  bills@microware.com  --  {uunet,sun}!mcrware!mwca!bill   #
#  Microware Systems Corporation  ---  OS-9: Seven generations beyond __/_!!   #
#######Opinions expressed are my own, though you'd be wise to adopt them!#######