[Openmcl-devel] Lisp image filename.
lisp at davidb.org
Mon Oct 6 01:34:55 PDT 2008
Is there any particular reason for the distinction on darwin of naming
the image by tacking an ".image" onto the filename, and other
platforms that use an equivalent named file in uppercase?
The reason I ask is that I commonly work on Linux images running in a
VM on MacOS. Generally, my home directory is just mapped through to
the underlying HFS filesystem. With the case-paired filenames, I'm
not able to store CCL in my home directory, but must expand it
somewhere in a native filesystem.
It seems like things would be simpler overall to just use an extension
on the name, and allow things to work on any platform, even if the
filesystem happens to be case insensitive.
More information about the Openmcl-devel