purify 4.1 and egcs still appear to be incompatible.

[Brad M. Garcia]

On Tue, 17 Feb 1998, Martin von Loewis wrote:

> Under optimization, g++ will recognize that this is all nonsense,
> and remove it.
> 
> Giving these structures empty constructors is a much easier way, as
> Ian suggests.

Sorry if this is a stupid question, but I just want to make sure I
understand this.

If I take all my classes that use this default copy constructor to copy
a single bogus byte, and specifically give them a copy constructor (one
which does nothing), I should stop getting these purify errors?

And furthermore, when I compile with optimization, the resulting code
should be _no_ different either way?

I'll test this tomorrow to see if it works, but I value an informed
opinion too.

Brad Garcia
   ___/  __ /  __ /  ___/ "Being the Linux of digital media
  __/   /  /  / _/  __/    would be a very good life."
_/    ____/ _/ _| ____/      - Jean-Louis Gassee, CEO of Be, Inc.