c++: implicit conversion order

Question

I've a (member-)fuction overloaded like this:

bool foo(bool);
int foo(int);
float foo(float);
...
std::string foo( std::string const&);

for a couple of build-in-types but not for const char*. Calling foo("beauty is only skin-deep");, to my big suprise, called the bool-variant of the foo function. This leads to my questions:

QUESTION: Is there a well defined implicit conversion order for build-in-types

NOT THE QUESTION: How to avoid implicit conversion. How evil is implicit conversion. ...

EDIT: removed question about implicit converstion order for user-defined-questions

It should be 1 question at a time so can you pick just one

EdChum
– EdChum

2015-05-29 09:17:42 +00:00
Commented May 29, 2015 at 9:17 — EdChum
– EdChum, Commented May 29, 2015 at 9:17

Hcorg · Accepted Answer · 2015-05-29 09:40:41Z

7

according to: http://en.cppreference.com/w/cpp/language/implicit_cast

all build-in conversions take place before user defined ones

pointer -> bool is a 'Boolean conversions' (needed for if(pointer) notation), last of 'numeric conversions'

'const char*' -> std::string is a 'user defined conversion' as from language point of view, std::string is a user defined type.

Unfortunately simplest solution is to write proper overload of fun(const char*), or to avoid fun(bool) vs fun(std::string) overloads

edited May 29, 2015 at 9:40

answered May 29, 2015 at 9:34

Hcorg

12.2k3 gold badges33 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

c++: implicit conversion order

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related