Fix Statement Summary

Fix is a nonterminal, command statement that occurs in command scripts and can also occur within Compile or Author statements. It is used as well with EditFile commands in GlobalSettings files. This statement supports making changes to the source code before it is compiled or target code before it is written. A source code fix does not change the original VB6 or ASP files; rather it changes the code in memory after it is read.

The attributes of the Fix statement are as follows:

The substatements of the Fix statement are as follows:

The script errors associated with the Fix statement are as follows:

ReplaceFile Fix Substatement Summary

ReplaceFile is a terminal substatement of the Fix statement. It replaces the content of files within the active text buffers with the content of a specified text file.

The attributes of the ReplaceFile substatement are as follows:

Text buffers contain multiple files each of which is started with a cat filename statement and ended with a terminal marker !)(!. The ReplaceFile substatement searches the active text buffers for cat statements whose filename matches the source attribute. For each one found, all records below the cat and above the !)(! are deleted. Then the records from the target file are inserted.

Replace Fix Substatement Summary

Replace is a nonterminal substatement of the Fix statement. It replaces or deletes either string fragments within text records or blocks of one or more records. When the fix type is ReplaceGlobal, then all matches in all active text buffers are processed. When the fix type is ReplaceSingle, once a match is found the process stops.

The attributes of the Replace substatement are as follows:

The substatements of the Replace substatement are as follows:

The script errors associated with the Replace substatement are as follows:

There are two forms that can be used for specifying the text blocks. The single line form is

    <OldBlock><![CDATA[...oldtext...

The multi line form is

    <OldBlock><![CDATA[
    ...oldline 1...
        ...
     ...oldline n...

    

There is no requirement that the two forms match in a given replace. In all cases leading and trailing whitespace is ignored and the comparisons are not case-sensitive. Single line matchs replace or delete substrings within lines and may work on multiple matching substrings on the same line. Multiple line matchs work on entire lines.

There is a special wildcard notation "..." available for use in the multi line form of the OldBlock specification that means "skip records until match is found". For example the following specification

<Fix>
   <Type>ReplaceSingle</Type>
   <Replace name="Remove duplicate function">
   <OldBlock><![CDATA[
   Private Function ComputeSomeThing
     ...
   End Function
   

will remove the first occurrence of the function "ComputeSomeThing". The ... must be the only entry on the line and it may be neither the first nor the last line of the specification. Once the starting lines are matched, records are skipped until a record matching the following line is found.

"Top-Level" Fix

Fix statements typically occur in as a child-element in a Compile, Author, or EditFile blocks.  However, they may also occur as a top-level script command.  In this context, the Fix must also have a FileFilter attribute.  And, unlike the child-elements that work on a copy of the file in stored in system model in memory, top-level fixes modify the specified file directly.