Known anomalies

 1) MAIN is sometimes not the first procedure in the .LNK file

    Rescue5 sometimes fails to place MAIN first in the list of
    procedures in the .LNK file, resulting in an EXE file that does
    not run.

    The workaround is to edit the .LNK file to make MAIN the first
    procedure.

    This does not apply to systems in which all the code was
    compiled with the /b switch, which do not have a MAIN.UDF.

 2) CA-Clipper reports 'string space exhausted error'

    This can occur when compiling source files that contain a very
    large number of string operations.  The CA-Clipper parser
    simply runs out of the memory it reserves for string
    processing.

    In every case identified to date, the original source code had
    embedded quotes in strings, which Rescue5 recovers as chr(34)
    string concatenations:


      Original:

         '"This is a fine example", she said'


      Recovered:

         chr(34) + "This is a fine example" + chr(34) + ", she said"

    Workarounds include reducing the number of string operations by
    editing the strings, moving some of the strings into another
    source file by splitting the procedures(s) concerend, or trying
    a different memory configuration and/or different version of
    CA-Clipper 5.x.

 3) CA-Clipper reports 'too many segments' error

    A recovered source file is too large for CA-Clipper to compile.

    Although Rescue5 splits files that are becoming too large, it is
    difficult to predict the point beyond which this error will
    occur (it is only indirectly related to the number of lines of
    code and file size).

    Workarounds include changing the grouping file to move code
    into another file, using a different /s switch setting or
    manually splitting the file.

 4) CA-Clipper reports 'phase error'

    Phase errors are caused by some combination of STATIC
    declarations (both variable and procedure).  The precise
    combination varies from version to version, and a source file
    that CA-Clipper 5.01 compiles without a problem may cause
    CA-Clipper 5.2 to choke, or vice-versa.

    If a version of CA-Clipper reports a phase error in Rescue5
    recovered code, then that error would also have been reported
    in the original code.

    The workarounds are not very precise - change the order of
    STATIC's or assign them at a different point in the program, or
    try a different version of CA-Clipper.

 5) CA-Clipper reports 'duplicate procedure name' in ORPHAN.UDF

    ORPHAN.UDF is now included in the .RMK and .LNK files (contrary
    to the printed documentation), and it can contain duplicate
    procedure names.

    Workarounds include removing ORPHAN.UDF from the .RMK and .LNK
    files, renaming the procedures concerned or distributing the
    duplicate procedures in different source files by editing the
    grouping file.

 6) RDD request statements

    The REQUEST <rdd> statement is a directive to the linker, not a
    CA-Clipper command.  If your system uses RDD's other than
    DBFNTX you will need to insert the appropriate REQUEST
    statements in the source code in addition to adding the
    appropriate libraries to the .LNK file.