Thread: Prototypes?

Outside of writing the prototypes for you, what would you like us to do?

Are you having trouble understanding what a function prototype is?

Writing prototypes is simple. Just select the first line of the function, copy it, paste it at the top and add a semicolon. Works in most cases.

Originally Posted by MuzicMedia

Yes i am. and could u finish the program so i can get a step by step basis of how to complete my programs.

That is your responsibility.
http://en.wikipedia.org/wiki/Function_prototype

The prototype should just be a replica of how your function definition looks like, but with a ; at the end, as have already been implied. It's not tougher than that.

Originally Posted by MuzicMedia

Yes i am. and could u finish the program so i can get a step by step basis of how to complete my programs. its a hybrid course so i have little help for the instructor. Thank you

Yes, I could do your homework for you, but that doesn't help you learn anything. There are examples of code all over the web, which you can learn from. Assignments are for you to actually gain practice from doing the work.

A function prototype is easy to understand if you know what a function is. Basically, a function prototype is used to tell the compiler that you have a function that you wrote. This lets the compiler store information on what types of variables it accepts and what type of variable it returns. When it comes across usage of your function and the definition of the function itself, it can verify that it matches the prototype. If it doesn't match, however, then the compiler can let you know something is wrong, and allow you the opportunity to go back and fix it.

Originally Posted by CornedBee

Writing prototypes is simple. Just select the first line of the function, copy it, paste it at the top and add a semicolon. Works in most cases.

And will work in your case.

a hint for you:

the following will work fine:

Code:

double calcint(double amount, double rate)
{
	return amount * rate * 1;
}

int main () {
	//...
	calcint (amount, rate);
	//...
	return 0;
}

the next code won't compile because the compiler doesn't know what calcint is:
its declaration appears after the program calls it in main.

Code:

int main () {
	//...
	calcint (amount, rate);
	//...
	return 0;
}

double calcint(double amount, double rate)
{
	return amount * rate * 1;
}

a function prototype tells the compiler that calcint exists: it lets you implement your calcint anywhere:
<solution removed>

not a good practice remove var names from function prototypes - makes code harder to read

When they are member functions, I tend to leave the names in. When they are not member functions (usually when I'm actually writing in C), I tend to leave the names out.

When they are not member functions (usually when I'm actually writing in C), I tend to leave the names out.

What's your rationale for this practice?

Originally Posted by laserlight

What's your rationale for this practice?

In all honesty, probably nothing worth copying. I just posted what I have done in the past, and I'm open to changing it. Usually, it was done without much conscious thought.

I try to write my classes inside headers, and I need to have an idea how all of my classes generally interact. I imagine I write the names out because of this, because it helps me figure out what the class is doing in each function when I'm writing the headers before I write any actual implementation code.

In terms of C, I guess it's because I generally know from the name of the function and the types they take what is going on. Member functions have the added context of a class that they operate within. Non-member functions do not have that context. They operate in terms of the program (or the collection of other functions you're grouping them with), and I think potentially (depending on how you write your code of course) easier to figure out what they do.

All in all, I've heard both ends.... it's good to leave the names in, and it's good to not leave the names in. In terms of people that need to study the headers or prototypes and want to learn how to use your code, it's probably best to leave the names in as hints as to how the function works.

Originally Posted by MacGyver

When they are member functions, I tend to leave the names in. When they are not member functions (usually when I'm actually writing in C), I tend to leave the names out.

And how do you know looking at
char *strstr(const char *, const char *);
Where should be put the full string and where the substring to be searched?