[Openmcl-devel] Question about SET-PPRINT-DISPATCH

[Robert Goldman]

I was trying to load up my colleague's NST unit testing library, and it
crashed on CCL 1.6 (on the Mac).

I found that the problem was a call to SET-PPRINT-DISPATCH with no
priority or table optional arguments.  A little poking around in the
debugger seemed to indicate that *PRINT-PPRINT-DISPATCH* was NIL.

Is this normal, is this a bug in CCL, or is this some load versus
compile thing that we don't understand properly (but note that the crash
occurred when loading the fasl, not compiling)?

thanks for any information,
r