Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!twg.com!david
From: david@twg.com (David S. Herron)
Newsgroups: comp.unix.sysv386
Subject: Re: 14 character limitation in filenames
Message-ID: <8638@gollum.twg.com>
Date: 13 Feb 91 03:13:08 GMT
References: <20711@hydra.gatech.EDU> <1991Feb1.003532.15719@NCoast.ORG> <1991Feb02.232049.17438@scuzzy.in-berlin.de>
Organization: The Wollongong Group, Palo Alto, CA
Lines: 29

In article <1991Feb02.232049.17438@scuzzy.in-berlin.de> src@scuzzy.in-berlin.de (Heiko Blume) writes:
>allbery@NCoast.ORG (Brandon S. Allbery KB8JRR) writes:
>>"Silliness"?  I still fail to understand why everyone wants to be able to
>>create files with humongous names --- I don't enjoy typing 14 character file
>>names (but don't want to decrease that size, there *is* a tradeoff here), the
>>30-plus-character names I've seen in use on some BSD systems don't appeal at
>>all.

I generally don't personally use file names more than about 20-30 characters.
Things like the <ESC>-to-complete-file-names help a lot in that regard ...

Looooooong file names *do* give the possibility for software to use all
that extra room for expansion in interesting ways.  The reason you might
want to put data into file names are for things like using the file system
as an index to a data base.

No I don't have any software around which does that.  But it's nice to
know that it can be done, no?

Supporting FLEXNAMES in the file system is useful in exactly the same
way as putting FLEXNAMES in the compiler is.

What I wanna know is why there should be a limit to file name length
in the first place?
-- 
<- David Herron, an MMDF & WIN/MHS guy, <david@twg.com>
<- Formerly: David Herron -- NonResident E-Mail Hack <david@ms.uky.edu>
<-
<-	MS-DOS ... The ultimate computer virus.