The book I'm currently going through is Sams Teach Yourself C++ in 21 Days. I also have C++ Primer Plus. I am reading these two books to really drill the fundamentals of C++ programming into my head.
Thanks to everyone for their answers to my questions. Much appreciated. Julie --- In c-prog@yahoogroups.com, "Paul Herring" <[EMAIL PROTECTED]> wrote: > > On Thu, Apr 3, 2008 at 5:20 AM, fireplace_tea <[EMAIL PROTECTED]> wrote: > > Hello Everyone, > > > > I am learning about functions and the book I am reading says that it > > is good practice to create function prototypes. My questions are: > > Which book? > > > Do you really need to create function prototypes? If so, why? > > If you write your source code such that you define the functions > before they're used (resulting in main() being at the end of the > source file) then, no, you don't need to create prototypes. > > There are occasions where this breaks down where you have two objects > that refer to each other (e.g. foo() may call bar(), and bar() may > call foo(),) in which case you prototype one before defining both (in > this example prototype foo(), define bar() then define foo(),) but > they're the exception rather than the rule. > > -- > PJH > > A man in a shellsuit goes into a posh furriers. He says to the shop > assistant "I want a coat". > The shop assistant, barely concealing her disdain, asks "What fur?" > The man replies "Fur ma girlfriend". >
