🚀 go-pugleaf

In article <TOM.96Feb28161011@amber.ssd.csd.harris.com> tom@ssd.hcsc.com
(Tom Horsley) writes:

|> Someone showed me the "function try blocks" in the draft standard today, and
|> I immediately began to wonder what happens if the function in question is
|> a constructor and one of the exceptions I catch is "out of memory". If I
|> have something like:

|> Fred::Fred(...) try : initializers... {
|>    code goes here...
|> } catch ...

|> And then I say "new Fred" and run out of memory.

|> I know some existing C++ implementations call the memory allocation code from
|> inside the constructor and others call it from the place in the code where
|> 'new' was invoked. So in different implementations today, the exception
|> might actually occur in the caller or the constructor itself.

Where the compiler actually generates the call to the memory allocator
is irrelevant.  The compiler is required to generate code whose
`observable behavior' is as if the call to the memory allocator preceded
the call to operator new.

|> Does the standard say who gets the memory exception? Or is running out of
|> memory even an exception? Or is this simply left undefined?

The exception (bad_alloc) is thrown by operator new.  The first place it
becomes catchable is in the new expression.  The constructor is never
called (as far as the observable behavior is concerned).
-- 
James Kanze           (+33) 88 14 49 00          email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs Bourgeois, 67000 Strasbourg, France
Conseils, études et réalisations en logiciel orienté objet --
              -- A la recherche d'une activité dans une region francophone


[ comp.std.c++ is moderated.  To submit articles: Try just posting with your
                newsreader.  If that fails, use mailto:std-c++@ncar.ucar.edu
  comp.std.c++ FAQ: http://reality.sgi.com/austern/std-c++/faq.html
  Moderation policy: http://reality.sgi.com/austern/std-c++/policy.html
  Comments? mailto:std-c++-request@ncar.ucar.edu
]