Text.ParserCombinators.UU.Core

The module Core contains the basic functionality of the parser library. It defines the types and implementations of the elementary parsers and recognisers involved.

Classes

class (Alternative p, Applicative p, ExtAlternative p) => IsParser p

In the class IsParser we assemble the basic properties we expect parsers to have. The class itself does not have any methods. Most properties come directly from the standard Control.Applicative module. The class ExtAlternative contains some extra methods we expect our parsers to have.

Instances

IsParser (P st)

Functor f => IsParser (Gram f)

class Alternative p => ExtAlternative p where

Methods

(<<|>) :: p a -> p a -> p a

<<|> is the greedy version of <|>. If its left hand side parser can make any progress then it commits to that alternative. Can be used to make parsers faster, and even get a complete Parsec equivalent behaviour, with all its (dis)advantages. Intended use p <<|> q <<|> r <|> x <|> y <?> "string". Use with care!

(<?>) :: p a -> String -> p a

The parsers build a list of symbols which are expected at a specific point. This list is used to report errors. Quite often it is more informative to get e.g. the name of the non-terminal . The <?> combinator replaces this list of symbols by the string argument.

doNotInterpret :: p a -> p a

doNotInterpret makes a parser opaque for abstract interpretation; used when permuting parsers where we do not want to compare lengths.

must_be_non_empty :: String -> p a -> c -> c

must_be_non_empty checks whether its second argument is a parser which can recognise the empty input. If so, an error message is given using the String parameter. If not, then the third argument is returned. This is useful in testing for illogical combinations. For its use see the module Text.ParserCombinators.UU.Derived.

must_be_non_empties :: String -> p a -> p b -> c -> c

must_be_non_empties is similar to must_be_non_empty, but can be used in situations where we recognise a sequence of elements separated by other elements. This does not make sense if both parsers can recognise the empty string. Your grammar is then highly ambiguous.

opt :: p a -> a -> p a

If p can be recognized, the return value of p is used. Otherwise, the value v is used. Note that opt by default is greedy. If you do not want this use ...<|> pure v instead. Furthermore, p should not recognise the empty string, since this would make the parser ambiguous!!

Instances

ExtAlternative (P st)

Functor f => ExtAlternative (Gram f)

class Eof state where

The class Eof contains a function eof which is used to check whether we have reached the end of the input and deletAtEnd should discard any unconsumed input at the end of a successful parse.

Methods

eof :: state -> Bool

deleteAtEnd :: state -> Maybe (Cost, state)

Instances

(Show a, ListLike s a) => Eof (Str a s loc)

class Show loc => IsLocationUpdatedBy loc str where

The input state may maintain a location which can be used in generating error messages. Since we do not want to fix our input to be just a String we provide an interface which can be used to advance this location by passing information about the part recognised. This function is typically called in the splitState functions.

Methods

advance

Arguments

:: loc

The current position

-> str

The part which has been removed from the input

-> loc

Instances

IsLocationUpdatedBy Int Char

IsLocationUpdatedBy Int Word8

IsLocationUpdatedBy LineColPos Char

IsLocationUpdatedBy LineCol Char

IsLocationUpdatedBy loc a => IsLocationUpdatedBy loc [a]

class StoresErrors state error | state -> error where

The class StoresErrors is used by the function pErrors which retrieves the generated correction steps since the last time it was called.

Methods

getErrors :: state -> ([error], state)

getErrors retrieves the correcting steps made since the last time the function was called. The result can, by using it in a monad, be used to control how to proceed with the parsing process.

Instances

StoresErrors (Str a s loc) (Error loc)

class HasPosition state pos | state -> pos where

Methods

getPos :: state -> pos

getPos retrieves the correcting steps made since the last time the function was called. The result can, by using it as the left hand side of a monadic bind, be used to control how to proceed with the parsing process.

Instances

HasPosition (Str a s loc) loc

Types

The parser descriptor

data P st a

Instances

Idiomatic st x (Ii -> P st x)

Idiomatic st f g => Idiomatic st (a -> f) (IF -> Bool -> THEN -> P st a -> ELSE -> P st a -> FI -> g)

Idiomatic st f g => Idiomatic st (a -> f) (P st a -> g)

Monad (P st)

Functor (P state)

MonadPlus (P st)

Applicative (P state)

Alternative (P state)

ExtAlternative (P st)

