Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!convex!rosenkra From: rosenkra@convex.com (William Rosencranz) Newsgroups: comp.sys.atari.st Subject: Re: case insensitivity in TOS Message-ID: <1991Jan24.215555.12359@convex.com> Date: 24 Jan 91 21:55:55 GMT References: <1991Jan12.023029.20022@convex.com> <1991Jan18.005041.22961@convex.com> <1991Jan22.170111.12465@cs.mcgill.ca> <1991Jan23.115630.5846@convex.com> <4723@ruuinf.cs.ruu.nl> Sender: news@convex.com (news access account) Organization: Convex Computer Corporation; Richardson, TX Lines: 37 Nntp-Posting-Host: convex1.convex.com In article <4723@ruuinf.cs.ruu.nl> ate@cs.ruu.nl (Ate Brink) writes: >This depends on the TOS version. With TOS 1.0 I couldn't extract a file >from a ZOO archive with the x option when I started ZOO.TTP from the desktop. >TOS translated everything to uppercase and the X option is illegal with ZOO. >I had to use the -extract option. >After I replaced TOS 1.0 with TOS 1.4 I can use the x option. The X option >still generates an error message. >So TOS 1.4 is case sensitive, it only translates FILENAMES to uppercase. probably semantics or splitting hairs, but the 1.4 desktop is now case sensitive when dealing with .ttp dialogs, at least. TOS itself (or probably more properly GEMDOS), when dealing with filenames and file operations (notably GEMDOS Fopen/Fcreate/et al), remains case insensitive, forcing file names to upper case. my entire point is that there is no inherent reason to force upper case in GEMDOS, really. the actual bytes representing the file name written to FATs need not be upper case or lower case, but can be any ascii char. i believe it is GEMDOS which defines legal chars in file names. all i was asking for was a way to toggle GEMDOS into expanding this definition of legal chars as to differentiate between upper and lower case letters. and regarding breaking programs, i suspect that since if u pass Fopen a ptr to string "file.nam", on return, the string IS CHANGED (a definite "bug", IMHO, that i've always detested), forcing you to change your idea of the filename, programs have the modifications mentioned when parsing a filename AFTER an Fopen/Fcreate/etc and probably because of this flagrant disregard for sanctity of user data. such parsing may be done to isolate paths, extensions, etc, tho these examples look for non-letters (i.e. ".", ":", and "\"). drive letter seems like the only real reason to worry, or perhaps extensions. so rather than strcmp/strncmp, use stricmp/strincmp (ignore case). and yes, i know these are not in POSIX/ANSI C... -bill rosenkra@convex.com -- Bill Rosenkranz |UUCP: {uunet,texsun}!convex!c1yankee!rosenkra Convex Computer Corp. |ARPA: rosenkra%c1yankee@convex.com