This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ctor style cast vs c style cast
- From: Andreas Schwab <schwab at suse dot de>
- To: "Peter A. Felvegi" <petschy at praire-chicken dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 14 Dec 2007 10:38:59 +0100
- Subject: Re: ctor style cast vs c style cast
- References: <4761EAFF.1030801@praire-chicken.com>
"Peter A. Felvegi" <petschy@praire-chicken.com> writes:
> today i've run into this: if i cast a double value to an unsigned int
> using the C style cast when passing it to printf, it's fine. however, if
> i use the ctor style cast, i get a compile error.
This question is off-topic here, please use gcc-help@gcc.gnu.org in
future. Functional cast notation [expr.type.conv] only allows a single
simple-type-specifier, but unsigned int isn't. Use static_cast<unsigned
int> instead.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."