BorlandTalk.com

Guest

I'm seeing a difference in how overload resolution works between C++
Builder 5 and Builder 6 which is causing an issue with several
applications I need to upgrade.

I created a simple console app below and used the debugger to watch
which function is called/which one gets compiled out.
//---------------------------------------------------------------------------

#pragma hdrstop
#include <string>

using namespace std;

bool ExecuteThis(string Test){
return false;
}

bool ExecuteThis(bool Test){
return true;
}

#pragma argsused
int main(int argc, char* argv[])
{
ExecuteThis("asdfasdf");
return 0;
}
/---------------------------------------------------------------------------
Under Builder 5, the string version of ExecuteThis gets called unless
the string function does not exist. In which case, the string version
is called.
Under Builder 6 (using both the old RogueWave and new string template)
the bool version of ExecuteThis gets called, unless the bool version
does not exist. In which case, the string version is called.

Is there a setting somewhere to make the Builder 6 compiler overload
resolution behave like the Builder 5 compiler under this scenario so
it always considers the string function the better candidate than the
bool version like it did in Builder 5? I have a substantial amount of
code that expects the implicit string conversion to occur like this.
Thanks!

Zara · Guest

On 25 Apr 2007 05:15:24 -0700, megatillo (AT) hotmail (DOT) com wrote: