[ clisp-Bugs-3165355 ] load binds *load-pathname* incorrectly

[SourceForge.net <no...@so...>]

Bugs item #3165355, was opened at 2011-01-25 17:23
Message generated for change (Tracker Item Submitted) made by pcostanza
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3165355&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: ANSI compliance issue
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Pascal Costanza (pcostanza)
Assigned to: Bruno Haible (haible)
Summary: load binds *load-pathname* incorrectly

Initial Comment:
Here is a test case to illustrate the bug:

I have a file in /Users/costanza/Temp/test.lisp that contains the single line (print *load-pathname*).

Here is a session with clisp:

[1]> (setq custom:*parse-namestring-ansi* t)
T
[2]> (setf (logical-pathname-translations "temp")
	'(("**;*.*.*" "/Users/costanza/Temp/**/*.*")))
((#P"TEMP:**;*.*.*" "/Users/costanza/Temp/**/*.*"))
[3]> (load #P"temp:test.lisp")
;; Loading file /Users/costanza/Temp/test.lisp ...
#P"/Users/costanza/Temp/test.lisp" 
;; Loaded file /Users/costanza/Temp/test.lisp
T

The HyperSpec states that *load-pathname* is bound to the pathname denoted by the first argument to load, not to the translated physical pathname.

This seems to cause problems when trying to use ASDF 2 with logical pathnames.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3165355&group_id=1355