Home Page   We Generate Your Software.
Products Services Company Technology Demo Contact Site Map Search
The Somusar/SoProTech[tm] Booklet Series
Volume VII

"somusar/SoProMach: User's Guide"

Printer friendly


Contents
1. Introduction
2. Package Contents
3. Installing SoProMach
4. Verifying the Installation
5. Generating software with SoProMach
6. SoProMach Models
7. Sisendel Messages
8. Tefigel Messages
8.1 Tefigel Error Messages
8.2 Tefigel Warning Messages
8.2.1 Tefigel Warning Messages During Tag File Processing
9. Contacting Somusar
10. Further Reading

Chapter 8 - Tefigel Messages

The following list describes all fatal errors of the Tefigel processor, that is, all error conditions that cause Tefigel to stop processing input commands and text, and terminate with an error condition. The official definition of the syntax and semantics of Tefigel is documented in "Somusar/Tefigel[tm]: Reference Guide ".

8.1 - Tefigel Error Messages        top

- Badly formed ...

The specified instruction contains one or more syntax errors, with respect to the syntax rules specified by document "Somusar/Tefigel[tm]: Reference Guide ": possible errors may be missing parentheses, missing terms, unexpected characters, unexpected terms, and similar errors.

- Badly formed embedded call "......"

The specified function call after the current callkey is syntactically incorrect.

- Could not jump to "...": label not found

The specified label could not be found in the specified file, thus the jump instruction could not be performed as requested.

- Could not ... to "...": seek error

The specified jump instruction to the specified label could not be performed due to a seek error. A possible reason for this error could be a change in the contents of, or in the access permissions to, the specified file.

- Divide by zero

The divisor of the DIV instruction at the specified line evaluated to zero, thus the result of the division would be undefined.

- Empty string for system command

The evaluation of the command line string for the system instruction yielded an empty string.

- "fseek" on "..." failed

An attempt to perform a file seek operation on the specified file failed. A possible reason for this error could be a change in the contents of, or in the access permissions to, the specified file.

- "ftell" on "..." failed

An attempt to perform a "file tell" operation on the specified file failed. A possible reason for this error could be a change in the contents of, or in the access permissions to, the specified file.

- Illegal first character for ... variable

The identifier of the specified variable in the specified command does not start with a letter or an underscore _ and is therefore illegal.

- Instruction ... is missing corresponding ...

The specified instruction can only be used in conjunction with the specified corresponding instruction.

- [internal] filters "..." and "..." have the same priority

Internal error. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation". Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- [internal] excess slots in table "shortcut"

Internal error. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation". Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- [internal] insufficient slots in table "shortcut"

Internal error. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation". Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- [internal] need upper case code for macro "..."

Internal error. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation". Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- [internal] undefined opcode for ...

Internal error. It is highly recommended to verify the SoProMach installation as specified in "Verifying the Installation". Should this error condition appear again, please notify the Somusar support team as specified in http://www.somusar.com/services/support.

- jumpconds on <stdin> are not allowed

The specified instruction cannot be performed when the Tefigel processor reads text and commands from the standard input.

- jumps on <stdin> are not allowed

The specified instruction cannot be performed when the Tefigel processor reads text and commands from the standard input.

- label "..." already used on line ...

The specified label is used more than once in the specified file, thus the JUMP destination is ambiguous.

- labels on <stdin> are not allowed

The specified instruction cannot be performed when the Tefigel processor reads text and commands from the standard input.

- Line too long (...+ bytes)

The specified logical input line - possibly a concatenation of two or more physical input lines - exceeds the specified internal maximum input buffer size (currently 16 KB).

- Missing assignment '=' on ... of "..."

The specified instruction does not contain the assignment operator =.

- Missing condition for jumpcond

The specified instruction contains no logical condition (i.e., no boolean comparison).

- Missing delimiter '=' for retvalue

The specified instruction does not contain the assignment operator =.

- Missing ... at end of file processing

