Xref: utzoo comp.windows.x:33307 comp.windows.x.motif:2046 comp.windows.open-look:716
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!tdatirv!sarima
From: sarima@tdatirv.UUCP (Stanley Friesen)
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: <155@tdatirv.UUCP>
Date: 26 Feb 91 16:34:13 GMT
References: <1991Feb19.210822.26826@visix.com> <1991Feb20.170617.15372@cs.umn.edu> <TOML.91Feb20110922@marvin.Solbourne.COM> <1991Feb25.213202.4591@visix.com>
Reply-To: sarima@tdatirv.UUCP (Stanley Friesen)
Followup-To: comp.windows.x
Organization: Teradata Corp., Irvine
Lines: 19

In article <1991Feb25.213202.4591@visix.com> amanda@visix.com (Amanda Walker) writes:
<toml@marvin.Solbourne.COM (Tom LaStrange) writes:
<Uh, you *do* have an exception handling scheme, don't you?
...
<Which, actually, brings me to another point.  We've found that using
<an Ada-style (well, MacApp-style, actually) exception handler really
<cleans up our code, and makes it more robust at the same time.  This
<is another problem I have with C++, since it is much harder to write
<a library for it than it is in C.  Ideally, you'd want destructors
<to get called even when a scope is exited via an exception.

This is exactly why the ANSI C++ committee is *seriously* considering
adding exceptions to C++.  [I believe that ATT's just-released cfront 3.0
contains just such a mechanism].
I am not sure if it is Ada/MacApp style of not, it is rather similar to the
exception mechanism in Eiffel.
-- 
---------------
uunet!tdatirv!sarima				(Stanley Friesen)