That''s an odd question... I don''t think that you need a book. Just know the characteristics of the various loops, and practice! Eventually, you will know what should be used "instinctively".

For more advanced (actually, much more advanced, compared to for/while) constructs, check out the Design Pattern book by Gamma et al. (IIRC). But be aware that if you don''t know when to use a for and when to use a while, you shouldn''t start reading this book now.

Good luck,

Cédric

quote:Original post by Alpha_ProgDes
I wanted to know if there is a book or site that shows you when to use a while loop, do while loop, or for loop; when to use a class or struct; or just when to use which coding techniques or structure AND how to set it up CORRECTLY.

I think the reason you''re having problems is that this is more of a style issue than a correctness issue.

In general:

- A while loop checks the condition at the start of each iteration.

- A do while loop checks the condition at the end of every iteration.

- A for loop performs instructions a set number of times.

However, none of these are hard and fast rules. I can make a for loop into a while loop:

bool bCondition = true;for ( ; bCondition ; ){...} 

The only reason I can think of to not do this is simply that it''s not very standard, and might confuse other people who look at the code. On a solo project, that''s not usually a big concern.

On classes versus structs, I generally use classes for data structures that include functions, and structs for data structures that do not. There is no rule here either. There is exactly one difference between a struct and a class (bonus points for anyone who can name it!). However, again, it''s more standard to use classes for OO.

Pretty much any type of loop can be used for any other type. The main difference, really, is CONCEPTUAL. Use the right type of loop for the right purpose.

For loop: implies a set number of iterations that is known before the loop is entered. Also used to iterate over an entire data structure (i.e., a linked list). Basically, a finite series.

While loop: the most general. Implies doing something "as many times as it''s needed", which may be zero times. Implies that checking whether something still needs to be done is a simple process (i.e. a condition will suffice, with no extra need for algorithm stuff).

Do loop: probably the least used. Use of this loop implies you don''t know whether to stop until AFTER you''ve done stuff; that is, the act of executing the body of the loop produces a decision on whether to execute it again, or finish. An example is getting input from the user and seeing if it''s valid; you don''t know whether the input is good until after the user has entered it.

Goto loop: Get thee behind me, foul programming demon!

Don''t listen to me. I''ve had too much coffee.