The specified expected end clause instruction could not be found after all input lines of the specified file have been processed.

- Missing ')' on call

The parameter list to the specified call instruction is not properly terminated.

- Missing test operator (one of =#~><}{) in ... ...

The logical condition (that is, boolean comparison) does not contain any comparison operator.

- Non-logical destination "..." (=...) for ...

The target (or destination) variable of the specified boolean operation has been previously set to a value which is neither 0 nor 1, and thus not suitable for boolean computation.

- Non-numeric destination "..." (=...) for ...

The target (or destination) variable of the specified arithmetic operation has been previously set to a non-numeric value, and is thus not suitable for arithmetic computation.

- Non-numeric value (...) for ...

In the case of arithmetic operations, this message notifies that the second operand of the specified arithmetic operation has been previously set to a non-numeric value, and is thus not suitable for arithmetic computation.

In the case of exit instruction, this message notifies that a non-numeric value has been incorrectly provided as an exit value to be returned to the originating operating system process.

In the case of switch instruction, this message notifies that a non-numeric value has been incorrectly provided for the specified switch control variable.

- Opening file "..."

The specified file could not be opened due to the specified reason. This message can appear as either a warning or an error message, depending on the setting of the ON_MISSING_FILE switch control.

- Out of range value (...) for ... [...]

The new value supplied for the specified switch control variable falls outside the valid range for that variable.

- Ran out of memory

An attempt of the Tefigel processor to allocate memory has failed probably due to a system overload. A check of the system status is highly recommended.

- Substitution loop on "..."

An attempt to expand the contents of the specified variable resulted in a substitution loop, that is, the current value of the specified variable contains direct or indirect references to the very same variable.

- Too many filters

The specified maximum number (currently 16) of concurrently active filters has been exceeded.

- Too many arguments (more than ...) to call

The specified maximum number (currently 32) of parameters to a function call has been exceeded.

- Too many nested files

The specified maximum level of file nesting via process or call instructions has been exceeded. An upgrade to a higher edition of SoProMach is recommended.

- Too many nested ...s

The specified maximum level of nesting with respect to the specified instruction has been exceeded. An upgrade to a higher edition of SoProMach is recommended.

- Unbalanced ...

The specified instruction attempts to restore a previously saved value of the associated special character, but no more saved values are available for that special character.

- Undefined destination "..." for ...

The specified target (or destination) variable of the specified boolean or arithmetic operation is not set to a valid value for the specified operation.

- Unknown ... identifier "..."

The specified identifier is not valid in the context of the specified instruction as defined by document "Somusar/Tefigel[tm]: Reference Guide ".

8.2 - Tefigel Warning Messages        top

The following lists describe all warning messages issued by the Tefigel translator, that is, all error conditions that do not cause Tefigel to stop processing input commands and text.

- Already in comment section

A comment section opening delimiter was encountered while already in a comment section.

- Already in tefigel section

A tefigel section opening delimiter (tefigel) was encountered while already in a tefigel section.

- codefile is obsolete, use tefigel instead

Instruction codefile has been superseded by instruction tefigel.

- Compiling reg. exp. of test "...": ...

The internal compilation of the specified regular expression failed due to the specified error, thus the boolean comparison could not be performed.

- filter "..." is not associated with any reg. exp.

The request to deactivate the specified filter could not be fulfilled as the specified file is not an active filter.

- filter "...", reg. exp. "...": ...

The internal compilation of the specified regular expression failed due to the specified error, thus the requested filter activation could not be performed.

- filter "...", reg. exp. "...": save failed

The internal saving of the specified regular expression failed, thus the requested filter activation could not be performed.

- FMT_FLOAT requires two arguments

Wrong number of arguments provided to function fmt_float.

- FMT_INT requires two arguments

Wrong number of arguments provided to function fmt_int.

- FMT_STR requires two arguments

Wrong number of arguments provided to function fmt_str.

- globset of previously set variable "..."

An attempt to define the specified variable in the global name space has failed because the same variable identifier has already been used in one or more non-global name spaces. The specified instruction is performed as if it were a plain set instruction, thus the variable is set to the new value specified by the instruction.

- Ignoring extra arguments (more than 3) to REPLACE

Too many arguments provided to function replace.

- Illegal id. format "..."

The identifier of the specified variable either contains characters other than lower case letters, decimal digits, or underscores "_", or it does not start with a letter and is therefore illegal.

- "library ..." would override "...", ignoring it

An attempt has been made to specify a library path when another path is already active, but only one library path at a time can be active, to ensure that called or processed files can be uniquely identified.

- mark '...' for <instruction-1> already in use as mark for <instruction-2>

The new marker specified for <instruction-1> was already in use for <instruction-2>; depending on the type of <instruction-1> and <instruction-2>, subsequent input command lines starting with the new marker might be interpreted by the Tefigel processor as either <instruction-1> or <instruction-2> command lines.

- Missing identifier to create new list

No list identifier has been provided to function new_list.

- No argdelim set, can't perform shift

A shift instruction was attempted, but no argdelim is set, so it is not possible to shift the argument variables.

- Not in comment section

A comment section closing delimiter was encountered while not in a comment section.

- Not in tefigel section

A tefigel section closing delimiter (endtefigel) was encountered while not in a tefigel section.

- Opening file "..."

The specified file could not be opened due to the specified reason. This message can appear as either a warning or an error message, depending on the setting of the ON_MISSING_FILE switch control.

- Restoring reg. exp. "...": ...

An attempt to restore the specified regular expression failed, so that the associated filter - although correctly active - cannot be applied to the current output line.

- Truncating very long internal exec "..."

The specified internal exec is too long and will be truncated.

- Unknown output line count, returning 0

The Tefigel processor cannot compute the current output line number after a system instruction has been run while the output file was still the standard output.

- Unrecognized id. pattern "..."

The specified identifier pattern string is not included in the list provided in "Somusar/Tefigel[tm]: Reference Guide " and is therefore illegal.

8.2.1 - Tefigel Warning Messages During Tag File Processing        top

The following list describes all warning messages issued by the Tefigel translator when processing a tag file.

- Closing unbalanced tag end "..."

The specified tag node has not been closed before the end of the tag node that includes it as a subnode.

- Control character 0x... converted to blank

The specified non-textual character has been automatically converted to blank by Tefigel.

- Empty tag "..."

The specified tag is empty.

- Exceeded tag stack capacity

The maximum level of tag nesting has been exceeded. An upgrade to a higher edition of SoProMach is recommended.

- Expected TAG_START '<', found '...'

The specified unexpected character has been found where a "<" was expected.

- Missing TAG_END > at end of file

A tag appears to have not been properly closed before the end of file.

- Missing terminating ... quote sign at end of file

A string of text in quotes appears to have not been properly closed before the end of file.

- No open tags, unbalanced tag end "..."

The specified tag node has been closed, but there were no open tags at that stage.

- Tag file processing failed. Reason: ...

Tag file processing was not possible for the specified reason.

- Tag key/value pair too long, skipping it

A tag attribute/value pair string is too long, and will be ignored.

- Tag text too long (... characters), truncating it

The specified tag text is too long and will be truncated.

- Truncating very long tag id "..."

The specified tag id is too long and will be truncated.

- Truncating very long tag path

The current tag nesting path is too long and its conversion to a string will be truncated.

- Unbalanced tag end "..."

The specified tag node has been closed, but it had not been opened previously.

- Unbalanced TAG_END > ignored

A ">" tag end encountered outside a tag node will be ignored.

- Unbalanced TAG_START < ignored

A "<" tag start encountered inside a tag node will be ignored.

[Previous chapter]    [Next chapter]    [Back to top]

http:// www.somusar.com  / doc  / booklets  / usr_guide  - Powered by SoProMach
Copyright © 2003-2012 Somusar - Trademarks - Legal - Privacy - Webmaster