[Openmcl-devel] Directory and symlinks

james anderson james.anderson at setf.de
Sun Nov 13 12:40:37 PST 2011

good evening;

On 2011-11-13, at 20:19 , Zach Beane wrote:

> Gary Byers <gb at clozure.com> writes:
>> On Fri, 11 Nov 2011, Zach Beane wrote:
>>> In light of CCL's interpretation of the standard'
>> As I noted the other day, SBCL, AllegroCL, and LispWorks (at least)
>> seem to share this interpretation.
> SBCL no longer shares the interpretation, and I could not reproduce  
> the
> result on Allegro CL 8.2 for Linux. What Allegro version and platform
> are you using?
> Here's a survey of implementations. The directory structure looks like
> this:
>     src/bar/foo.asd
>     foo/bar -> ../src/bar
>     foo/baz/quux.asd

what happens when the link is to '../src/bar/' ?

if the results are the same, at least one of the listed  
implementations does something which would appear to be at odds with  
its documentation.

> So, seven implementations return results in a way that are very
> convenient to me, and two don't. I don't think interpretation of the
> spec is a matter of blessing majority practice (I mostly use SBCL,  
> after
> all), but when making a point regarding how other implementations act,
> it can be useful to have the full picture.
> Zach
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel

More information about the Openmcl-devel mailing list