RP> I'll write something resembling pseudocode with lines and arrows to
 RP> help indicate what's happening. That's the closest I get to flow
 RP> charts. Interestingly, just as I was wrapping up my teaching career,
 RP> the province's Ministry of Education also de-emphasized flow-charting
 RP> in the Computer Science curriculum. Too often, I saw flow-charting
 RP> used by the teacher as busy- work when there wasn't one computer for
 RP> every student, i.e. "You can't enter any program code into the
 RP> computer until I have seen and approved your flow-chart." Great way to
 RP> turn kids on to programming!
Howdy Rick,
That'll do the job.  It doesn't take diamonds and squares.  These days, I
sometimes start out in QuickBasic with a whole collection of REM's and labels 
and get all the tasks organized that way.  Then fill in the necessary chunks 
of source code.
I gather MicroSoft is hiring programmers that don't have the skills to 
organize their code these days.  So they end up with dozens of subroutines 
that perform the same kind of things, which if organized, one subroutine 
would handle.  The amount of compiled code sure indicates some sloppy design 
work.
If the kids are not comfortable working in a logical and structured fashion, 
it might be better they get turned off and find something more suitable.
Chris
--- FMail 0.96â
---------------