package numeric
- Alphabetic
- Public
- Protected
Type Members
- sealed abstract class BreakCharDesc extends AnyRef
This class, and its subtypes, describe how break characters are supported within literals.
This class, and its subtypes, describe how break characters are supported within literals.
- Since
4.0.0
- sealed abstract class ExponentDesc extends AnyRef
This class, and its subtypes, describe how scientific exponent notation can be used within real literals.
This class, and its subtypes, describe how scientific exponent notation can be used within real literals.
- Since
4.0.0
- final case class NumericDesc(literalBreakChar: BreakCharDesc, leadingDotAllowed: Boolean, trailingDotAllowed: Boolean, leadingZerosAllowed: Boolean, positiveSign: PlusSignPresence, integerNumbersCanBeHexadecimal: Boolean, integerNumbersCanBeOctal: Boolean, integerNumbersCanBeBinary: Boolean, realNumbersCanBeHexadecimal: Boolean, realNumbersCanBeOctal: Boolean, realNumbersCanBeBinary: Boolean, hexadecimalLeads: Set[Char], octalLeads: Set[Char], binaryLeads: Set[Char], decimalExponentDesc: ExponentDesc, hexadecimalExponentDesc: ExponentDesc, octalExponentDesc: ExponentDesc, binaryExponentDesc: ExponentDesc) extends Product with Serializable
This class describes how numeric literals, in different bases, should be processed lexically.
This class describes how numeric literals, in different bases, should be processed lexically.
- literalBreakChar
describes if breaks can be found within numeric literals.
- leadingDotAllowed
can a real number omit a leading 0 before the point?
- trailingDotAllowed
can a real number omit a trailing 0 after the point?
- leadingZerosAllowed
are extraneous zeros allowed at the start of decimal numbers?
- positiveSign
describes if positive (
+) signs are allowed, compulsory, or illegal.- integerNumbersCanBeHexadecimal
is it possible for generic "integer numbers" to be hexadecimal?
- integerNumbersCanBeOctal
is it possible for generic "integer numbers" to be octal?
- integerNumbersCanBeBinary
is it possible for generic "integer numbers" to be binary?
- realNumbersCanBeHexadecimal
is it possible for generic "real numbers" to be hexadecimal?
- realNumbersCanBeOctal
is it possible for generic "real numbers" to be octal?
- realNumbersCanBeBinary
is it possible for generic "real numbers" to be binary?
- hexadecimalLeads
what characters begin a hexadecimal literal following a
0(may be empty).- octalLeads
what characters begin an octal literal following a
0(may be empty).- binaryLeads
what characters begin a binary literal following a
0(may be empty).- decimalExponentDesc
describes how scientific exponent notation should work for decimal literals.
- hexadecimalExponentDesc
describes how scientific exponent notation should work for hexadecimal literals.
- octalExponentDesc
describes how scientific exponent notation should work for octal literals.
- binaryExponentDesc
describes how scientific exponent notation should work for binary literals.
- Since
4.0.0
- sealed abstract class PlusSignPresence extends AnyRef
This class, and its subtypes, describe whether or not the plus sign (
+) is allowed in a specific position.This class, and its subtypes, describe whether or not the plus sign (
+) is allowed in a specific position.- Since
4.0.0
Value Members
- object BreakCharDesc
This object contains the concrete subtypes of
BreakCharDesc.This object contains the concrete subtypes of
BreakCharDesc.- Since
4.0.0
- object ExponentDesc
This object contains the concrete subtypes of
ExponentDesc.This object contains the concrete subtypes of
ExponentDesc.- Since
4.0.0
- object NumericDesc extends Serializable
This object contains any preconfigured text definitions.
This object contains any preconfigured text definitions.
- Since
4.0.0
- object PlusSignPresence
This object contains the concrete subtypes for
PlusSignPresence.This object contains the concrete subtypes for
PlusSignPresence.- Since
4.0.0
This is the documentation for Parsley.
Package structure
The parsley package contains the
Parsleyclass, as well as theResult,Success, andFailuretypes. In addition to these, it also contains the following packages and "modules" (a module is defined as being an object which mocks a package):parsley.Parsleycontains the bulk of the core "function-style" combinators.parsley.combinatorcontains many helpful combinators that simplify some common parser patterns.parsley.charactercontains the combinators needed to read characters and strings, as well as combinators to match specific sub-sets of characters.parsley.debugcontains debugging combinators, helpful for identifying faults in parsers.parsley.extensioncontains syntactic sugar combinators exposed as implicit classes.parsley.iocontains extension methods to run parsers with input sourced from IO sources.parsley.exprcontains the following sub modules:parsley.expr.chaincontains combinators used in expression parsingparsley.expr.precedenceis a builder for expression parsers built on a precedence table.parsley.expr.infixcontains combinators used in expression parsing, but with more permissive types than their equivalents inchain.parsley.expr.mixedcontains combinators that can be used for expression parsing, but where different fixities may be mixed on the same level: this is rare in practice.parsley.implicitscontains several implicits to add syntactic sugar to the combinators. These are sub-categorised into the following sub modules:parsley.implicits.charactercontains implicits to allow you to use character and string literals as parsers.parsley.implicits.combinatorcontains implicits related to combinators, such as the ability to make any parser into aParsley[Unit]automatically.parsley.implicits.liftenables postfix application of the lift combinator onto a function (or value).parsley.implicits.zippedenables boths a reversed form of lift where the function appears on the right and is applied on a tuple (useful when type inference has failed) as well as a.zippedmethod for building tuples out of several combinators.parsley.errorscontains modules to deal with error messages, their refinement and generation.parsley.errors.combinatorprovides combinators that can be used to either produce more detailed errors as well as refine existing errors.parsley.errors.tokenextractorsprovides mixins for common token extraction strategies during error message generation: these can be used to avoid implementingunexpectedTokenin theErrorBuilder.parsley.liftcontains functions which lift functions that work on regular types to those which now combine the results of parsers returning those same types. these are ubiquitous.parsley.apcontains functions which allow for the application of a parser returning a function to several parsers returning each of the argument types.parsley.registerscontains combinators that interact with the context-sensitive functionality in the form of registers.parsley.tokencontains theLexerclass that provides a host of helpful lexing combinators when provided with the description of a language.parsley.positioncontains parsers for extracting position information.parsley.genericbridgescontains some basic implementations of the Parser Bridge pattern (see Design Patterns for Parser Combinators in Scala, or the parsley wiki): these can be used before more specialised generic bridge traits can be constructed.