In C, Do I really have to have a function prototype?? If I do have one, why do I define my function after main

Question

If I do have a prototype, Do I have to define my function after main?? What if I do not??

I am really annoyed by these retarded prototypes! What happenes if I do not put them, then How do I define function and when??

And Finally, why is this an error

#include

int mult (int x, int y);

int main()
{
printf("Hello\n");
mult();

int mult (int x, int y)
{
scanf("%d", &x);
scanf("%d", &y);
printf("The result is %d", x * y);
}
It gives me too few arguments for mult!

Pls help me! I am annoyed to maximum by these functions!

Answer 1

To use the function "mult" in main, you either have to have a prototype before main or the entire function definition before main. Otherwise, when the compiler gets to the point in main where you call your function (mult) it will complain that it's never heard of anything called "mult" before.



So, you can just put the whole function definition before main, or you can use a prototype, which tells the compiler that a function called "mult" exists, and will be defined later.



As for the compiler error, you declare mult to take two integers, but when you call it you provide none. You're also not returning anything from mult when, as it's defined, it should return an integer. Try changing mult to look like this:



void mult()

{

int x, y;

scanf("%d", &x);

scanf("%d", &y);

printf("The result is %d", x * y);

}



This declares the variables x and y inside of mult, rather than specifying them as values that have to be supplied when the function is called. Or you could do this:



#include



int mult (int x, int y);



int main()

{

printf("Hello\n");

int firstNumber, secondNumber, result;

scanf("%d", &firstNumber);

scanf("%d", &secondNumber);

resutl = mult(firstNumber, secondNumber);

printf("The result is %d", x * y);

}



int mult (int x, int y)

{

return x * y;

}

Answer 2

1. Prototyping in most C compilers is not required. It DOES help you avoid syntax errors, as the compiler 'checks' all instances of the function for correct values.



2. A couple of problems with your code. You need a closing brace for the Main function. Assuming that's a typo, the next problem is in your definition, both prototype and actual, you're indicating that the mult function will be passed two integers, and you're never passing them. Change the definition to read int mult() in both instances. Then in the mult function, add a line after the first brace "int x,y" to define the integers as a local variable. Alternative solution: define mult as "int mult()" and declare int x,y as a global variable. 2nd alternative: declare x and y in the main function, perform the scanf functions in Main, then pass the values to mult

Answer 3

If you define your function before main, then you don't need a prototype. If you design it after main, then you need the prototype to let whatever is in main know that these functions exist.



You called the function mult() with no arguments. You defined the function with the requirement that two integers must be passed as arguments.



Don't get frustrated. Once you get the gist of it things, functions will be in your veins.



main is... well... the main part of your program. Its the first thing that's executed when you run a program. Functions provide a way to do things without knowing how its done. For example if you have an "add" function that takes two integers then return their sum, all you want to know is that it does what it does. How it does it is of no concern... unless you have to write the code for it... or care about performance. That's the black box approach.



The good thing is that functions/methods are basically the same across all languages that you'll most likely use. Understand the concept for one and you'll understand it for all.



Check out this C++ tutorial on functions. The same applies to C.



http://www.cplusplus.com/doc/tutorial/functions.html

Answer 4

2 Errors with your code, one was already mentioned, the other is below:



#include



int mult (int x, int y);



int main()

{

printf("Hello\n");

mult();



int mult (int x, int y)

{

scanf("%d", &x);

scanf("%d", &y);

printf("The result is %d", x * y);

}



is missing a "}" before int mult(int x, int y)



You never got out of your main program, and you want to do your scanfs in main

int x,y;

scanf("%d", &x);

scanf("%d",&y);

mult(x,y);



Further, your function is set to return a value of int type, but you're not returning anything.



so you could in your mult function you could do:

return x*y;

and do the print in main. Or set the return type to void on your mult function

Answer 5

The C++ function Prototypes are there to make the compiler happy . How's that? initially the compiler desires in easy terms the prototype of the function :its call, parameters, and return style . The compiler reads the source code from good to down ; now assume u have this code . here, we supply the Prototypes to function foo() , call it in substantial() THEN after substantial() we define the entire physique for foo () void foo( int x ) ; //prototype void substantial() { //Code //................. //call foo( ) foo() ; //Code //.............. }//end substantial() //Now define: the foo() function void foo ( int x ) { cout<< x ; } What the compiler does is: 1It sees the prototype for foo()It 'knows' it is going to bump into function called foo() that takes an int as a parameter and returns void 2.It is going all the way down to substantial() and encounters a function called foo() , yet he would not ***** as he knows its signature 3.After substantial() is done, the compiler famous the full code for foo () in an attempt to sum up, the compiler desires a minimum of the prototype till now a function could nicely be called ; latter on u can define the full code fro the function Tip : merely style the entire function till now calling it from yet another .