Re: asdf and relative names

(Assuming the response was meant for the list)

2008/9/3 Richard M Kreuter <[email protected]>:
>> At ITA, we've been happily using the attached file to allow names such
>> as "foo/bar/baz" to be used for component names, either modules or
>> files. It works great for us, and allows to portably use #\/ to denote
>> relative pathnames where the character was previously forbidden in
>> portable systems.
>
> Why aren't you calling PARSE-NAMESTRING on the string?  Constructing a
> pathname from substrings you parse manually will yield different
> results on different Lisps in various cases.
>
The whole point of the exercise is that for .asd files to be portable,
you do NOT want to rely on non-portable PARSE-NAMESTRING to interpret
the relative names of modules and other components. That ASDF should
interpret / as a directory separator in an implementation-independent
way is a feature that makes / useful at all in portable .asd files.
Relying on PARSE-NAMESTRING means that you have to requiring different
module names on different implementations - which completely defeats
the purpose.

[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
You may easily play a joke on a man who likes to argue -- agree with him.
                -- Edgar Waston Howe

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/