Yes, and it gives away a huge amount of information that you are merely giving away that they themselves should be able to do.
The best thing would be for the OP to do what code he/she can, consult the books and ask questions if there is something in there that he/she does not understand, which would be where we come in.
Is it indented? Yes.
Properly? No.
This is an example of how properly indented code should look like:
Code:
#include <@#>
void convertToCelsius(double);
void convertToFahren(double);
int getConvertChoice( int);
double getTemperature(int );
int main()
{
int x;
getConvertChoice(x);
getTemperature(x);
return 0;
}
double getTemperature(int choice)
{
if (choice ==1)
convertToFahren( );
else
convertToCelsius( );
}
int getConvertChoice(int x)
{
}
void convertToFahren(double z )
{
~
~
~
cout<<z<<endl;
}
convertToCelsius(w )
{
~
~
~
cout<<w<<endl;
}
And also a word of advice: do not strip the names of the parameters in the function prototypes. Just... do not.
And convertToCelcius also lacks return type and parameter type, so it is even more bad.