Why does pointer to int convert to void* but pointer to function convert to bool?

by

Based on the above, it is perfectly OK to convert a function pointer or a pointer to an int to a void* as well as bool.

The quotation states that a pointer to an object can be converted to cv void *. Functions are not objects, and this disqualifies the conversion to cv void *, leaving only bool.

However, given the choice of both, which one should a pointer convert to?

It should convert to const void * over bool. Why? Well, prepare for a journey that starts in Overload Resolution (§13.3 [over.match]/2). Emphasis mine, of course.

But, once the candidate functions and argument lists have been identified, the selection of the best function is the same in all cases:

— First, a subset of the candidate functions (those that have the proper number of arguments and meet
certain other conditions) is selected to form a set of viable functions (13.3.2).

— Then the best viable function is selected based on the implicit conversion sequences (13.3.3.1) needed to match each argument to the corresponding parameter of each viable function.

So what about these implicit conversion sequences?

Let’s jump over to §13.3.3.1 [over.best.ics]/3 and see just what an implicit conversion sequence is:

A well-formed implicit conversion sequence is one of the following forms:
— a standard conversion sequence (13.3.3.1.1),
— a user-defined conversion sequence (13.3.3.1.2), or
— an ellipsis conversion sequence (13.3.3.1.3).

We’re interested in standard conversions sequences. Let’s pop over to Standard Conversion Sequences (§13.3.3.1.1 [over.ics.scs]):

1 Table 12 summarizes the conversions defined in Clause 4 and partitions them into four disjoint categories: Lvalue Transformation, Qualification Adjustment, Promotion, and Conversion. [ Note: These categories are orthogonal with respect to value category, cv-qualification, and data representation: the Lvalue Transformations do not change the cv-qualification or data representation of the type; the Qualification Adjustments do not change the value category or data representation of the type; and the Promotions and Conversions do not change the value category or cv-qualification of the type. — end note ]

2 [ Note: As described in Clause 4, a standard conversion sequence is either the Identity conversion by itself (that is, no conversion) or consists of one to three conversions from the other four categories.

The important part is in /2. A standard conversion sequence is allowed to be a single standard conversion. These standard conversions are listed in Table 12, shown below. Notice that both your Pointer Conversions and Boolean Conversions are in there.

Table of standard conversions and their categories and ranks

From here, we learn something important: Pointer conversions and boolean conversions have the same rank. Remember that as we head to Ranking Implicit Conversion Sequences (§13.3.3.2 [over.ics.rank]).

Looking at /4, we see:

Standard conversion sequences are ordered by their ranks: an Exact Match is a better conversion than a Promotion, which is a better conversion than a Conversion. Two conversion sequences with the same rank are indistinguishable unless one of the following rules applies:

— A conversion that does not convert a pointer, a pointer to member, or std::nullptr_t to bool is
better than one that does.

We’ve found our answer in the form of a very explicit statement. Hooray!

More Related Contents:

  1. Program stopped working, when tried to run
  2. What is a smart pointer and when should I use one?
  3. What exactly is nullptr?
  4. Why should I use a pointer rather than the object itself?
  5. Which kind of pointer do I use when?
  6. Differences between unique_ptr and shared_ptr [duplicate]
  7. How to return a std::string.c_str()
  8. Pointers in c++ after delete
  9. Constexpr pointer value
  10. Get pointer to object from pointer to some member
  11. What is the difference between std::reference_wrapper and a simple pointer?
  12. std::unique_ptr with derived class
  13. Does ‘auto’ type assignments of a pointer in c++11 require ‘*’?
  14. Pointer to a given memory address -C++
  15. iterating with auto ref or an iterator
  16. How to emulate C array initialization “int arr[] = { e1, e2, e3, … }” behaviour with std::array?
  17. How do I combine hash values in C++0x?
  18. Removing item from vector, while in C++11 range ‘for’ loop?
  19. Is the ‘override’ keyword just a check for a overridden virtual method?
  20. Generic hash for tuples in unordered_map / unordered_set
  21. Why does cudaMalloc() use pointer to pointer?
  22. std::map, pointer to map key value, is this possible?
  23. C++0x thread interruption
  24. Is it legal to declare a constexpr initializer_list object?
  25. How can I expand call to variadic template base classes?
  26. What lasts after using std::move c++11
  27. Double-Checked Lock Singleton in C++11
  28. Why does std::forward have two overloads?
  29. Is a struct’s address the same as its first member’s address?
  30. Is there a proper ‘ownership-in-a-package’ for ‘handles’ available?

Leave a Comment