Search:

I do not understand what you are trying to say in the sentence quoted above, so kindly explain and elaborate.

What I meant is that since a named conversion function forces the user of the type to...

Yes, it is like declaring copy constructors and copy assignment operators private in order to disable copying.


Ah, but what if the type you are designing is intended for use (or just might be...

You still have to determine what to invoke, and have to update your code if there are additions to the target type interface (for class types not under your control, at least), even if these would...

I do not see what "it isn't a counter" has to do with anything. Concerning the error: I ignored that part due to the disclaimer that only C++ Coding Standards incorporates corrections, but thinking...

I'd say that you are trying to provide an excuse for lazy programmers to use such implicit conversions even when they are dangerous.


I'd say that in those cases you usually actually want this...

For a good example of why one should avoid writing such conversion functions, read GotW #19: Automatic Conversions.

EDIT:
Actually, I notice that cpjust linked to an online copy of a book that...