This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/12961] Problem with generic complex constructor
- From: "gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 10 Nov 2003 09:45:37 -0000
- Subject: [Bug libstdc++/12961] Problem with generic complex constructor
- References: <20031108091954.12961.Yves.Renard@gmm.insa-tlse.fr>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gdr at integrable-solutions dot net 2003-11-10 09:45 -------
Subject: Re: Problem with generic complex constructor
"Yves dot Renard at gmm dot insa-tlse dot fr" <gcc-bugzilla@gcc.gnu.org> writes:
| But I think, the problem is that the template definition should be
| complex(const _Tp& = _Tp(), const _Tp & = _Tp(0));
I can't understand that "should". If your sscalar type behaves in
such a way that T() is different from T(0), then you're in trouble and
that isn't the library's fault. See the standard requirement on
numeric types.
[...]
| The problem with QD is that the default constructor does not initialize the
| number to zero.
That is a flaw design in QD then.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12961