Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!husc6!wjh12!redsox!campbell
From: campbell@redsox.UUCP (Larry Campbell)
Newsgroups: comp.lang.c++
Subject: Re: Sharing classes
Keywords: comp.sources.misc, comp.sources.c++
Message-ID: <599@redsox.UUCP>
Date: 9 Mar 89 11:58:21 GMT
References: <1989Feb27.090941.18193@LTH.Se> <2491@crete.cs.glasgow.ac.uk> <7101@thorin.cs.unc.edu> <8688@paris.ics.uci.edu> <3748@geaclib.UUCP> <19887@uflorida.cis.ufl.EDU>
Reply-To: campbell@redsox.UUCP (Larry Campbell)
Organization: The Boston Software Works, Inc.
Lines: 15

Sharing classes, in the sense of making classes available that are nearly
universally useful, will be very difficult until exception handling is
in the language and some sort of convention as to how to use the feature
has been widely adopted.

The problem is that classes need to report errors.  Writing to standard
output or standard error is *not* an acceptable way to report errors.
(Think of background tasks without stdout or stdout;  think of operating
systems besides UNIX;  think of real-time or embedded or distributed systems.)

Pining for cfront v2.0 (any rumors about release dates?)...
-- 
Larry Campbell                          The Boston Software Works, Inc.
campbell@bsw.com                        120 Fulton Street
wjh12!redsox!campbell                   Boston, MA 02146