Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!cmcl2!husc6!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: Re: Case sensitive file names
Message-ID: <5971@ut-sally.UUCP>
Date: Thu, 9-Oct-86 17:53:08 EDT
Article-I.D.: ut-sally.5971
Posted: Thu Oct  9 17:53:08 1986
Date-Received: Fri, 10-Oct-86 01:48:46 EDT
References: <5860@ut-sally.UUCP>
Organization: IEEE P1003 Portable Operating System for Computer Environments Committee
Lines: 34
Approved: jsq@sally.utexas.edu

From: seismo!philabs!phri!cooper!cooper!chris (Chris Lent)
Date: Tue, 7 Oct 86 19:26:42 edt

Just wondering,
	Why not set up a few functions to determine how the heck
each operating system handles filenames?

	For case sensitivity how about something like:
		isfsense() 
	which could be a macro to a constant or a function.

	Or better how about:
		isflegal(fname)
		char *fname;
	which would tell you if the operating system approves of your file
	name? Of course this could be done through existing functions
by opening the file, but this way COULD be implemented to reduce
file access overhead.

	But I think a good solution would be to follow FORTRAN-77's
example with the inquire statement which can get back the fully expanded
filename of an already open unit-number (file descriptor) or a
closed file.  I've found all F-77's I've tried to give back the
full pathnames on files.

	But I think that a minimum allowable character set for
filenames might be sufficient.  That is 'A-Z0-9.' would be fine
for most users I've run into.

Well that's about it
Chris Lent
ihnp4!philabs!phri!cooper!chris

Volume-Number: Volume 7, Number 44