[ clisp-Bugs-3124235 ] hex format directive ignores upper/lower case distinction

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

Bugs item #3124235, was opened at 2010-12-01 05:58
Message generated for change (Comment added) made by informatimago
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3124235&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: Andrew Pennebaker (mcandre)
Assigned to: Bruno Haible (haible)
Summary: hex format directive ignores upper/lower case distinction

Initial Comment:
(format nil "~x" 10) => "A"

when it should evaluate to "a".

Specs:

GNU CLISP 2.49 (2010-07-07) (built 3499977130) (memory 3499977680)
Software: GNU C 4.2.1 (Apple Inc. build 5646)

That's clisp x2.49 (via MacPorts) on Mac OS X 10.6.5 / MacBook Pro 5,1.

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

Comment By: Pascal J. Bourguignon (informatimago)
Date: 2010-12-01 06:48

Message:
(Sorry for the previous comment it was intended for another bug report).

First,  CLHS is clear about directive characters:
http://www.lispworks.com/documentation/HyperSpec/Body/22_c.htm

   The case of the directive character is ignored. 

If you want to force lowercase or upper case, use ~:( or ~:@(


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

Comment By: Pascal J. Bourguignon (informatimago)
Date: 2010-12-01 06:42

Message:
You can use *load-pathname* to get the script name.


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

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