🚀 go-pugleaf

In article <199511021344.OAA02487@ssv4.dina.kvl.dk>
abraham@dina.kvl.dk (Per Abrahamsen) writes:

|> Can anyone explain to me why two doIt calls below select different
|> overloaded functions?

Compiler bug?

|> ------------- bug.C -------------
|> #include <iostream.h>
|> #include <string>

|> void doIt (string)
|> {
|>   cout << "Gotta string\n";
|> }

|> void doIt (bool)
|> {
|>   cout << "Gotta bool\n";
|> }

|> int main ()
|> {
|>   const char* const cp = "Hi!";
|>   doIt (cp);

Should call do( bool ), since a pointer converts to a bool implicitly
(and the conversion, which doesn't use any user defined conversions,
has precedence over the conversion to string, which involves calling
the constructor).

|>   doIt ("Hi!");

Same as above.

|>   return 0;
|> }

Rigorously speaking, it is an error.  On the other hand, I can easily
imagine a compiler having an extension which allows literal string
constants (like "Hi!") to be treated exactly as strings (even up to
correctly initializing static memory for a string statically).
-- 
James Kanze         Tel.: (+33) 88 14 49 00        email: kanze@gabi-soft.fr
GABI Software, Sarl., 8 rue des Francs-Bourgeois, F-67000 Strasbourg, France
Conseils en informatique industrielle --
                              -- Beratung in industrieller Datenverarbeitung