15,861,168 members
Sign in
Sign in
Email
Password
Forgot your password?
Sign in with
home
articles
Browse Topics
>
Latest Articles
Top Articles
Posting/Update Guidelines
Article Help Forum
Submit an article or tip
Import GitHub Project
Import your Blog
quick answers
Q&A
Ask a Question
View Unanswered Questions
View All Questions
View C# questions
View C++ questions
View Javascript questions
View Visual Basic questions
View Python questions
discussions
forums
CodeProject.AI Server
All Message Boards...
Application Lifecycle
>
Running a Business
Sales / Marketing
Collaboration / Beta Testing
Work Issues
Design and Architecture
Artificial Intelligence
ASP.NET
JavaScript
Internet of Things
C / C++ / MFC
>
ATL / WTL / STL
Managed C++/CLI
C#
Free Tools
Objective-C and Swift
Database
Hardware & Devices
>
System Admin
Hosting and Servers
Java
Linux Programming
Python
.NET (Core and Framework)
Android
iOS
Mobile
WPF
Visual Basic
Web Development
Site Bugs / Suggestions
Spam and Abuse Watch
features
features
Competitions
News
The Insider Newsletter
The Daily Build Newsletter
Newsletter archive
Surveys
CodeProject Stuff
community
lounge
Who's Who
Most Valuable Professionals
The Lounge
The CodeProject Blog
Where I Am: Member Photos
The Insider News
The Weird & The Wonderful
help
?
What is 'CodeProject'?
General FAQ
Ask a Question
Bugs and Suggestions
Article Help Forum
About Us
Search within:
Articles
Quick Answers
Messages
Comments by Mike M.00 (Top 1 by date)
Mike M.00
22-Feb-13 12:05pm
View
Yes, white space is your friend - computers don't care, but brains see the structure better.
HINT to the unseasoned or occasional programmer: Pay close attention to at least the first error message generated by the compiler - make sure you know what it means as it will lead you in the direction of your solution. In this case "no matching function for call to 'pow(int)'" was trying to tell you the compiler could not find a function called 'pow' which took one integer parameter (see hemantrautela's Solution 1).
Another trick I like to use to debug complicated math expressions, is to define a series of temporaries and build up the final expression one step at a time. This allows me to see all the intermediary values and it ends up isolating any error messages to exactly and only the offending item, e.g.:
int t1 = maxSpeedRpm/minSpeedRpm; // Here you would see t1 is zero for some data like 5/7, so this needs to be float.
float t2 = pow ( t1, 0.2 ); // And actually pow() needs a double as first argument, but comilers convert it for you.
float t3 = sqrt ( t2 );
A debugger allows you to see each value and understand what's working, what's not.
Mike M.