RP> The sheer size of such a flow chart would minimize its usefulness
RP> as a simplified overview. And how do you represent event-driven
Windows
RP> apps with flow charts? But whatever works for the individual,
there's
RP> no hard and fast rule. Several studies have been done however, that
showed
RP> flow charting made little or no difference in the quality of
programs
RP> written by high school and college students. I can't quote you any
RP> sources unfortunately, it's been ten years or more since I left
teaching.
     IF one were into flowcharts, they could be done on
a broad scale, rather than every single branch.
Somewhat like  documenting.  I will sometimes
head large sections with a REMark, but I have seen
programs (way back) that would have:
 REM print the value of A, stay on line
 PRINT A;
 REM print the value of A$
 PRINT A$
     No, I mean it: I have actually seen things that
stupid.  I see nothing wrong with "self-documenting"
code, using variable names that have a human meaning -
I remember when a BASIC I was using allowed only
2-letter variables.  Now I'm allowed to use:
 DayOfWeek$ = "Tuesday"
and that has meaning. DA$ did not!
     I may, if I'm going to write an involved program,
sketch out a chart or list.  It won't have the squares
and diamonds, but will be a broad outline.
     Of course, if I must tell the truth, I usually
just sit down and start typing and see what happens!
  FIDO: Bill White @ 1:135/110 (Miami)
 InterNet: bill.white@110.sunshine.com
 * SLMR 2.1a * Put love notes in your child's lunch box!
--- Maximus 2.01wb
---------------