Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!att!dptg!ulysses!andante!alice!bs
From: bs@alice.UUCP (Bjarne Stroustrup)
Newsgroups: comp.lang.c++
Subject: Re: multiple destructors
Summary: storage class: beware of co-routines
Message-ID: <10042@alice.UUCP>
Date: 22 Oct 89 13:19:04 GMT
References: <1989Sep30.190719.3340@polyslo.CalPoly.EDU> <6590273@hplsla.HP.COM> <1989Oct21.182759.13138@paris.ics.uci.edu>
Organization: AT&T Bell Laboratories, Murray Hill NJ
Lines: 8



Ron Guilmette points out that by being clever you can deduce the storage
clas of an object from its address by knowing how your machine lays out
a program in memory. This is not only non-portable, but also unreliable
in the presense of a co-routine or lightweight process package because
these tend to have stacks in areas that to the simple single-thread layout
looks like free store.