home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!kithrup!stanford.edu!ames!pacbell.com!att!att!allegra!alice!ark
- From: ark@alice.att.com (Andrew Koenig)
- Newsgroups: comp.lang.c++
- Subject: Re: complex classes and temporary destruction.
- Message-ID: <23592@alice.att.com>
- Date: 30 Aug 92 02:41:36 GMT
- Article-I.D.: alice.23592
- References: <MCGRANT.92Aug26232410@rascals.stanford.edu> <23563@alice.att.com> <64821@cup.portal.com> <23578@alice.att.com> <64878@cup.portal.com> <23587@alice.att.com> <64915@cup.portal.com>
- Reply-To: ark@alice.UUCP ()
- Distribution: world
- Organization: AT&T Bell Laboratories, Murray Hill NJ
- Lines: 16
-
- In article <64915@cup.portal.com> Aurelius@cup.portal.com (Mark Christian Barnes) writes:
-
- > If operator+(a,b) does, in fact, construct a temporary of type
- > String, then the compiler could determine its storage class,
- > perhaps based upon the storage class of the context to which
- > it is applied.
-
- Sorry, but I'm not going to tell you what operator+(a,b) does.
- I'm compiling it separately and giving you the object code to link
- in with your source code.
-
- Now, how is the compiler going to determine its storage class when
- it is compiling your program?
- --
- --Andrew Koenig
- ark@europa.att.com
-