ErrorConfig
This class is used to specify how errors should be produced by the
Lexer class.
The Lexer is set up to produce a variety of different
errors via label-ing, explain-ing, and filter-ing, and some applications of
the Verified and Preventative error patterns. The exact content of those
errors can be configured here. Errors can be suppressed or specified with different
levels of detail, or even switching between vanilla or specialised errors.
This class should be used by extending it and overriding the relevant parts: all methods here are non-abstract and their default is documented inside. Not configuring something does not mean it will not appear in the message, but will mean it uses the underlying base errors.
Attributes
- Since:
4.1.0
- Source:
- ErrorConfig.scala
- Graph
- Supertypes
Members list
Symbol Errors
These control the errors generated with the symbol component of the Lexer.
How to refer to a > symbol in an error message.
How to refer to a > symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "closing angle bracket"
- Source:
- ErrorConfig.scala
How to refer to a } symbol in an error message.
How to refer to a } symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "closing brace"
- Source:
- ErrorConfig.scala
How to refer to a ) symbol in an error message.
How to refer to a ) symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "closing parenthesis"
- Source:
- ErrorConfig.scala
How to refer to a ] symbol in an error message.
How to refer to a ] symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "closing square bracket"
- Source:
- ErrorConfig.scala
How to refer to a : symbol in an error message.
How to refer to a : symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "colon"
- Source:
- ErrorConfig.scala
How to refer to a , symbol in an error message.
How to refer to a , symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "comma"
- Source:
- ErrorConfig.scala
How to refer to a . symbol in an error message.
How to refer to a . symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "dot"
- Source:
- ErrorConfig.scala
How the required end of a given keyword should be specified in an error.
How the required end of a given keyword should be specified in an error.
Attributes
- Since:
4.1.0
- Note:
defaults to "end of symbol"
- Source:
- ErrorConfig.scala
How the required end of a given operator should be specified in an error.
How the required end of a given operator should be specified in an error.
Attributes
- Since:
4.1.0
- Note:
defaults to "end of symbol"
- Source:
- ErrorConfig.scala
How a given keyword should be described in an error message.
How a given keyword should be described in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to labelling with the symbol itself
- Source:
- ErrorConfig.scala
How to refer to a < symbol in an error message.
How to refer to a < symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "open angle bracket"
- Source:
- ErrorConfig.scala
How to refer to a { symbol in an error message.
How to refer to a { symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "open brace"
- Source:
- ErrorConfig.scala
How to refer to a ( symbol in an error message.
How to refer to a ( symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "open parenthesis"
- Source:
- ErrorConfig.scala
How to refer to a [ symbol in an error message.
How to refer to a [ symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "open square bracket"
- Source:
- ErrorConfig.scala
How a given operator should be described in an error message.
How a given operator should be described in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to labelling with the symbol itself
- Source:
- ErrorConfig.scala
How to refer to a ; symbol in an error message.
How to refer to a ; symbol in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "semicolon"
- Source:
- ErrorConfig.scala
Space Errors
These control the errors generated with the space component of the Lexer.
How the end of a single-line comment should be described or explained.
How the end of a single-line comment should be described or explained.
Attributes
- Since:
4.1.0
- Note:
defaults to "end of comment"
- Source:
- ErrorConfig.scala
How the end of a multi-line comment should be described or explained.
How the end of a multi-line comment should be described or explained.
Attributes
- Since:
4.1.0
- Note:
defaults to "end of comment"
- Source:
- ErrorConfig.scala
Text Errors
These control the errors generated with the text component of the Lexer.
When a non-ASCII character is found in a ASCII-only character literal, specifies how this should be reported.
When a non-ASCII character is found in a ASCII-only character literal, specifies how this should be reported.
Attributes
- Since:
4.1.0
- Note:
defaults to a filter generating the reason "non-ascii character"
- Source:
- ErrorConfig.scala
When a non-BMP character is found in a BMP-only character literal, specifies how this should be reported.
When a non-BMP character is found in a BMP-only character literal, specifies how this should be reported.
Attributes
- Since:
4.1.0
- Note:
defaults to a filter generating the reason "non-BMP character"
- Source:
- ErrorConfig.scala
When a non-Latin1 character is found in a Latin1-only character literal, specifies how this should be reported.
When a non-Latin1 character is found in a Latin1-only character literal, specifies how this should be reported.
Attributes
- Since:
4.1.0
- Note:
defaults to a filter generating the reason "non-latin1 character"
- Source:
- ErrorConfig.scala
When a numeric escape sequence is not legal, this describes how to report that error, given the original illegal character.
When a numeric escape sequence is not legal, this describes how to report that error, given the original illegal character.
Attributes
- maxEscape
the largest legal escape character
- radix
the radix used for this numeric escape sequence
- Since:
4.1.0
- Note:
defaults to a specialised message stating if the character is larger than the given maximum, or just an illegal codepoint otherwise.
- Source:
- ErrorConfig.scala
When a numeric escape sequence requires a specific number of digits but this was not successfully parsed, this describes how to report that error given the number of successfully parsed digits up this point.
When a numeric escape sequence requires a specific number of digits but this was not successfully parsed, this describes how to report that error given the number of successfully parsed digits up this point.
Attributes
- needed
the possible numbers of digits required
- radix
the radix used for this numeric escape sequence
- Since:
4.1.0
- Note:
defaults to a specialised message describing how many digits are required but how many were present.
- Source:
- ErrorConfig.scala
When a non-ASCII character is found in a ASCII-only string literal, specifies how this should be reported.
When a non-ASCII character is found in a ASCII-only string literal, specifies how this should be reported.
Attributes
- Since:
4.1.0
- Note:
defaults to a filter generating a specialised message of "non-ascii characters in string literal, this is not allowed"
- Source:
- ErrorConfig.scala
When a non-Latin1 character is found in a Latin1-only string literal, specifies how this should be reported.
When a non-Latin1 character is found in a Latin1-only string literal, specifies how this should be reported.
Attributes
- Since:
4.1.0
- Note:
defaults to a filter generating a specialised message of "non-latin1 characters in string literal, this is not allowed"
- Source:
- ErrorConfig.scala
How a ASCII character literal should be referred to or explained in error messages.
How a ASCII character literal should be referred to or explained in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the closing quote of an ASCII character literal should be referred to in error messages.
How the closing quote of an ASCII character literal should be referred to in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How a BMP (Basic Multilingual Plane) character literal should be referred to or explained in error messages.
How a BMP (Basic Multilingual Plane) character literal should be referred to or explained in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the closing quote of a BMP character literal should be referred to in error messages.
How the closing quote of a BMP character literal should be referred to in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How a Latin1 (extended ASCII) character literal should be referred to or explained in error messages.
How a Latin1 (extended ASCII) character literal should be referred to or explained in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the closing quote of a Latin1 character literal should be referred to in error messages.
How the closing quote of a Latin1 character literal should be referred to in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How a UTF-16 character literal should be referred to or explained in error messages.
How a UTF-16 character literal should be referred to or explained in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the closing quote of a UTF-16 character literal should be referred to in error messages.
How the closing quote of a UTF-16 character literal should be referred to in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the end of an escape sequence (anything past the opening character) should be referred to or explained within an error message.
How the end of an escape sequence (anything past the opening character) should be referred to or explained within an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to label of "end of escape sequence" with a reason of "invalid escape sequence"
- Source:
- ErrorConfig.scala
How a numeric escape sequence (after the opening character) should be referred to or explained in error messages.
How a numeric escape sequence (after the opening character) should be referred to or explained in error messages.
Attributes
- radix
the radix this specific configuration applies to
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the end of a numeric escape sequence (after a prefix) should be referred to or explained in error messages.
How the end of a numeric escape sequence (after a prefix) should be referred to or explained in error messages.
Attributes
- prefix
the character that started this sequence
- radix
the radix this specific configuration applies to
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How an escape sequence should be referred to or explained in error messages.
How an escape sequence should be referred to or explained in error messages.
Attributes
- See also:
labelEscapeEndfor how to explain what valid escape sequences may be when the lead character has been parsed.- Since:
4.1.0
- Note:
defaults to label of "escape sequence"
explains for escape characters do not work in string literals.
- Source:
- ErrorConfig.scala
How a graphic character (a regular character in the literal) should be referred to or explained in error messages.
How a graphic character (a regular character in the literal) should be referred to or explained in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to a label of "graphic character"
explains for graphic characters do not work in string literals.
- Source:
- ErrorConfig.scala
How a ASCII-only string literal should be referred to or explained in error messages.
How a ASCII-only string literal should be referred to or explained in error messages.
Attributes
- multi
whether this is for multi-line strings
- raw
whether this is for raw strings
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the closing quote(s) of an ASCII string literal should be referred to in error messages.
How the closing quote(s) of an ASCII string literal should be referred to in error messages.
Attributes
- multi
whether this is for multi-line strings
- raw
whether this is for raw strings
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How general string characters should be referred to in error messages.
How general string characters should be referred to in error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to label of "string character"
this superscedes
labelGraphicCharacterandlabelEscapeSequencewithin string literals.- Source:
- ErrorConfig.scala
How zero-width escape characters should be referred to within error messages.
How zero-width escape characters should be referred to within error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How string gaps should be referred to within error messages.
How string gaps should be referred to within error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to label of "string gap"
- Source:
- ErrorConfig.scala
How the end of a string gap (the closing slash) should be referred to within error messages.
How the end of a string gap (the closing slash) should be referred to within error messages.
Attributes
- Since:
4.1.0
- Note:
defaults to label of "end of string gap"
- Source:
- ErrorConfig.scala
How a Latin1-only string literal should be referred to or explained in error messages.
How a Latin1-only string literal should be referred to or explained in error messages.
Attributes
- multi
whether this is for multi-line strings
- raw
whether this is for raw strings
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the closing quote(s) of a Latin1 string literal should be referred to in error messages.
How the closing quote(s) of a Latin1 string literal should be referred to in error messages.
Attributes
- multi
whether this is for multi-line strings
- raw
whether this is for raw strings
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How a UTF-16-only string should literal be referred to or explained in error messages.
How a UTF-16-only string should literal be referred to or explained in error messages.
Attributes
- multi
whether this is for multi-line strings
- raw
whether this is for raw strings
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the closing quote(s) of a UTF-16 string literal should be referred to in error messages.
How the closing quote(s) of a UTF-16 string literal should be referred to in error messages.
Attributes
- multi
whether this is for multi-line strings
- raw
whether this is for raw strings
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
Character literals parse either graphic characters or escape characters.
Character literals parse either graphic characters or escape characters. This configuration allows for individual errors when a character not part of either graphic characters or escape characters is encountered.
Attributes
- Since:
4.1.0
- Note:
defaults to
Unverified- Source:
- ErrorConfig.scala
String literals parse either graphic characters or escape characters.
String literals parse either graphic characters or escape characters. This configuration allows for individual errors when a character not part of either graphic characters or escape characters is encountered.
Attributes
- Since:
4.1.0
- Note:
defaults to
Unverified- Source:
- ErrorConfig.scala
Name Errors
These control the errors generated with the names component of the Lexer.
When parsing identifiers that are required to have specific start characters, how bad identifiers should be reported.
When parsing identifiers that are required to have specific start characters, how bad identifiers should be reported.
Attributes
- Since:
4.1.0
- Note:
defaults to unexpected "identifier v"
- Source:
- ErrorConfig.scala
When parsing operators that are required to have specific start/end characters, how bad operators should be reported.
When parsing operators that are required to have specific start/end characters, how bad operators should be reported.
Attributes
- Since:
4.1.0
- Note:
defaults to unexpected "operator v"
- Source:
- ErrorConfig.scala
How an identifier should be referred to in an error message.
How an identifier should be referred to in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "identifier"
- Source:
- ErrorConfig.scala
How a user-defined operator should be referred to in an error message.
How a user-defined operator should be referred to in an error message.
Attributes
- Since:
4.1.0
- Note:
defaults to "operator"
- Source:
- ErrorConfig.scala
How an illegally parsed hard keyword should be referred to as an unexpected component.
How an illegally parsed hard keyword should be referred to as an unexpected component.
Attributes
- v
the illegal identifier
- Since:
4.1.0
- Note:
defaults to "keyword v"
- Source:
- ErrorConfig.scala
How an illegally parsed hard operator should be referred to as an unexpected component.
How an illegally parsed hard operator should be referred to as an unexpected component.
Attributes
- Since:
4.1.0
- Note:
defaults to "reserved operator v"
- Source:
- ErrorConfig.scala
Numeric Errors
These control the errors generated with the numeric component of the Lexer.
The name given to doubles.
The name given to doubles.
Attributes
- Since:
4.1.0
- Note:
defaults to "IEEE 754 double-precision float"
- Source:
- ErrorConfig.scala
This method describes the content of the error when an integer literal is parsed and it is not within the required bit-width.
This method describes the content of the error when an integer literal is parsed and it is not within the required bit-width.
Attributes
- max
the largest value the integer could have taken
- min
the smallest value the integer could have taken
- nativeRadix
the radix that the integer was parsed using
- Since:
4.1.0
- Note:
defaults to a specialised error describing what the min and max bounds are.
- Source:
- ErrorConfig.scala
This method describes the content of the error when a real literal is parsed and it is not representable exactly as the required precision.
This method describes the content of the error when a real literal is parsed and it is not representable exactly as the required precision.
Attributes
- name
the name of the required precision (one of
doubleNameorfloatName)- Since:
4.1.0
- Note:
defaults to a specialised error stating that the literal is not exactly representable.
- Source:
- ErrorConfig.scala
This method describes the content of the error when a real literal is parsed and it is not within the bounds perscribed by the required precision.
This method describes the content of the error when a real literal is parsed and it is not within the bounds perscribed by the required precision.
Attributes
- max
the largest value the real could have taken
- min
the smallest value the real could have taken
- name
the name of the required precision (one of
doubleNameorfloatName)- Since:
4.1.0
- Note:
defaults to a specialised error describing what the min and max bounds are.
- Source:
- ErrorConfig.scala
The name given to floats.
The name given to floats.
Attributes
- Since:
4.1.0
- Note:
defaults to "IEEE 754 single-precision float"
- Source:
- ErrorConfig.scala
How the fact that the end of a binary integer literal is expected should be referred to within an error.
How the fact that the end of a binary integer literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerNumberEnd- Source:
- ErrorConfig.scala
How the fact that the end of a decimal integer literal is expected should be referred to within an error.
How the fact that the end of a decimal integer literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerNumberEnd- Source:
- ErrorConfig.scala
How the fact that the end of a hexadecimal integer literal is expected should be referred to within an error.
How the fact that the end of a hexadecimal integer literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerNumberEnd- Source:
- ErrorConfig.scala
How the fact that the end of a generic integer literal is expected should be referred to within an error.
How the fact that the end of a generic integer literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the fact that the end of an octal integer literal is expected should be referred to within an error.
How the fact that the end of an octal integer literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerNumberEnd- Source:
- ErrorConfig.scala
How signed binary integers should be referred to or explained within an error.
How signed binary integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerSignedNumber- Source:
- ErrorConfig.scala
How signed binary integers should of a given bit-width be referred to or explained within an error.
How signed binary integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerSignedBinary- Source:
- ErrorConfig.scala
How signed decimal integers should be referred to or explained within an error.
How signed decimal integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerSignedNumber- Source:
- ErrorConfig.scala
How signed decimal integers should of a given bit-width be referred to or explained within an error.
How signed decimal integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerSignedDecimal- Source:
- ErrorConfig.scala
How signed hexadecimal integers should be referred to or explained within an error.
How signed hexadecimal integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerSignedNumber- Source:
- ErrorConfig.scala
How signed hexadecimal integers should of a given bit-width be referred to or explained within an error.
How signed hexadecimal integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerSignedHexadecimal- Source:
- ErrorConfig.scala
How generic signed integers should be referred to or explained within an error.
How generic signed integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How generic signed integers should of a given bit-width be referred to or explained within an error.
How generic signed integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How signed octal integers should be referred to or explained within an error.
How signed octal integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerSignedNumber- Source:
- ErrorConfig.scala
How signed octal integers should of a given bit-width be referred to or explained within an error.
How signed octal integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerSignedOctal- Source:
- ErrorConfig.scala
How unsigned binary integers should be referred to or explained within an error.
How unsigned binary integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerUnsignedNumber- Source:
- ErrorConfig.scala
How unsigned binary integers should of a given bit-width be referred to or explained within an error.
How unsigned binary integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerUnsignedNumber- Source:
- ErrorConfig.scala
How unsigned decimal integers should be referred to or explained within an error.
How unsigned decimal integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerUnsignedNumber- Source:
- ErrorConfig.scala
How unsigned decimal integers should of a given bit-width be referred to or explained within an error.
How unsigned decimal integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerUnsignedNumber- Source:
- ErrorConfig.scala
How unsigned hexadecimal integers should be referred to or explained within an error.
How unsigned hexadecimal integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerUnsignedNumber- Source:
- ErrorConfig.scala
How unsigned hexadecimal integers should of a given bit-width be referred to or explained within an error.
How unsigned hexadecimal integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerUnsignedNumber- Source:
- ErrorConfig.scala
How generic unsigned integers should be referred to or explained within an error.
How generic unsigned integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How generic unsigned integers should of a given bit-width be referred to or explained within an error.
How generic unsigned integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How unsigned octal integers should be referred to or explained within an error.
How unsigned octal integers should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerUnsignedNumber- Source:
- ErrorConfig.scala
How unsigned octal integers should of a given bit-width be referred to or explained within an error.
How unsigned octal integers should of a given bit-width be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelIntegerUnsignedNumber- Source:
- ErrorConfig.scala
How a numeric break character should (like _) be referred to or explained within an error.
How a numeric break character should (like _) be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Source:
- ErrorConfig.scala
How binary reals should be referred to or explained within an error.
How binary reals should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumber- Source:
- ErrorConfig.scala
How the fact that the end of a binary real literal is expected should be referred to within an error.
How the fact that the end of a binary real literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumberEnd- Source:
- ErrorConfig.scala
How decimal reals should be referred to or explained within an error.
How decimal reals should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumber- Source:
- ErrorConfig.scala
How the fact that the end of a decimal real literal is expected should be referred to within an error.
How the fact that the end of a decimal real literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumberEnd- Source:
- ErrorConfig.scala
How the "dot" that separates the integer and fractional part of a real number should be referred to or explained within an error.
How the "dot" that separates the integer and fractional part of a real number should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How binary doubles should be referred to or explained within an error.
How binary doubles should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealBinary- Source:
- ErrorConfig.scala
How decimal doubles should be referred to or explained within an error.
How decimal doubles should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealDecimal- Source:
- ErrorConfig.scala
How hexadecimal doubles should be referred to or explained within an error.
How hexadecimal doubles should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealHexadecimal- Source:
- ErrorConfig.scala
How generic doubles should be referred to or explained within an error.
How generic doubles should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumber- Source:
- ErrorConfig.scala
How octal doubles should be referred to or explained within an error.
How octal doubles should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealOctal- Source:
- ErrorConfig.scala
How the trailing exponents of a real number should be referred to or explained within an error.
How the trailing exponents of a real number should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the fact that the end of an exponent part of a real literal is expected should be referred to within an error.
How the fact that the end of an exponent part of a real literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How binary floats should be referred to or explained within an error.
How binary floats should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealBinary- Source:
- ErrorConfig.scala
How decimal floats should be referred to or explained within an error.
How decimal floats should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealDecimal- Source:
- ErrorConfig.scala
How hexadecimal floats should be referred to or explained within an error.
How hexadecimal floats should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealHexadecimal- Source:
- ErrorConfig.scala
How generic floats should be referred to or explained within an error.
How generic floats should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumber- Source:
- ErrorConfig.scala
How octal floats should be referred to or explained within an error.
How octal floats should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealOctal- Source:
- ErrorConfig.scala
How hexadecimal reals should be referred to or explained within an error.
How hexadecimal reals should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumber- Source:
- ErrorConfig.scala
How the fact that the end of a hexadecimal real literal is expected should be referred to within an error.
How the fact that the end of a hexadecimal real literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumberEnd- Source:
- ErrorConfig.scala
How generic reals should be referred to or explained within an error.
How generic reals should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How the fact that the end of a generic real literal is expected should be referred to within an error.
How the fact that the end of a generic real literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
NotConfigured- Source:
- ErrorConfig.scala
How octal reals should be referred to or explained within an error.
How octal reals should be referred to or explained within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumber- Source:
- ErrorConfig.scala
How the fact that the end of an octal real literal is expected should be referred to within an error.
How the fact that the end of an octal real literal is expected should be referred to within an error.
Attributes
- Since:
4.1.0
- Note:
defaults to
labelRealNumberEnd- Source:
- ErrorConfig.scala
Even if leading and trailing zeros can be dropped, . is not a valid real number: this
method specifies how to report that to the user.
Even if leading and trailing zeros can be dropped, . is not a valid real number: this
method specifies how to report that to the user.
Attributes
- Since:
4.1.0
- Note:
defaults to a vanilla explain: "a real number cannot drop both a leading and trailing zero"
- Source:
- ErrorConfig.scala