This is the mail archive of the
mailing list for the Archer project.
Re: C++ Exceptions Status
- From: Tom Tromey <tromey at redhat dot com>
- To: Phil Muldoon <pmuldoon at redhat dot com>
- Cc: Project Archer <archer at sourceware dot org>
- Date: Wed, 06 Aug 2008 16:16:19 -0600
- Subject: Re: C++ Exceptions Status
- References: <48999B3C.firstname.lastname@example.org>
- Reply-to: Tom Tromey <tromey at redhat dot com>
>>>>> "Phil" == Phil Muldoon <email@example.com> writes:
Phil> I've written this up to accompany the call today.
Thanks. I'm still reading most of this but wanted to address one
particular thing sooner.
Phil> The issue that I am currently wrestling with is how specific is this
Phil> unwind and exception work to C++? Are Java and Python exceptions
Phil> handled in the same way? And how can we avoid language specific
Phil> semantics in very general commands like "next"? Can we?
Our primary focus is C++ and C (though we don't talk about the latter
much since it works well :).
Debugging Python or other languages -- let's simply not worry about
it. If we need this someday (I dunno, we might), it will take an
special effort. Debugging an interpreted language would require far
more than fixes to exception handling -- it would also require changes
to stack tracing, to breakpoint setting, to expression parsing and/or