
Lesson #18 - Pseudocoding the Core Routine
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Once you have completed your generic session outline (or session
flowchart), it's time to start sketching out the macro.  Here are the
conventions I'm going to use in my example:

        - anything on the outline which is listed as "sometimes",
          "depending", or "maybe" will be treated with a conditional
          macro command, e.g., "SSLO", "GOLO", or "CALO"

        - I will be using variables for all "LOOK"ed for info.
          Variable name will be a short, easily recognized prefix
          (something related to the prompt, e.g., "main" for main
          menu prompt) followed by a "_p" for "prompt", e.g.,
          "main_p" for the "Main Menu Prompt".

        - I will be using variables for most "SEND" data.  Variable
          name will be the same short prefix that matches the prompt
          it's designed to reply to, followed by a "_r" for
          "response", e.g., "main_r" for the response to Main Menu
          Prompt.

        - I will use "========" as visual divider between major
          subelements of the script, I will use "------" as logical
          dividers between major processes within sub-elements.

The example which follows is a "first cut" at translating our outline
to {COMMO} macro language.  Feel free to use whatever conventions you
think best for variable names, etc., when coding your own outline.

Jim
