nemesis wrote:
> really?!  What was it?  An settable option for the compiler?

So say you had a piece of code that would take input, do some calculations, 
then print the report.

"main" would be in the root, along with things like printf(), malloc(), etc. 
And anything else that was used in more than just input, calcs, or print.

Main would call your top input routine, which would cause that chunk of code 
to be read in and branched to. It would take the inputs it needs and save 
them out to a file (or memory or whatever).  Input routines would return 
with a flag that says "Yes, go run the calcs", so Main would invoke the calcs.

You'd overlay input on top of calcs, so while you're doing the math, your 
input validation routines and code to draw menus and widgets and such 
doesn't need to be around.

Your calcs would write out their results (say, in a CSV file) and return to 
main, which would invoke the print routines, including those that knew how 
to put in commas and dollar signs, paginate reports, print the appropriate 
footnotes on the proper pages, etc. All your printer drivers could be gone 
while you're doing input. All your input validation could be gone while 
you're doing printing.

-- 
Darren New, San Diego CA, USA (PST)
   Serving Suggestion:
     "Don't serve this any more. It's awful."

Post a reply to this message