This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: wrong warning on private constructors
- From: Stefan Seefeld <stefan dot seefeld at orthosoft dot ca>
- To: gcc at gcc dot gnu dot org
- Date: Tue, 17 Dec 2002 17:14:49 -0500
- Subject: Re: wrong warning on private constructors
- References: <5547bbc1615d5c2e5fb830ca23d1ee443dff994b@> <m3y96oxswz.fsf@uniton.integrable-solutions.net>
Gabriel Dos Reis wrote:
I think the logic used in the implementation is broken. I'm not
sanguine about dropping the warning (although I suspect that people
would suddendly fill reports). Maybe a workable way would be to find
an exhaustive criterioon (no friends, no public memeber function) that
would make that warning unbroken.
oh, sure. It's certainly possible from within gcc to test whether
the class is usable, and to emit that warning in case it *really* is
not. I just thought that not emitting that warning is better than
emitting it always, which is wrong.
Thanks,
Stefa