This is the mail archive of the gcc@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]
Other format:	[Raw text]

Re: cannot pass objects of non-POD type

From: Jack Lloyd <lloyd at randombit dot net>
To: gcc at gcc dot gnu dot org
Date: Wed, 24 Oct 2007 15:39:06 -0400
Subject: Re: cannot pass objects of non-POD type
References: <20071024135520.61ceae8c.gateley@jriver.com> <de8d50360710241203yaafd5a2g4d3e262e8aea1895@mail.gmail.com> <20071024141311.46a742a8.gateley@jriver.com> <de8d50360710241215q43f6934ewa1feda89d3e9a21b@mail.gmail.com>

On Wed, Oct 24, 2007 at 12:15:03PM -0700, Andrew Pinski wrote:

> > a "real" illegal instruction, caused by g++ doing something different
> > that I expected with the String object as an argument? Or is the illegal
> > instruction just a "place marker" that is generated because I passed
> > a non-POD as an argument?
> 
> The latter.

Is there a reason it's not just an error, then? (As a user) I don't
see the point of something being a warning when the compiled code is
intentionally set up to crash.

-Jack

Follow-Ups:
- Re: cannot pass objects of non-POD type
  - From: Andrew Pinski

References:
- cannot pass objects of non-POD type
  - From: John Gateley
- Re: cannot pass objects of non-POD type
  - From: Andrew Pinski
- Re: cannot pass objects of non-POD type
  - From: John Gateley
- Re: cannot pass objects of non-POD type
  - From: Andrew Pinski

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