Custom Query (1030 matches)

? (time (print (make-string 10000)))
""
(PRINT (MAKE-STRING 10000)) took 11,157,608 microseconds (11.157608 seconds) to run 
                    with 2 available CPU cores.
During that period, 10,291,164 microseconds (10.291164 seconds) were spent in user mode
                    868,038 microseconds (0.868038 seconds) were spent in system mode
70,577 microseconds (0.070577 seconds) was spent in GC.
 97,616 bytes of memory allocated.
 120 minor page faults, 12,281 major page faults, 0 swaps.
""

Note that the above was run with string highlighting disabled. When it's enabled, things get even slower. (See ticket #540.)

It would also be nice (and would be a resolution of this ticket as far as I'm concerned) to have something like *print-length* that applied to strings. I'm doing some database work that involves very long strings (megabytes) and it would be very nice not to have to manually kill the printing process whenever I accidentally print one of these monsters.

I'm calling this a "minor enhancement" because I can work around it myself by defining a print-object method on strings.

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.

On Win32 (and likely other 32-bit platforms):

? (read-from-string (format nil "~a" (make-random-state)))
> Error: value 1267438753 is not of the expected type (INTEGER 0 (2147483647)).
> While executing: INITIALIZE-MRG31K3P-STATE, in process listener(1).