The decompilation screen


 The decompilation screen is divided into five regions:

 1) The Configuration region displays the current Rescue5
    settings.

            EXE file:  Name of the .EXE file being decompiled
         Indent mode:  /tt or /ts setting
        Right margin:  /r setting
       LIB threshold:  /s setting
       Graphic chars:  /g setting
           Key words:  /k setting
             Memvars:  /m setting
          Procedures:  /p setting

 2) The Procedures region displays information about the
    procedures in the .EXE file.  The first column of figures
    contains the symbol number, the second the percentage
    processed so far.

    The type of the procedure currently being processed is
    ticked.

    The "protected" figures will always be zero.  This slot is
    reserved for procedures that have been individually
    protected by APTware's protection utility.

           Name: Procedure being processed
         Normal: Total and % of non static, init or exit procedures
         Static: Total and % of static procedures
           Init: Total and % of init procedures
           Exit: Total and % of exit procedures
          C/ASM: Total and % of non CA-Clipper procedures
      Protected: Total and % of protected procedures


 3) In the centre of the screen is a progress bar
    that indicates the status of the current operation.

 4) The Decompilation region displays information about the
    decompilation of the current procedure.

            Name:  Name of the procedure being decompiled
      Parameters:  Number of local parameters
          Locals:  Number of local variables
         Memvars:  Number of publics, privates and autos
     Code blocks:  Number of code blocks
   Sticky blocks:  Code blocks with detached activation stacks*
    Flow nesting:  Deepest flow control nesting level
   Block nesting:  Deepest level of code block nesting

  *A "sticky block" is a code block that refers to a local or
   static variable declared outside itself.  When this happens,
   CA-Clipper links the code block to the activation stack of
   the procedure in which it was created, ensuring that the
   correct locals and statics are in scope wherever the code
   block is evaluated. The procedure's activation stack in
   effect "sticks" to the block.

 5) The Output region shows information about the files the
    decompiled code is written into.

        Module:  Module name and number of lines of code.
          Name:  Procedure name and number of lines of code.

         Total modules:  Number of modules written
      Total procedures:  Number of procedures written
           Total lines:  Number of lines of code written
           Total bytes:  Number of bytes written