Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (772 - 774 of 1030)

Ticket Resolution Summary Owner Reporter
#229 wontfix Recompiling Hemlock from the command line gives an error Gary Byers Rainer Joswig
Description

I have Openmcl started from the command line. No GUI.

I call:

(require "COMPILE-HEMLOCK")

and

(ccl::compile-hemlock t)

Read error between positions 18247 and 18805 in /Lisp/Implementations/openmcl/ccl/cocoa-ide/hemlock/src/macros.lisp.

Error: Reader error on #<BASIC-FILE-CHARACTER-INPUT-STREAM ("/Lisp/Implementations/openmcl/ccl/cocoa-ide/hemlock/src/macros.lisp"/9 ISO-8859-1) #x3000425DD39D>, near position 18805, within "gui::typeo":

Reference to unknown package "GUI".

#230 fixed Format ~F switches to scientific notation too soon Gary Byers Daniel Dickison
Description

ClozureCL seems to switch to scientific notation when doing format ~F before the number becomes too large or small.

Example:

CCL> (format t "~F" 0.0001)
1.0E-4  ;; Expected: 0.0001

From CLHS Section 22.3.3.1:

If w is omitted, then if the magnitude of arg is so large (or, if d is also omitted, so small) that more than 100 digits would have to be printed, then an implementation is free, at its discretion, to print the number using exponential notation instead, as if by the directive ~E (with all parameters to ~E defaulted, not taking their values from the ~F directive).

I read that to mean that if less than 100 digits would be printed, then it's required to use fixed point representation.

MCL 5.0 actually gets this right, so I/we/somebody might be able to merge code from MCL's Lib/format.lisp into CCL's file of the same name.

#231 duplicate Printing NSData objects does not obey *print-length* Gary Byers Ron Garret
Description

Printing NSData objects prints out the data contained within them, which is convenient, but it does not obey *print-length*. This gets particularly annoying when working with images, because if one accidentally prints a very large NSData object in the IDE (which often happens during error reporting when such an object has been passed in as an argument), Hemlock chokes, and the only way to recover is to kill the current listener and fire up a new one.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.