axiom-developer
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Axiom-developer] depsys


From: Gabriel Dos Reis
Subject: Re: [Axiom-developer] depsys
Date: 13 Oct 2006 08:39:07 +0200

Gabriel Dos Reis <address@hidden> writes:

| Tim --
| 
| I have a question about a difference in "load" behaviour bewteen a
| clean lisp image (GCL), and depsys (and any image derived from it).
| 
| In a clean image, when I say '(load "foo")', Lisp will try to search
| from the current directory -- just what is expected.
| 
| However, depsys will start search from $AXIOM/.. -- which is less expected.
| I spent quite lot of time figuring out where that behaviour is
| implemented in the files that make up depsys, but I was unsuccessful.
| Do you have an idea whether that behaviour is implemented?
| I looked many times at reroot, but could not deduce how it might be
| responsible.  It looks like there is an Axiom code that fundamentally
| changes GCL's usual load procedure.


Let me add this (from a debug session -- i hate those).

#0   APPLY {loc0=#<compiled-function 
system:universal-error-handler>,loc1=:error,loc2=nil,l...} [ihs=12]
#1   APPLY {loc0=#<compiled-function 
system:universal-error-handler>,loc1=:error,loc2=nil,l...} [ihs=11]
#2   LAMBDA {"/home/gdr/build/axiom/target/foo"=nil,} [ihs=8] 
#3   LOAD 
{loc0=#p"/home/gdr/build/axiom/target/foo.lsp",loc1=t,loc2=nil,loc3=:error,loc4=...}
 [ihs=7]
#4   EVAL {loc0=nil,loc1=nil,loc2=nil,loc3=#<compiled-function load>}
 [ihs=6]
#5   TOP-LEVEL 
{loc0=nil,loc1=0,loc2=0,loc3=nil,loc4=nil,loc5=nil,loc6=nil,loc7="/usr/local/lib...}
 [ihs=5]
#6   FUNCALL {loc0=#<compiled-function system:top-level>} [ihs=4]
NIL

So, it looks like some code effectively called the "real" load with the
wrong prefix.

-- gaby




reply via email to

[Prev in Thread] Current Thread [Next in Thread]