Re: [STUMP] [PATCH] Fix module paths on sbcl

[Julian Stecklina]

Ivy Foster <address@hidden> writes:

> So it turns out that sbcl doesn't like it when it's asked to `(load ...)' a 
> path
> instead of a string. This lets sbcl users use the new module.lisp stuff.

Oh, I seem to have missed this mail and fixed the same bug in my tree. But...

> +  (make-pathname :directory #+sbcl (namestring *contrib-dir*)
> +                            #-sbcl *contrib-dir*
> +                 :name name
> +                 :type "lisp"))

This still looks wrong. The most portable way would be to pass a list of
strings or to use merge-pathnames:

(merge-pathnames (make-pathname :name name
                                :type "lisp")
                 *contrib-dir*))

Regards,
-- 
Julian Stecklina

Well, take it from an old hand: the only reason it would be easier to
program in C is that you can't easily express complex problems in C,
so you don't. - Erik Naggum (in comp.lang.lisp)