Open GoogleCodeExporter opened 9 years ago
This is actually more general, applying to any prototype which cannot actually
be a
prototype for its "instances"; all literal types are included, as well as
"abstract
prototypes".
Probably the general solution involves re-structuring Slate's inheritance and
type
composition structure to avoid needing fake prototypes.
Original comment by BrianTRice
on 25 Nov 2009 at 7:15
The other perspective on this is that printOn: ought to generically
handle/capture
its own errors and go for truncated/safe output in that case. It's not clear
yet how
to perform this in a reasonable way.
Original comment by BrianTRice
on 25 Nov 2009 at 7:31
We're fixing a related issue today in printing by changing #printString to
handle
errors. This will help with debugger frames which fail printing things. We will
also
patch printOn: to handle SmallInteger specifically.
The class of errors (infinite recursion) between the print functions and entry
into
the debugger still needs to be addressed but is fairly low priority since most
of the
examples are contrived.
Original comment by google@timmy.tmbx.com
on 25 Nov 2009 at 8:08
Calls to #printOn: by the REPL and Debugger are also patched now, so for most
cases
this is fixed now.
Original comment by BrianTRice
on 30 Nov 2009 at 7:36
Original issue reported on code.google.com by
google@timmy.tmbx.com
on 1 Feb 2009 at 11:52