Login | Register   
LinkedIn
Google+
Twitter
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX


Tip of the Day
Language: C++
Expertise: Intermediate
Jan 30, 2006

Avoiding Ambiguity in Math.h functions While Porting from 32-bit to 64-bit

One of the most common errors while porting from 32-bit Code to a 64-bit code is in the use of Math.h library functions.

Suppose you use a call to the pow function and get an error such as "Ambiguous call to a overloaded member function" in the 64-bit compiler. The reason is that a few more overloaded functions have been added to the math.h making it ambiguous for the compiler to understand which function to call. For example, pow now has seven overloads:


long double pow(long double,int)
long double pow(long double,long double)
float pow(float,int)
float pow(float,float)
double pow(int,int)
double pow(double,int)
double pow(double,double)
The straightforward solution to this problem is to call the methods with the explicit parameter typecast. So the call now looks like:

pow((float)11,(float)2.0)
or:

pow((double)11,(double)2.0)
... and so on and so forth.

Modifying your existing 32-bit code for explicit parameters works with both 32-bit and 64-bit code and helps make porting a bit less painful.

C.V. Ram
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap