This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: g++ 2.95.2 bug

To: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
Subject: Re: g++ 2.95.2 bug
From: Martin Sebor <sebor at roguewave dot com>
Date: Mon, 20 Dec 1999 12:12:35 -0700
CC: llewelly at 198 dot dsl dot xmission dot com, gcc-bugs at gcc dot gnu dot org, baus at roguewave dot com, pedretti at roguewave dot com
Organization: Rogue Wave Software, Inc.
References: <Pine.LNX.4.10.9912200010410.16024-100000@198.dsl.xmission.com> <199912201420.PAA00960@loewis.home.cs.tu-berlin.de>

"Martin v. Loewis" wrote:
> 
> > See 3.9 p2. I don't think references are PODs; How do you copy the bytes
> >   that make up a reference into an array of char?
> 
> That is more clearly explained in 3.9/9 (reference types are not
> object types) and 3.9/10 (references are not POD). See also 8.3.2/3:
> 
> # It is unspecified whether or not a reference requires storage (3.7).
> 
> Regards,
> Martin

Yes, I missed that, sorry. However then, is it not a bug in g++ that the
reference _is_ statically initialized if A does not have a ctor? I don't
see why this should make a difference.

Thanks
Martin

Follow-Ups:
- Re: g++ 2.95.2 bug
  - From: Martin v. Loewis

References:
- Re: g++ 2.95.2 bug
  - From: llewelly
- Re: g++ 2.95.2 bug
  - From: Martin v. Loewis

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]