Use static_cast on non-pointer POD instead of c style cast

Question

is there any reason for using static_cast on non pointer POD data types, like int, float, double?

float v = 100;
int x = (int) v vs int x = static_cast<int>v

Is there any reason/advantage on using that, I saw several answers that covers pointers, but plain POD data I could not find explicit answers about non-pointers.

`(int)v` is c. `static_cast(v)` is c++. – DimChtz Jul 27 '17 at 21:42 — DimChtz, Jul 27 '17 at 21:42
When in Rome, do as the Romans do. – Yuval Ben-Arie Jul 27 '17 at 21:43 — Yuval Ben-Arie, Jul 27 '17 at 21:43
C or C++. You cannot have both here. – Walter Jul 27 '17 at 21:45 — Walter, Jul 27 '17 at 21:45
@Walter fixed, removed C tag – Lefsler Jul 27 '17 at 21:49 — Lefsler, Jul 27 '17 at 21:49
@YuvalBen-Arie, makes sense, thanks – Lefsler Jul 27 '17 at 21:49 — Lefsler, Jul 27 '17 at 21:49

score 1 · Answer 1 · answered Jul 27 '17 at 21:51

The best reason I've heard is because you can grep for static_cast and know you will only find casts whereas (int) is much less specific about what's going on in that expression.

Also, C-style casts can remove or add const or volatile and change types without any warnings. If you try to static_cast a const pointer/reference type to a non-const pointer/reference type, you will get a compile error.

Use static_cast on non-pointer POD instead of c style cast

1 Answers1