Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!csn!stan!garya
From: garya@Solbourne.COM (Gary Aitken)
Newsgroups: comp.windows.x
Subject: Re: Toolkit for Open Look *and* OSF/Motif Look and Feel
Message-ID: <1991Feb27.004813.22802@Solbourne.COM>
Date: 27 Feb 91 00:48:13 GMT
Organization: Solbourne Computer, Inc.
Lines: 17

> > 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 :).

Except that C++ has no exception handling mechanism.
Every C++ guru I've talked to admits this a problem.  If you know a way around
it, I'd be delighted to see it.  The constructor has to unwind and free up
all the malloc'd space, both in user code and C++ generated code.
-- 
Gary Aitken

Solbourne Computer Inc.    ARPA: garya@Solbourne.COM
Longmont, CO               UUCP: !{boulder,sun}!stan!garya