home *** CD-ROM | disk | FTP | other *** search
-
- Explanation of Error Messages generated by TPTC
- ===============================================
-
- Fatal: Aborted by <escape> key
- This message indicates that the user pressed the ESCAPE key to abort
- the translation in progress.
-
- Fatal: Can't create tempfile: <NAME>
- The translator wanted to create a temporary file but could not.
- This is usually caused by an invalid drive or directory specified
- with the '-w' command line option. It could also be caused by
- insufficient disk space, not enough file handles available, or
- excessive procedure block nesting.
-
- Fatal: Can't open unit symbol file: <NAME>
- The translator needed to load a unit symbol file (a .UNS file), but
- could not locate the file. Tptc needs to load TPTCSYS.UNS for each
- translation (this file defines the default environment and
- predefined functions). This could also be caused by a missing or
- incorrect directory specification in the '-s' command line option.
-
- Fatal: Functions nested too deeply
- Procedure or function units were nested more than 10 levels deeply.
- This might also be caused by a missing "interface" keyword (which
- would cause the procedure specifications to look like nested
- procedure implementations).
-
- Fatal: Includes nested too deeply
- Include files may be nested up to two levels.
-
- Fatal: Out of memory
- There was not enough memory to make another symbol table entry, or
- to allocate the buffer for a new file. Increase memory, divide your
- program into smaller parts, or include fewer units in your "uses"
- statement.
-
- Fatal: Out of stack space
- This error indicates that all available stack was exhausted while
- parsing your source file. It can be caused by highly complex
- expressions in conjunction with high levels of procedure unit
- nesting.
-
- Fatal: Too many identifiers
- You listed too many identifiers in a declaration before the data
- type specification. These identifiers are limited because they must
- be held until the ': type' clause is reached. Break up the
- declaration into two or more parts.
-
- Fatal: Too many params
- There were too many parameters in the current procedure declaration
- or call. This is currently limited to 16.
-
- Error: Identifier expected
- In an expression, a symbol or keyboard was found where an identifier
- (variable name) was required.
-
- Error: Section header expected
- The translator was expecting VAR, CONST, TYPE, PROCEDURE, FUNCTION,
- or some other main section header. Instead, it found an identifier
- or special character. Often caused by faulty recovery from a
- previous error.
-
- Warning: Dynamic length reference
- A reference to the zero-th byte in a string was detected. Since
- translated code uses the C convention for strings, this code
- requires a conversion to C string conventions.
-
- Warning: Gigantic case range
- A numeric range in a case selector covers too great a range. Since
- the translator must benerate a line of code for each value within
- the range, it is advised that the statement be recoded using an if
- statement.
-
- Warning: Inline procedure
- An inline procedure was detected within an interface section.
- Interface sections must not contain executable code in the C
- language target files. Convert this to a normal procedure
- containing an inline statement.
-
- Warning: Interrupt handler
- An 'interrupt' procedure was detected. These procedures require
- special attention, since the C conventions for interrupt handlers
- differ from those of turbo pascal.
-
- Warning: Nested function
- This warning is generated when a nested procedure/function block is
- found. The translator does not yet translate shared variables or
- formal parameters among nested functions.
-
- Warning: Redeclaration not identical
- A global procedure, function or variable declaration is incompatible
- with a previous declaration of the same name. This sometimes
- results from nested procedures or local constants.
-
-
-