[Sbcl-devel] ASDF 2.016.2
Faré
I introduce some non-trivial pathname changes.
On RMCL, ASDF sees strings as "/posix/namestrings/" in its configuration.
if you want OS9-style pathnames, they are #p"that:a:way:". You can thus
both trivially share your configuration with other implementations, and
just as trivially use MCL-specific paths.
For logical pathnames, I implemented my "harder way" plan
from previous email:
> make extra effort when using DIRECTORY against logical pathnames
> to always reconstitute LPNs from the PPNs given by directory, and
> drop the reconstituted results if they don't resolve to the same thing.
In other words, if I compute (directory #p"FOO:CL;BAR;"),
and find a file #p"/home/baz/cl/bar/quux.asd", the file will be kept
only if (make-pathname :name "quux" :type "asd" :defaults #p"FOO:CL;BAR;")
has the previous as its truename. And similarly when walking directories.
I believe this restriction is not a problem in practice, and
will keep things somewhat sane.
And no, it's probably still not a good idea to try mix logical pathnames
and mixed-case physical pathnames, as the result is highly non-portable.
Also removed *system-cache* and getuid, which were bad ideas that
never worked (and if anyone is using either, he'll thank me for making
him stop).
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
I believe in God, only I spell it Nature. — Frank Lloyd Wright
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Sbcl-devel mailing list
Sbcl-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sbcl-devel
Pascal Costanza
On 12 Jun 2011, at 07:12, Faré wrote:
> Regarding RMCL and logical pathnames, please test 2.016.2.
> I introduce some non-trivial pathname changes.
>
> On RMCL, ASDF sees strings as "/posix/namestrings/" in its configuration.
> if you want OS9-style pathnames, they are #p"that:a:way:". You can thus
> both trivially share your configuration with other implementations, and
> just as trivially use MCL-specific paths.
>
> For logical pathnames, I implemented my "harder way" plan
> from previous email:
>> make extra effort when using DIRECTORY against logical pathnames
>> to always reconstitute LPNs from the PPNs given by directory, and
>> drop the reconstituted results if they don't resolve to the same thing.
>
> In other words, if I compute (directory #p"FOO:CL;BAR;"),
> and find a file #p"/home/baz/cl/bar/quux.asd", the file will be kept
> only if (make-pathname :name "quux" :type "asd" :defaults #p"FOO:CL;BAR;")
> has the previous as its truename. And similarly when walking directories.
> I believe this restriction is not a problem in practice, and
> will keep things somewhat sane.
I'm not sure if I understand all the implications of this change, so I'm hesitating to applaud this. I don't think it should be ASDF's job to fix this particular problem.
Pascal
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.
Faré
>> and find a file #p"/home/baz/cl/bar/quux.asd", the file will be kept
>> only if (make-pathname :name "quux" :type "asd" :defaults #p"FOO:CL;BAR;")
>> has the previous as its truename. And similarly when walking directories.
>> I believe this restriction is not a problem in practice, and
>> will keep things somewhat sane.
>
> I'm not sure if I understand all the implications of this change, so I'm hesitating to applaud this. I don't think it should be ASDF's job to fix this particular problem.
>
to not commute with the setting of name and type:
symlinks and clever pathname mappings to wholly different files;
mapping of type fasl to implementation-specific type, etc.
But for the specific sake of searching for .asd files,
these reasons do not apply, and it's safer to avoid such cases:
indeed, since the name of a .asd file has to match the name of the
defsystem inside it, it's probably best to avoid looking
for system "foo" in a file named "bar.c".
Therefore, I think it's not wholly inappropriate
for ASDF to do this filtering.
As for filtering directory names — a bit ugly,
but required by the behavior of DIRECTORY.
If you think you must fix the spec and all implementations — good luck.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org
You have the capacity to learn from mistakes. You'll learn a lot today.
Pascal Costanza
On 12 Jun 2011, at 17:42, Faré wrote:
> If you think you must fix the spec and all implementations — good luck.
I have had very good and very positive experiences in that regard, as part of my work on Closer to MOP. Thank you very much.
Pascal
--
Pascal Costanza
The views expressed in this email are my own, and not those of my employer.