Xref: utzoo comp.windows.x:33223 comp.windows.x.motif:2028 comp.windows.open-look:696 Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.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: <1991Feb25.213202.4591@visix.com> Date: 25 Feb 91 21:32:02 GMT References: <1991Feb19.210822.26826@visix.com> <1991Feb20.170617.15372@cs.umn.edu> Organization: Visix Software Inc., Reston, VA Lines: 22 toml@marvin.Solbourne.COM (Tom LaStrange) writes: >How do you signal a failure when using a constructor? The same way you signal any other failure... Uh, you *do* have an exception handling scheme, don't you? Using magic return codes is so ... passe :). 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. Of course, you can always do it C-style, but then what's the point of using C++? -- Amanda Walker amanda@visix.com Visix Software Inc. ...!uunet!visix!amanda -- "This is a basic principle of the universe known as `The Law of the Cussedness of Nature.'" --W. Kauzmann