Article View: mod.std.unix
Article #322Re: Case sensitive file names
From: Moderator, John Quarterman
Date: Fri, 17 Oct 1986 23:42
Date: Fri, 17 Oct 1986 23:42
21 lines
1423 bytes
1423 bytes
From: rbj@icst-cmr.arpa (Jim Cottrell) Date: Fri, 17 Oct 86 16:57:43 EDT > Having done a lot of case insensitive work, i've always felt that the > UNIX case sensitivity was from laziness. If i were to be charitable, > i might go so far as to call it a shortcut. I prefer to call it optimization. Case insensitivity must be enforced. By my count, that's at least two instructions per character, plus loop control (unless you have something like VAX's `move translated characters'). That ought to negate any speedup from hashing or name translation caching. What is lazy is people refusing to learn the difference. [ See previous comments about argument by character assassination. -mod ] (Root Boy) Jim Cottrell <rbj@icst-cmr.arpa> YOW!! I'm in a very clever and adorable INSANE ASYLUM!! Volume-Number: Volume 7, Number 69
Technical Details
Message-ID:
<6037@ut-sally.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!seismo!ut-sally!std-unixReferences:
<6027@ut-sally.UUCP>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!mnetor!seismo!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: <6037@ut-sally.UUCP> Date: Fri, 17-Oct-86 19:42:36 EDT Article-I.D.: ut-sally.6037 Posted: Fri Oct 17 19:42:36 1986 Date-Received: Sat, 18-Oct-86 00:31:10 EDT References: <6027@ut-sally.UUCP> Organization: IEEE P1003 Portable Operating System for Computer Environments Committee Lines: 21 Approved: jsq@sally.utexas.edu