/
gmplAuthorStatement
gmplAuthorStatement
Mark Juras
Owned by Mark Juras
Author Statement Summary
Author is a nonterminal, command statement that occurs only in command scripts. It takes as input the intermediate code produced by the analysis phase of the translation process. Using that code and the information contained in the symbol table it produces a fully functional code in the target language. The attributes of the Author statement are as follows:| Attribute | Description |
| Name | This attribute specifies the overall name to be used as the web project name for an ASP site translation. If omitted, the name WebProject is used. This attribute is ignored in VB6 translations. |
| Project | This attribute specifies the name of a previously compiled and analysed VBP project or ASP page. It restricts the author to that component only. If omitted, all active components are authored. |
The substatements of the Author statement are as follows:
| Substatement | Description |
| Fix | Adding a Fix command to the Author statement makes it possible to apply search and replace type edits to the translated source code before it is written. This facility has several benefits: first a quick, inexpensive way to solve one-off problems; and second, a temporary workaround to document and handle issues until a permanent solution can be incorporated into the standard tool configuration or the core translation engine. |
The script errors associated with the Author statement are as follows:
| Error | Description |
| 1007 | Encountered illegal AUTHOR directive %1d |
| 1008 | The Project [%1d] does not exist in the storage area. |
| 1009 | The Component [%1d] is not a project. |
| 1010 | The Storage area does not contain any projects. |
The actual records written by the author are stored in the virtual binary information file in editable text buffers. These buffers can then be modified via Fix substatements. It is the final records in these buffers that are actually written. In addition to the target code the author also produces the project files needed to create .NET assemblies, resource files containing control property values, stubs for any external components referenced, and a reference file describing the public symbols exposed by the code. When-ever possible the code produced by the author can be deployed to its deployment location and directly built using the .NET compilers.
Table of Contents