Hi Doug.

Thank you for taking the time to consider my point.

Please note that to handle syntax errors while fullPrinting
blocks, we need these errors to rise exceptions. As you
know, SyntaxErrors aren't Exceptions and thus we cannot use
the on:do: message to handle them in an simple way. That's
one of the reasons for the SyntaxErrorNotification change
set I sent to the list. SyntaxErrorNotifications use
SyntaxErrors for their default action and give us the
possibility to handle special cases conveniently.
SyntaxErrorNotifications could also be useful while
pretty-printing (stef?), finding selectors (alt-m/n), filing
in and browsing code from disc, etc.

/Leandro


Doug Way wrote:
> 
> Leandro Caniglia wrote:
> >
> > This change set implements the BlockContext>>fullPrintOn:
> > method. It is specially useful when combined with the
> > fullPrintOnInspector GOODIE, that replaces the use of
> > printString in inspectors with that of fullPrintString.
> 
> This is very cool!  I was thinking the other day that it would be nice for BlockContexts to actually display their (decompiled) source code when inspecting/debugging them. (now I can actually see what a sortBlock is doing, for example)
> 
> At first I was wondering if the fullPrintOn: scheme was really necessary to support this, but it does make some sense... a larger block of source code becomes tough to read when it's bunched together into one line.
> 
> - Doug Way
>   dway at riskmetrics.com