Xref: utzoo comp.windows.x:33339 comp.windows.x.motif:2055 comp.windows.open-look:722 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!visix!amanda From: amanda@visix.com (Amanda Walker) Newsgroups: comp.windows.x,comp.windows.x.motif,comp.windows.open-look Subject: Re: Toolkit for Open Look *and* OSF/Motif Look and Feel Message-ID: <1991Feb27.185044.24581@visix.com> Date: 27 Feb 91 18:50:44 GMT References: <1991Feb25.213202.4591@visix.com> <155@tdatirv.UUCP> Organization: Visix Software Inc., Reston, VA Lines: 28 sarima@tdatirv.UUCP (Stanley Friesen) writes: >This is exactly why the ANSI C++ committee is *seriously* considering >adding exceptions to C++. Good ho. This will help a lot. One of the problems with C++ is that the control structures didn't catch up to the data structures :). >I am not sure if it is Ada/MacApp style of not, it is rather similar to the >exception mechanism in Eiffel. Well, I'm not very familiar with Eiffel yet. What we implement is a dynamic exception handler stack, which, in effect gives you the equivalent of Lisp's 'catch/throw/unwind-protect' primitives. That is to say, exception handlers can catch and reraise exceptions, as well as perform arbitrary actions (such as deallocating memory, for example) when their scope is exited, even for exceptions they do not otherwise handle. Fairly simple, and quite effective. Back on topic, though... some kind of exception handling (even as rudimentary as I've just described) makes both the implementation and the API of a toolkit much cleaner (not to mention the debugging benefits...). -- Amanda Walker amanda@visix.com Visix Software Inc. ...!uunet!visix!amanda -- "Duct tape is like the force: it has a light side, and a dark side, and it holds the universe together." --Carl Zwanzig