ErrorConfig

class ErrorConfig extends AnyRef

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.

Source: ErrorConfig.scala
Since: 4.1.0

Linear Supertypes

AnyRef, Any

Ordering

Grouped
Alphabetic
By Inheritance

Inherited

ErrorConfig
AnyRef
Any

Hide All
Show All

Visibility

Public
Protected

Instance Constructors

new ErrorConfig()

Value Members

final def !=(arg0: Any): Boolean
Definition Classes
AnyRef → Any
final def ##: Int
Definition Classes
AnyRef → Any
final def ==(arg0: Any): Boolean
Definition Classes
AnyRef → Any
final def asInstanceOf[T0]: T0
Definition Classes
Any
def clone(): AnyRef
Attributes
protected[lang]
Definition Classes
AnyRef
Annotations
@throws(classOf[java.lang.CloneNotSupportedException]) @native()
def doubleName: String
What is the name given to doubles.
What is the name given to doubles.
Since
4.1.0
Note
defaults to "IEEE 754 double-precision float"
final def eq(arg0: AnyRef): Boolean
Definition Classes
AnyRef
def equals(arg0: AnyRef): Boolean
Definition Classes
AnyRef → Any
def filterCharNonAscii: VanillaFilterConfig[Int]
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.
Since
4.1.0
Note
defaults to a filter generating the reason "non-ascii character"
def filterCharNonBasicMultilingualPlane: VanillaFilterConfig[Int]
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.
Since
4.1.0
Note
defaults to a filter generating the reason "non-BMP character"
def filterCharNonLatin1: VanillaFilterConfig[Int]
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.
Since
4.1.0
Note
defaults to a filter generating the reason "non-latin1 character"
def filterEscapeCharNumericSequenceIllegal(maxEscape: Int, radix: Int): SpecialisedFilterConfig[BigInt]
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.
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.
def filterEscapeCharRequiresExactDigits(radix: Int, needed: Seq[Int]): SpecialisedFilterConfig[Int]
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.
radix
the radix used for this numeric escape sequence
needed
the possible numbers of digits required
Since
4.1.0
Note
defaults to a specialised message describing how many digits are required but how many were present.
def filterIntegerOutOfBounds(min: BigInt, max: BigInt, nativeRadix: Int): FilterConfig[BigInt]
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.
min
the smallest value the integer could have taken
max
the largest 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.
def filterNameIllFormedIdentifier: FilterConfig[String]
When parsing identifiers that are required to have specific start characters, how should bad identifiers be reported.
When parsing identifiers that are required to have specific start characters, how should bad identifiers be reported.
Since
4.1.0
Note
defaults to unexpected "identifier v"
def filterNameIllFormedOperator: FilterConfig[String]
When parsing operators that are required to have specific start/end characters, how should bad operators be reported.
When parsing operators that are required to have specific start/end characters, how should bad operators be reported.
Since
4.1.0
Note
defaults to unexpected "operator v"
def filterRealNotExact(name: String): FilterConfig[BigDecimal]
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.
name
the name of the required precision (one of doubleName or floatName)
Since
4.1.0
Note
defaults to a specialised error stating that the literal is not exactly representable.
def filterRealOutOfBounds(name: String, min: BigDecimal, max: BigDecimal): FilterConfig[BigDecimal]
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.
name
the name of the required precision (one of doubleName or floatName)
min
the smallest value the real could have taken
max
the largest value the real could have taken
Since
4.1.0
Note
defaults to a specialised error describing what the min and max bounds are.
def filterStringNonAscii: SpecialisedFilterConfig[StringBuilder]
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.
Since
4.1.0
Note
defaults to a filter generating a specialised message of "non-ascii characters in string literal, this is not allowed"
def filterStringNonLatin1: SpecialisedFilterConfig[StringBuilder]
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.
Since
4.1.0
Note
defaults to a filter generating a specialised message of "non-latin1 characters in string literal, this is not allowed"
def finalize(): Unit
Attributes
protected[lang]
Definition Classes
AnyRef
Annotations
@throws(classOf[java.lang.Throwable])
def floatName: String
What is the name given to floats.
What is the name given to floats.
Since
4.1.0
Note
defaults to "IEEE 754 single-precision float"
final def getClass(): Class[_ <: AnyRef]
Definition Classes
AnyRef → Any
Annotations
@native()
def hashCode(): Int
Definition Classes
AnyRef → Any
Annotations
@native()
final def isInstanceOf[T0]: Boolean
Definition Classes
Any
def labelCharAscii: LabelWithExplainConfig
How should a ASCII character literal be referred to or explained in error messages.
How should a ASCII character literal be referred to or explained in error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelCharAsciiEnd: LabelConfig
How should the closing quote of an ASCII character literal be referred to in error messages.
How should the closing quote of an ASCII character literal be referred to in error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelCharBasicMultilingualPlane: LabelWithExplainConfig
How should a BMP (Basic Multilingual Plane) character literal be referred to or explained in error messages.
How should a BMP (Basic Multilingual Plane) character literal be referred to or explained in error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelCharBasicMultilingualPlaneEnd: LabelConfig
How should the closing quote of a BMP character literal be referred to in error messages.
How should the closing quote of a BMP character literal be referred to in error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelCharLatin1: LabelWithExplainConfig
How should a Latin1 (extended ASCII) character literal be referred to or explained in error messages.
How should a Latin1 (extended ASCII) character literal be referred to or explained in error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelCharLatin1End: LabelConfig
How should the closing quote of a Latin1 character literal be referred to in error messages.
How should the closing quote of a Latin1 character literal be referred to in error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelCharUtf16: LabelWithExplainConfig
How should a UTF-16 character literal be referred to or explained in error messages.
How should a UTF-16 character literal be referred to or explained in error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelCharUtf16End: LabelConfig
How should the closing quote of a UTF-16 character literal be referred to in error messages.
How should the closing quote of a UTF-16 character literal be referred to in error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelEscapeEnd: LabelWithExplainConfig
How should the end of an escape sequence (anything past the opening character) be referred to or explained within an error message.
How should the end of an escape sequence (anything past the opening character) be referred to or explained within an error message.
Since
4.1.0
Note
defaults to label of "end of escape sequence" with a reason of "invalid escape sequence"
def labelEscapeNumeric(radix: Int): LabelWithExplainConfig
How should a numeric escape sequence (after the opening character) be referred to or explained in error messages.
How should a numeric escape sequence (after the opening character) be referred to or explained in error messages.
radix
the radix this specific configuration applies to
Since
4.1.0
Note
defaults to NotConfigured
def labelEscapeNumericEnd(prefix: Char, radix: Int): LabelWithExplainConfig
How should the end of a numeric escape sequence (after a prefix) be referred to or explained in error messages.
How should the end of a numeric escape sequence (after a prefix) be referred to or explained in error messages.
prefix
the character that started this sequence
radix
the radix this specific configuration applies to
Since
4.1.0
Note
defaults to NotConfigured
def labelEscapeSequence: LabelWithExplainConfig
How should an escape sequence be referred to or explained in error messages.
How should an escape sequence be referred to or explained in error messages.
Since
4.1.0
Note
defaults to label of "escape sequence"
,
explains for escape characters do not work in string literals.
See also
labelEscapeEnd for how to explain what valid escape sequences may be when the lead character has been parsed.
def labelGraphicCharacter: LabelWithExplainConfig
How should a graphic character (a regular character in the literal) be referred to or explained in error messages.
How should a graphic character (a regular character in the literal) be referred to or explained in error messages.
Since
4.1.0
Note
defaults to a label of "graphic character"
,
explains for graphic characters do not work in string literals.
def labelIntegerBinaryEnd: LabelConfig
How should the fact that the end of a binary integer literal is expected be referred to within an error.
How should the fact that the end of a binary integer literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to labelIntegerNumberEnd
def labelIntegerDecimalEnd: LabelConfig
How should the fact that the end of a decimal integer literal is expected be referred to within an error.
How should the fact that the end of a decimal integer literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to labelIntegerNumberEnd
def labelIntegerHexadecimalEnd: LabelConfig
How should the fact that the end of a hexadecimal integer literal is expected be referred to within an error.
How should the fact that the end of a hexadecimal integer literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to labelIntegerNumberEnd
def labelIntegerNumberEnd: LabelConfig
How should the fact that the end of a generic integer literal is expected be referred to within an error.
How should the fact that the end of a generic integer literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelIntegerOctalEnd: LabelConfig
How should the fact that the end of an octal integer literal is expected be referred to within an error.
How should the fact that the end of an octal integer literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to labelIntegerNumberEnd
def labelIntegerSignedBinary(bits: Int): LabelWithExplainConfig
How should signed binary integers of a given bit-width be referred to or explained within an error.
How should signed binary integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerSignedBinary
def labelIntegerSignedBinary: LabelWithExplainConfig
How should signed binary integers be referred to or explained within an error.
How should signed binary integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerSignedNumber
def labelIntegerSignedDecimal(bits: Int): LabelWithExplainConfig
How should signed decimal integers of a given bit-width be referred to or explained within an error.
How should signed decimal integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerSignedDecimal
def labelIntegerSignedDecimal: LabelWithExplainConfig
How should signed decimal integers be referred to or explained within an error.
How should signed decimal integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerSignedNumber
def labelIntegerSignedHexadecimal(bits: Int): LabelWithExplainConfig
How should signed hexadecimal integers of a given bit-width be referred to or explained within an error.
How should signed hexadecimal integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerSignedHexadecimal
def labelIntegerSignedHexadecimal: LabelWithExplainConfig
How should signed hexadecimal integers be referred to or explained within an error.
How should signed hexadecimal integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerSignedNumber
def labelIntegerSignedNumber(bits: Int): LabelWithExplainConfig
How should generic signed integers of a given bit-width be referred to or explained within an error.
How should generic signed integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelIntegerSignedNumber: LabelWithExplainConfig
How should generic signed integers be referred to or explained within an error.
How should generic signed integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelIntegerSignedOctal(bits: Int): LabelWithExplainConfig
How should signed octal integers of a given bit-width be referred to or explained within an error.
How should signed octal integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerSignedOctal
def labelIntegerSignedOctal: LabelWithExplainConfig
How should signed octal integers be referred to or explained within an error.
How should signed octal integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerSignedNumber
def labelIntegerUnsignedBinary(bits: Int): LabelWithExplainConfig
How should unsigned binary integers of a given bit-width be referred to or explained within an error.
How should unsigned binary integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerUnsignedNumber
def labelIntegerUnsignedBinary: LabelWithExplainConfig
How should unsigned binary integers be referred to or explained within an error.
How should unsigned binary integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerUnsignedNumber
def labelIntegerUnsignedDecimal(bits: Int): LabelWithExplainConfig
How should unsigned decimal integers of a given bit-width be referred to or explained within an error.
How should unsigned decimal integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerUnsignedNumber
def labelIntegerUnsignedDecimal: LabelWithExplainConfig
How should unsigned decimal integers be referred to or explained within an error.
How should unsigned decimal integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerUnsignedNumber
def labelIntegerUnsignedHexadecimal(bits: Int): LabelWithExplainConfig
How should unsigned hexadecimal integers of a given bit-width be referred to or explained within an error.
How should unsigned hexadecimal integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerUnsignedNumber
def labelIntegerUnsignedHexadecimal: LabelWithExplainConfig
How should unsigned hexadecimal integers be referred to or explained within an error.
How should unsigned hexadecimal integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerUnsignedNumber
def labelIntegerUnsignedNumber(bits: Int): LabelWithExplainConfig
How should generic unsigned integers of a given bit-width be referred to or explained within an error.
How should generic unsigned integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelIntegerUnsignedNumber: LabelWithExplainConfig
How should generic unsigned integers be referred to or explained within an error.
How should generic unsigned integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelIntegerUnsignedOctal(bits: Int): LabelWithExplainConfig
How should unsigned octal integers of a given bit-width be referred to or explained within an error.
How should unsigned octal integers of a given bit-width be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerUnsignedNumber
def labelIntegerUnsignedOctal: LabelWithExplainConfig
How should unsigned octal integers be referred to or explained within an error.
How should unsigned octal integers be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelIntegerUnsignedNumber
def labelNameIdentifier: String
How should an identifier be referred to in an error message.
How should an identifier be referred to in an error message.
Since
4.1.0
Note
defaults to "identifier"
def labelNameOperator: String
How should a user-defined operator be referred to in an error message.
How should a user-defined operator be referred to in an error message.
Since
4.1.0
Note
defaults to "operator"
def labelNumericBreakChar: LabelWithExplainConfig
How should a numeric break character (like _) be referred to or explained within an error.
How should a numeric break character (like _) be referred to or explained within an error.
Since
4.1.0
def labelRealBinary: LabelWithExplainConfig
How should binary reals should be referred to or explained within an error.
How should binary reals should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealNumber
def labelRealBinaryEnd: LabelConfig
How should the fact that the end of a binary real literal is expected be referred to within an error.
How should the fact that the end of a binary real literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to labelRealNumberEnd
def labelRealDecimal: LabelWithExplainConfig
How should decimal reals should be referred to or explained within an error.
How should decimal reals should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealNumber
def labelRealDecimalEnd: LabelConfig
How should the fact that the end of a decimal real literal is expected be referred to within an error.
How should the fact that the end of a decimal real literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to labelRealNumberEnd
def labelRealDot: LabelWithExplainConfig
How should the "dot" that separates the integer and fractional part of a real number should be referred to or explained within an error.
How should the "dot" that separates the integer and fractional part of a real number should be referred to or explained within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelRealDoubleBinary: LabelWithExplainConfig
How should binary doubles should be referred to or explained within an error.
How should binary doubles should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealBinary
def labelRealDoubleDecimal: LabelWithExplainConfig
How should decimal doubles should be referred to or explained within an error.
How should decimal doubles should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealDecimal
def labelRealDoubleHexadecimal: LabelWithExplainConfig
How should hexadecimal doubles should be referred to or explained within an error.
How should hexadecimal doubles should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealHexadecimal
def labelRealDoubleNumber: LabelWithExplainConfig
How should generic doubles should be referred to or explained within an error.
How should generic doubles should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealNumber
def labelRealDoubleOctal: LabelWithExplainConfig
How should octal doubles should be referred to or explained within an error.
How should octal doubles should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealOctal
def labelRealExponent: LabelWithExplainConfig
How should the trailing exponents of a real number be referred to or explained within an error.
How should the trailing exponents of a real number be referred to or explained within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelRealExponentEnd: LabelConfig
How should the fact that the end of an exponent part of a real literal is expected be referred to within an error.
How should the fact that the end of an exponent part of a real literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelRealFloatBinary: LabelWithExplainConfig
How should binary floats should be referred to or explained within an error.
How should binary floats should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealBinary
def labelRealFloatDecimal: LabelWithExplainConfig
How should decimal floats should be referred to or explained within an error.
How should decimal floats should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealDecimal
def labelRealFloatHexadecimal: LabelWithExplainConfig
How should hexadecimal floats should be referred to or explained within an error.
How should hexadecimal floats should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealHexadecimal
def labelRealFloatNumber: LabelWithExplainConfig
How should generic floats should be referred to or explained within an error.
How should generic floats should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealNumber
def labelRealFloatOctal: LabelWithExplainConfig
How should octal floats should be referred to or explained within an error.
How should octal floats should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealOctal
def labelRealHexadecimal: LabelWithExplainConfig
How should hexadecimal reals should be referred to or explained within an error.
How should hexadecimal reals should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealNumber
def labelRealHexadecimalEnd: LabelConfig
How should the fact that the end of a hexadecimal real literal is expected be referred to within an error.
How should the fact that the end of a hexadecimal real literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to labelRealNumberEnd
def labelRealNumber: LabelWithExplainConfig
How should generic reals should be referred to or explained within an error.
How should generic reals should be referred to or explained within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelRealNumberEnd: LabelConfig
How should the fact that the end of a generic real literal is expected be referred to within an error.
How should the fact that the end of a generic real literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to NotConfigured
def labelRealOctal: LabelWithExplainConfig
How should octal reals should be referred to or explained within an error.
How should octal reals should be referred to or explained within an error.
Since
4.1.0
Note
defaults to labelRealNumber
def labelRealOctalEnd: LabelConfig
How should the fact that the end of an octal real literal is expected be referred to within an error.
How should the fact that the end of an octal real literal is expected be referred to within an error.
Since
4.1.0
Note
defaults to labelRealNumberEnd
def labelSpaceEndOfLineComment: LabelWithExplainConfig
How should the end of a single-line comment be described or explained.
How should the end of a single-line comment be described or explained.
Since
4.1.0
Note
defaults to "end of comment"
def labelSpaceEndOfMultiComment: LabelWithExplainConfig
How should the end of a multi-line comment be described or explained.
How should the end of a multi-line comment be described or explained.
Since
4.1.0
Note
defaults to "end of comment"
def labelStringAscii(multi: Boolean, raw: Boolean): LabelWithExplainConfig
How should a ASCII-only string literal be referred to or explained in error messages.
How should a ASCII-only string literal be referred to or explained in error messages.
multi
whether this is for multi-line strings
raw
whether this is for raw strings
Since
4.1.0
Note
defaults to NotConfigured
def labelStringAsciiEnd(multi: Boolean, raw: Boolean): LabelConfig
How should the closing quote(s) of an ASCII string literal be referred to in error messages.
How should the closing quote(s) of an ASCII string literal be referred to in error messages.
multi
whether this is for multi-line strings
raw
whether this is for raw strings
Since
4.1.0
Note
defaults to NotConfigured
def labelStringCharacter: LabelConfig
How should general string characters be referred to in error messages.
How should general string characters be referred to in error messages.
Since
4.1.0
Note
defaults to label of "string character"
,
this superscedes labelGraphicCharacter and labelEscapeSequence within string literals.
def labelStringEscapeEmpty: LabelConfig
How should zero-width escape characters be referred to within error messages.
How should zero-width escape characters be referred to within error messages.
Since
4.1.0
Note
defaults to NotConfigured
def labelStringEscapeGap: LabelConfig
How should string gaps be referred to within error messages.
How should string gaps be referred to within error messages.
Since
4.1.0
Note
defaults to label of "string gap"
def labelStringEscapeGapEnd: LabelConfig
How should the end of a string gap (the closing slash) be referred to within error messages.
How should the end of a string gap (the closing slash) be referred to within error messages.
Since
4.1.0
Note
defaults to label of "end of string gap"
def labelStringLatin1(multi: Boolean, raw: Boolean): LabelWithExplainConfig
How should a Latin1-only string literal be referred to or explained in error messages.
How should a Latin1-only string literal be referred to or explained in error messages.
multi
whether this is for multi-line strings
raw
whether this is for raw strings
Since
4.1.0
Note
defaults to NotConfigured
def labelStringLatin1End(multi: Boolean, raw: Boolean): LabelConfig
How should the closing quote(s) of a Latin1 string literal be referred to in error messages.
How should the closing quote(s) of a Latin1 string literal be referred to in error messages.
multi
whether this is for multi-line strings
raw
whether this is for raw strings
Since
4.1.0
Note
defaults to NotConfigured
def labelStringUtf16(multi: Boolean, raw: Boolean): LabelWithExplainConfig
How should a UTF-16-only string literal be referred to or explained in error messages.
How should a UTF-16-only string literal be referred to or explained in error messages.
multi
whether this is for multi-line strings
raw
whether this is for raw strings
Since
4.1.0
Note
defaults to NotConfigured
def labelStringUtf16End(multi: Boolean, raw: Boolean): LabelConfig
How should the closing quote(s) of a UTF-16 string literal be referred to in error messages.
How should the closing quote(s) of a UTF-16 string literal be referred to in error messages.
multi
whether this is for multi-line strings
raw
whether this is for raw strings
Since
4.1.0
Note
defaults to NotConfigured
def labelSymbolClosingAngle: LabelConfig
How to refer to a > symbol in an error message.
How to refer to a > symbol in an error message.
Since
4.1.0
Note
defaults to "closing angle bracket"
def labelSymbolClosingBrace: LabelConfig
How to refer to a } symbol in an error message.
How to refer to a } symbol in an error message.
Since
4.1.0
Note
defaults to "closing brace"
def labelSymbolClosingParen: LabelConfig
How to refer to a ) symbol in an error message.
How to refer to a ) symbol in an error message.
Since
4.1.0
Note
defaults to "closing parenthesis"
def labelSymbolClosingSquare: LabelConfig
How to refer to a ] symbol in an error message.
How to refer to a ] symbol in an error message.
Since
4.1.0
Note
defaults to "closing square bracket"
def labelSymbolColon: LabelConfig
How to refer to a : symbol in an error message.
How to refer to a : symbol in an error message.
Since
4.1.0
Note
defaults to "colon"
def labelSymbolComma: LabelConfig
How to refer to a , symbol in an error message.
How to refer to a , symbol in an error message.
Since
4.1.0
Note
defaults to "comma"
def labelSymbolDot: LabelConfig
How to refer to a . symbol in an error message.
How to refer to a . symbol in an error message.
Since
4.1.0
Note
defaults to "dot"
def labelSymbolEndOfKeyword(symbol: String): String
How should the required end of a given keyword be specified in an error.
How should the required end of a given keyword be specified in an error.
Since
4.1.0
Note
defaults to "end of symbol"
def labelSymbolEndOfOperator(symbol: String): String
How should the required end of a given operator be specified in an error.
How should the required end of a given operator be specified in an error.
Since
4.1.0
Note
defaults to "end of symbol"
def labelSymbolKeyword(symbol: String): LabelConfig
How should a given keyword be described in an error message.
How should a given keyword be described in an error message.
Since
4.1.0
Note
defaults to labelling with the symbol itself
def labelSymbolOpenAngle: LabelConfig
How to refer to a < symbol in an error message.
How to refer to a < symbol in an error message.
Since
4.1.0
Note
defaults to "open angle bracket"
def labelSymbolOpenBrace: LabelConfig
How to refer to a { symbol in an error message.
How to refer to a { symbol in an error message.
Since
4.1.0
Note
defaults to "open brace"
def labelSymbolOpenParen: LabelConfig
How to refer to a ( symbol in an error message.
How to refer to a ( symbol in an error message.
Since
4.1.0
Note
defaults to "open parenthesis"
def labelSymbolOpenSquare: LabelConfig
How to refer to a [ symbol in an error message.
How to refer to a [ symbol in an error message.
Since
4.1.0
Note
defaults to "open square bracket"
def labelSymbolOperator(symbol: String): LabelConfig
How should a given operator be described in an error message.
How should a given operator be described in an error message.
Since
4.1.0
Note
defaults to labelling with the symbol itself
def labelSymbolSemi: LabelConfig
How to refer to a ; symbol in an error message.
How to refer to a ; symbol in an error message.
Since
4.1.0
Note
defaults to "semicolon"
final def ne(arg0: AnyRef): Boolean
Definition Classes
AnyRef
final def notify(): Unit
Definition Classes
AnyRef
Annotations
@native()
final def notifyAll(): Unit
Definition Classes
AnyRef
Annotations
@native()
def preventRealDoubleDroppedZero: PreventDotIsZeroConfig
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.
Since
4.1.0
Note
defaults to a vanilla explain: "a real number cannot drop both a leading and trailing zero"
final def synchronized[T0](arg0: => T0): T0
Definition Classes
AnyRef
def toString(): String
Definition Classes
AnyRef → Any
def unexpectedNameIllegalIdentifier(v: String): String
How should an illegally parsed hard keyword be referred to as an unexpected component.
How should an illegally parsed hard keyword be referred to as an unexpected component.
v
the illegal identifier
Since
4.1.0
Note
defaults to "keyword v"
def unexpectedNameIllegalOperator(v: String): String
How should an illegally parsed hard operator be referred to as an unexpected component.
How should an illegally parsed hard operator be referred to as an unexpected component.
Since
4.1.0
Note
defaults to "reserved operator v"
def verifiedCharBadCharsUsedInLiteral: VerifiedBadChars
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.
Since
4.1.0
Note
defaults to Unverified
def verifiedStringBadCharsUsedInLiteral: VerifiedBadChars
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.
Since
4.1.0
Note
defaults to Unverified
final def wait(): Unit
Definition Classes
AnyRef
Annotations
@throws(classOf[java.lang.InterruptedException])
final def wait(arg0: Long, arg1: Int): Unit
Definition Classes
AnyRef
Annotations
@throws(classOf[java.lang.InterruptedException])
final def wait(arg0: Long): Unit
Definition Classes
AnyRef
Annotations
@throws(classOf[java.lang.InterruptedException]) @native()

Inherited from AnyRef

Inherited from Any

Name Errors

These control the errors generated with the names component of the Lexer.

Numeric Errors

These control the errors generated with the numeric component of the Lexer.

Space Errors

These control the errors generated with the space component of the Lexer.

Symbol Errors

These control the errors generated with the symbol component of the Lexer.

Text Errors

These control the errors generated with the text component of the Lexer.

Packages

ErrorConfig

class ErrorConfig extends AnyRef

Instance Constructors

Value Members

Inherited from AnyRef

Inherited from Any

Name Errors

Numeric Errors

Space Errors

Symbol Errors

Text Errors

Ungrouped

Packages

ErrorConfig

class ErrorConfig extends AnyRef

Instance Constructors

Value Members

Inherited from AnyRef

Inherited from Any

Name Errors

Numeric Errors

Space Errors

Symbol Errors

Text Errors

Ungrouped

ErrorConfig