You could try just reading your error messages carefully and figuring out what they mean.
For example. warning C4183: 'Credit': missing return type; assumed to be a member function returning 'int'
[B]/*What goes here?*/[/B] Credit(double n)
{
cout << "How much money would you like to add?" << endl;
cin >> n;
if (n>0.00)
{
balance = n + balance;
}
else
{
cout << "That is not a correct amount to add" << endl;
}
}
Is it really so hard to figure out what you should make the function return?
Work through the messages one at a time, and see what you can come up with.
In future, press "compile" every time you add an empty class, and every time you add a new function to the class (or file). Then you won't be swamped with errors caused by many hours of sloppy coding, and you can nip any "copy/paste" errors before they have a chance to replicate.
Historically, - C++ was derived from C. - In C, everything was an int unless specified otherwise (there was no void), so it was natural for main to return int. - C programs were originally developed for command line use, and using a command line interpreter which was far more capable 30 years ago than M$ cmd.exe is even today. That command interpreter could easily determine whether the program just ran was a success (or not) from the value returned by main.
> Ok , ok so I failed to look at the datestamp of egemen's post -- three months old Yeah, a 3 month bump, which in itself began as a bump of a 3 YEAR old thread.
I bet Jack knows how to spell his own name, regardless.
#include <topic.h> Error - topic not found - entering thread wibble mode.