IsParser (P st)

Show (P st a)

The progress information

data Steps a where

The data type Steps is the core data type around which the parsers are constructed. It describes a tree structure of streams containing (in an interleaved way) both the online result of the parsing process, and progress information. Recognising an input token should correspond to a certain amount of Progress, which tells how much of the input state was consumed. The Progress is used to implement the breadth-first search process, in which alternatives are examined in a more-or-less synchronised way. The meaning of the various Step constructors is as follows:

Step

A token was succesfully recognised, and as a result the input was advanced by the distance Progress

Apply

The type of value represented by the Steps changes by applying the function parameter.

Fail

A correcting step has to be made to the input; the first parameter contains information about what was expected in the input, and the second parameter describes the various corrected alternatives, each with an associated Cost

Micro

A small cost is inserted in the sequence, which is used to disambiguate. Use with care!

The last two alternatives play a role in recognising ambigous non-terminals. For a full description see the technical report referred to from Text.ParserCombinators.UU.README.

Constructors

Step :: Progress -> Steps a -> Steps a

Apply :: forall a b. (b -> a) -> Steps b -> Steps a

Fail :: Strings -> [Strings -> (Cost, Steps a)] -> Steps a

Micro :: Int -> Steps a -> Steps a

End_h :: ([a], [a] -> Steps r) -> Steps (a, r) -> Steps (a, r)

End_f :: [Steps a] -> Steps a -> Steps a

type Cost = Int

type Progress = Int

Auxiliary types

data Nat

The data type Nat is used to represent the minimal length of a parser. Care should be taken in order to not evaluate the right hand side of the binary function `nat-add` more than necesssary.

Constructors

Zero Nat

Succ Nat

Infinite

Unspecified

Instances

Show Nat

type Strings = [String]

Functions

Basic Parsers

micro :: P state a -> Int -> P state a

micro inserts a Cost step into the sequence representing the progress the parser is making; for its use see `Text.ParserCombinators.UU.Demos.Examples`

amb :: P st a -> P st [a]

For the precise functioning of the amb combinators see the paper cited in the Text.ParserCombinators.UU.README; it converts an ambiguous parser into a parser which returns a list of possible recognitions,

pErrors :: StoresErrors st error => P st [error]

pErrors returns the error messages that were generated since its last call.

pPos :: HasPosition st pos => P st pos

pPos returns the current input position.

pEnd :: (StoresErrors st error, Eof st) => P st [error]

The function pEnd should be called at the end of the parsing process. It deletes any unconsumed input, turning it into error messages.

pSwitch :: (st1 -> (st2, st2 -> st1)) -> P st2 a -> P st1 a

pSwitch takes the current state and modifies it to a different type of state to which its argument parser is applied. The second component of the result is a function which converts the remaining state of this parser back into a value of the original type. For the second argument to pSwitch (say split) we expect the following to hold:

  let (n,f) = split st in f n == st

pSymExt :: (forall a. (token -> state -> Steps a) -> state -> Steps a) -> Nat -> Maybe token -> P state token

The basic recognisers are written elsewhere (e.g. in our module Text.ParserCombinataors.UU.BasicInstances; they (i.e. the parameter splitState) are lifted to ourP descriptors by the function pSymExt which also takes the minimal number of tokens recognised by the parameter spliState and an Maybe value describing the possibly empty value.

Calling Parsers

parse :: Eof t => P t a -> t -> a

The function parse shows the prototypical way of running a parser on some specific input. By default we use the future parser, since this gives us access to partal result; future parsers are expected to run in less space.

parse_h :: Eof t => P t a -> t -> a

The function parse_h behaves like parse but using the history parser. This parser does not give online results, but might run faster.

Acessing various components

getZeroP :: P t a -> Maybe a

getZeroP retrieves the possibly empty part from a descriptor.

getOneP :: P a b -> Maybe (P a b)

getOneP retrieves the non-zero part from a descriptor.

Evaluating the online result

eval :: Steps a -> a

eval removes the progress information from a sequence of steps, and constructs the value embedded in it. If you are really desparate to see how your parsers are making progress (e.g. when you have written an ambiguous parser, and you cannot find the cause of the exponential blow-up of your parsing process), you may switch on the trace in the function eval (you will need to edit the library source code).

Re-exported modules

module Control.Applicative

module Control.Monad