Mail Archives: opendos/1997/02/03/15:42:25
[...]
>Have you folks thought about giving the inode number to 8.3 filenames?
>An LFN app might see C:\Really.Long\Path.with.lots.of.dos\file23.tar.gz
>and an 8.3 app would see C:i32456.dat.
Okay, so you download some documentation and save it:
introduction.txt
tutorial1.txt
tutorial2.txt
command_reference.txt
api_reference.txt
Now you want to browse it with your favourite file viewer. This isn't LFN
aware. You see:
i348562.dat
i116733.dat
i058322.dat
i928726.dat
i273628.dat
Now, which one was the tutorial? Ummmm...
A better solution is to use some sort of hashing. For example, the above under
GEOS would appear as:
introduc.000
tutorial.000
tutorial.001
command_.000
api_refe.000
...which is slightly more understandable. Of course, you lose the extension,
but GEOS doesn't use them. I hate to say this, but the Win95 way:
introd~1.txt
tutori~1.txt
tutori~2.txt
comman~1.txt
api_re~1.txt
...is probably the most intelligent way to go.
--
------------------- http://www-hons-cs.cs.st-and.ac.uk/~dg --------------------
If you're up against someone more intelligent than you are, do something
totally insane and let him think himself to death. --- Pyanfar Chanur
---------------- Sun-Earther David Daton Given of Lochcarron ------------------
- Raw text -