Re: Structured exception information

[Ray Blaak <rAYblaaK@STRIPCAPStelus.net>]

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
> 
> > However, I have yet to see an _actual_ implemention of View that is
> > not equivalent to "write this string to a device". So I do _not_
> > anticipate changing that implementation.
> 
> I have to take this back, partly. Ray Blaak posted an example where
> View would do:
> 
> Write Short_Description to immediate display device
> Write Detailed_Description to log device
> 
> So View would take two strings, rather than one.
> 
> But the data is still strings, so the rest of my post stands.

Another twist on this that I have actually used is in the case of handling
parse errors when implementing editors in an IDE.

The exception certainly contained strings (since errors fundamentally have to
be shown to a human at some point), but also contained source locations
(line/col and absolute offsets) as integer fields, so that one not need to
parse them out.

The source location would be used such that the error message would appear in
some sort of log window, and double clicking on the error would auto-navigate
to the offending snippet of code where the error occurred in the source or
input file.

So, certainly the data is fundamentally strings, but can readily contain
auxiliary information that allows further processing to occur.

-- 
Cheers,                                        The Rhythm is around me,
                                               The Rhythm has control.
Ray Blaak                                      The Rhythm is inside me,
rAYblaaK@STRIPCAPStelus.net                    The Rhythm has my soul.