Menu
▾
▴
[ clisp-Bugs-3124235 ] hex format directive ignores upper/lower case distinction
|
From: SourceForge.net <no...@so...> - 2010-12-15 15:20:06
|
Bugs item #3124235, was opened at 2010-12-01 04:58 Message generated for change (Comment added) made by sf-robot 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: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Andrew Pennebaker (mcandre) Assigned to: Sam Steingold (sds) 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: SourceForge Robot (sf-robot) Date: 2010-12-15 15:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Bruno Haible (haible) Date: 2010-12-11 16:00 Message: See CLHS 22.3.2.5 Tilde X: Hexadecimal <http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_22-3-2-5.html>: FORMAT ~X is like WRITE with *PRINT-BASE* being 16. In <http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/var_stprint-b_rint-radixst.html> you have a couple of examples where hexadecimal printing produces uppercase ASCII letters and none where it produces lowercase ASCII letters. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2010-12-01 14:25 Message: why do you expect "a" there? could you please quote the relevant part of the standard? ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2010-12-01 14:25 Message: This bug report is now marked as "pending"/"invalid". This means that we think that the problem you report is not a problem with CLISP. Unless you - the reporter - act within 2 weeks, the bug will be permanently closed. Sorry about the inconvenience - we hope your silence means that you agree that this is not a bug in CLISP. ---------------------------------------------------------------------- Comment By: Andrew Pennebaker (mcandre) Date: 2010-12-01 07:59 Message: Thank you. I got the impression from skimming Practical Common Lisp that ~X was uppercase and ~x was lowercase. Had I scrolled down, I would have seen the bit about ~(...~). ---------------------------------------------------------------------- Comment By: Andrew Pennebaker (mcandre) Date: 2010-12-01 07:59 Message: This bug report is now marked as "pending"/"works for me". This means that we think that we cannot reproduce the problem and cannot do anything about it. Unless you - the reporter - act within 2 weeks (e.g., by submitting a self-contained test case or answering our other recent requests), the bug will be permanently closed. Sorry about the inconvenience - we hope your silence means that you are no longer observing the problem either. ---------------------------------------------------------------------- Comment By: Pascal J. Bourguignon (informatimago) Date: 2010-12-01 05: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 05: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 |
