Any other Python flaws?

[Hannah Schroeter]

Hello!

In article <3b2a94a6.591842855 at wa.news.verio.net>,
Bengt Richter <bokr at accessone.com> wrote:
>[...]

>>http://www.xanalys.com/software_tools/reference/HyperSpec/Body/chap-19.html

>Thanks for the link, although ISTM it focuses on regularizing path
>expressions relative to _existing_ file systems without creating a
>_new_ hierarchy, which is a key part of what I was trying to describe.

Just lookup the stuff on *logical* pathnames in subsection
19.3 Logical Pathnames...

>[...]

>_EXCEPT_ that they are trying to standardize _actual_ file systems
>whereas I was saying that you could define an _abstract_ tree of/for
>names totally independently, and then attach/mount things to standard
>places in that tree so that they can be accessed in known abstract
>tree locations irrespective of their actual file system tree locations
>or the pathnaming conventions of the particular OS/file system.

Now, my SBCL startup contains e.g. this:

(let* ((homedir (posix-getenv "HOME"))
       (translation (concatenate 'string homedir "/**/*")))
  (setf (logical-pathname-translations "home")
   `(("home:**;*.*.*" ,translation))))

Packages like CLOCC use logical pathname hosts like "clocc" and so
on for references to other files in that package.

>[...]

>Also, switching experimental stuff in and out would be made more
>flexible, I would anticipate, since changing a few lines in a
>configuration file could determine what shows up where.

Right, just as the (setf (logical-pathname-translations ...) ...)
stuff in my .sbclrc. And that can be more complicated translations
based on pattern matching instead of that simple one "translate
everything on host 'home' to be relative to my home directory".

Kind regards,

Hannah.