gslint error messages

An internal error occurred at 'value A':value B'

This error is internal, and does not normally occur. Contact your local support center.

'value A'Path does not exist: 'value B'

Check the GSLINTRULES environment variable. For further information, see Code Quality.

'value A'Path is not a file: 'value B'

Check the GSLINTRULES environment variable. For further information, see Code Quality.

Cannot read file of rules 'value'

For further information, see The lint rules file.

Invalid rule. 'value' is not a valid rule key

For further information, see The format of rules in the lint rules file.

Invalid rule property. The 'value' rule property is unknown

For further information, see Identifier naming convention rules.

Invalid rule property value. 'value' is not a valid value for the 'rule' rule property

For further information, see Identifier naming convention rules.

Can be one of the following messages according to the option(functions|comWebServiceEngineOptions|FGLImports|frontCalls) defined for a ruleid (deprecated|backwardCompatibility) in the gslint rules file:

The function 'function()' cannot appear twice, once in the 'value A'.'value C' list and one in the 'value B'.'value C' list

The WebServiceEngine option ''option' reference cannot appear twice, once in the 'value A'.'value C' list and one in the 'value B'.'value C' list

The IMPORT FGL 'reference' reference cannot appear twice, once in the 'value A'.'value C' list and one in the 'value B'.'value C' list

The front call 'reference' reference cannot appear twice, once in the 'value A'.'value C' list and one in the 'value B'.'value C' list

Two ruleids (deprecated|backwardCompatibility) defined in gslint rules file with same option can not contain the same value. Fix your rules file.

'value A' doesn't respect the 'object.function' front call convention rule syntax (For example WINCOM.CallMethod) in the 'value B'.'value C' rule property

Error message and resolution should be self-explanatory.

There is no rule to check.

Error message and resolution should be self-explanatory.

The Abstract Tree Syntax is not valid.

Error message and resolution should be self-explanatory.

Cannot load Abstract Tree Syntax from STDIN

Error message and resolution should be self-explanatory.

Cannot extract Abstract Tree Syntax from the file 'file'

Error message and resolution should be self-explanatory.

'value A' doesn't respect the 'value B' prefix naming convention rule

For further information, see Identifier naming convention rules.

Decimal precision is mandatory

For further information, see Mandatory DECIMAL and MONEY precision rules.

Avoid multi-line string

For further information, see Multi-line STRING definition rules.

Do not declare more than one variable per type inside a single declaration

For further information, see Only one variable per type inside a single declaration rules.

Do not declare more than one constant per declaration

Error message and resolution should be self-explanatory.

Do not declare more than one variable per declaration

For further information, see Only one variable per declaration rules.

Do not declare more than one type per declaration

Error message and resolution should be self-explanatory.

The 'value' is supported for backward compatibility

For further information, see Detect backwards compatibility features.

The 'value' is deprecated, and may be removed in a future version

For further information, see Detect deprecated features rules.