Is there a performance penalty if I do function prototyping for non-member functions?
Code:( code above, classes, etc ) // Some comments void Foo(int &v); // declare ( more code ) void Foo(int &v) { // define }I believe the first code is better organized, especially if you have a lot of functions.Code:( code above, classes, etc ) // comments void Foo(int &v) // declares and defines { // do something }
> Is there a performance penalty if I do function prototyping for non-member functions?
No.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
me, too.I believe the first code is better organized, especially if you have a lot of functions.
in most cases, you actually have to do the first: if they're all in one file, then ( more code ) is either main or else class definitions relying on knowledge of Foo.
but the file could also be just a list of functions relating to some issue, and Foo might be one that others don't depend on.
i still prefer version 1, though. it seems to me (i'm no expert, so i'm serious about the "seems" there) that version 2 is making an inline declaration. and i think that in turn means that the funcion is compiled separately for each call. so, if you call it more than once, version 2 would also on that view make your compiled code longer, although i think maybe also nanoseconds faster at runtime.
i'm not coming up with any circumstances where i like version 2 better, but that's not to say that they don't exist.
