Hi Robert
Thanks for looking into this.
--
Earth First
(we'll take care of the other planets later)
On Jul 13, 2009, at 12:10 PM, Robert Goldman
wrote:
> I see the following when I try to load an asdf system now:
>
> Error loading #P"/Users/rpg/clinit.cl":
> While searching for system `asdf-
Nikodemus Siivola wrote:
> I haven't really thought about this properly, but why not just:
>
> (defun sysdef-central-registry-search (system)
> (let ((name (coerce-name system)))
> (block nil
> (dolist (dir *central-registry*)
> (let* ((defaults (probe-file (eval dir)))
>
I haven't really thought about this properly, but why not just:
(defun sysdef-central-registry-search (system)
(let ((name (coerce-name system)))
(block nil
(dolist (dir *central-registry*)
(let* ((defaults (probe-file (eval dir)))
(file (when defaults
Hi Robert,
I think our code passed in the ether. (I think that) The only
substantive difference between your version and mine is that mine
checks both type and name against ("" nil :unspecific) whereas yours
treats name and type differently. What's up with that?
thanks,
On Jul 13, 2009,
Partial fix for directory-pathname-p.
diff --git a/asdf.lisp b/asdf.lisp
index 6a8453b..851b5b5 100644
--- a/asdf.lisp
+++ b/asdf.lisp
@@ -433,7 +433,10 @@ which evaluates to a pathname. For example:
")
(defun directory-pathname-p (pathname)
- (and (member (pathname-name pathname) (list nil :
Agreed. If we claim that a directory is a pathname 'without" a
filename, then the three ways (so far) for a filename to be missing
are for it to be `nil`, the empty string or :unspecific, Here's
another crack at it and a sort-of test
> (defun directory-pathname-p (pathname)
> "A directory-
Richard M Kreuter wrote:
> Gary King writes:
>
>>> OK, I /have/ misdiagnosed this. The logic seems actually busted in
>>> directory-pathname-p. The problem is that, at least on allegro, you
>>> can get a valid directory pathname whose name component is neither
>>> NIL, nor :unspecific, but "" (t
Gary King wrote:
>> OK, I /have/ misdiagnosed this. The logic seems actually busted in
>> directory-pathname-p. The problem is that, at least on allegro, you can
>> get a valid directory pathname whose name component is neither NIL, nor
>> :unspecific, but "" (the empty string).
>
> Ugh,
>
>> (
Gary King writes:
> > OK, I /have/ misdiagnosed this. The logic seems actually busted in
> > directory-pathname-p. The problem is that, at least on allegro, you
> > can get a valid directory pathname whose name component is neither
> > NIL, nor :unspecific, but "" (the empty string).
>
> Ugh,
>
Robert Goldman wrote:
> Robert Goldman wrote:
>> I see the following when I try to load an asdf system now:
>>
>> Error loading #P"/Users/rpg/clinit.cl":
>> While searching for system `asdf-context`: `(MERGE-PATHNAMES systems/
>> /Users/rpg/lisp/asdf-install-systems/)`
>> evaluated to `/Users/rpg/l
> OK, I /have/ misdiagnosed this. The logic seems actually busted in
> directory-pathname-p. The problem is that, at least on allegro, you
> can
> get a valid directory pathname whose name component is neither NIL,
> nor
> :unspecific, but "" (the empty string).
Ugh,
> (member (pathname-nam
Robert Goldman wrote:
> I see the following when I try to load an asdf system now:
>
> Error loading #P"/Users/rpg/clinit.cl":
> While searching for system `asdf-context`: `(MERGE-PATHNAMES systems/
> /Users/rpg/lisp/asdf-install-systems/)`
> evaluated to `/Users/rpg/lisp/asdf-install-systems/syst
12 matches
Mail list logo
