Re: ctor style cast vs c style cast

2 msg	libgfortran, libgomp not compiled with BOOT_CFL...
7 msg	HIRLAM with -ftree-loop-distribution.
1 msg	How to interpret the automaton output during gc...
3 msg	Fails for SPEC2006 using -O3 -ftree-parallelize...
1 msg	gcc-4.3-20071214 is now available
4 msg	Adding new dwarf encoding formats for complex i...
7 msg	HIRLAM and -ftree-loop-linear
7 msg	Ada ACATS Failures on SVN Trunk
2 msg	how to compile gcc4 on cygwin?
1 msg	help pls, about gcc-3.0.1 on HP unix

ctor style cast vs c style cast
\ Peter A. Felvegi (14 Dec 2007)
. \ David Fang (14 Dec 2007)
. \ Andreas Schwab (14 Dec 2007)

1 msg	Re: Status of simulator targets after dataflow ...
1 msg	Poisonous people
1 msg	gcc-4.2-20071212 is now available
28 msg	[RFC] WHOPR - A whole program optimizer framewo...
2 msg	Re: Something is broken in repack. Why not with...
5 msg	branch delay slots
3 msg	porting gcc to tic54x
1 msg	error: no data type for mode '..'
1 msg	Bootstrap Failure in trunk (fortran)

Subject:	Re: ctor style cast vs c style cast
Group:	Gcc
From:	Andreas Schwab
Date:	14 Dec 2007

"Peter A. Felvegi" <petschy> 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 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 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."