🚀 go-pugleaf

You are mostly correct but there is one notable mistake with your
response.  'void' functions can have an empty return statement in them
and will NOT produce a syntax error.  This is so that the control flow
of a function can be governed.   Consider, for example, a function that
swaps the values of two pointers (not unlike what SelSort does for the
current assignment):

void swap( Node* src1, Node* src2 )
{
	if( src1 == src2 )
		return;  //  <-- if the nodes are the same, I don't want
			 //       to do anything, and just return.

	etc....
}

As for placing prototypes in functions, that too is just fine and is in
fact preferable to placing prototypes in global space whenever
possible.  I didn't mention that because in truth, we'll be using c++
classes for later assignments, at which time the notion of a free
function (one outside of a class) becomes largely unused.


michael maitan wrote:
> 
>   I wanted to point out that function prototypes can be placed in functions
> as well.  This is useful if you do not want them to be global. In some of the
> programs in CS151 we were actually required to place the prototypes in
> the main() function.  I also noticed there were ruturn statements in the
> functions used. Since the functions were defined with void before the
> function name, the function is not expected to return anything through its
> name.  This will cause a syntax error when compiled. (Ex. void function()
> returns nothing through its name...  int function2() returns an int through
> its name)  I hope this is of help to any who read this. : )
> 
> -Mike
> (http://holly.colostate.edu/~brnruber)


cheers
--
Corby S. Hudnall
http://www.cs.colostate.edu/~hudnall/cs200