Text.Parsec.Prim (original) (raw)
Documentation
unexpected :: Stream s m t => String -> ParsecT s u m aSource
The parser unexpected msg
always fails with an unexpected error message msg
without consuming any input.
The parsers [fail](/packages/archive/base/4.5.0.0/doc/html/Control-Monad.html#v:fail)
, ([<?>](Text-Parsec-Prim.html#v:-60--63--62-)
) and unexpected
are the three parsers used to generate error messages. Of these, only ([<?>](Text-Parsec-Prim.html#v:-60--63--62-)
) is commonly used. For an example of the use of unexpected
, see the definition of [notFollowedBy](Text-Parsec-Combinator.html#v:notFollowedBy)
.
data ParsecT s u m a Source
ParserT monad transformer and Parser type
ParsecT s u m a
is a parser with stream type s
, user state type u
, underlying monad m
and return type a
. Parsec is strict in the user state. If this is undesirable, simply used a data type like data Box a = Box a
and the state type Box YourStateType
to add a level of indirection.
(<?>) :: ParsecT s u m a -> String -> ParsecT s u m aSource
The parser p <?> msg
behaves as parser p
, but whenever the parser p
fails without consuming any input, it replaces expect error messages with the expect error message msg
.
This is normally used at the end of a set alternatives where we want to return an error message in terms of a higher level construct rather than returning all possible characters. For example, if theexpr
parser from the [try](Text-Parsec-Prim.html#v:try)
example would fail, the error message is: '...: expecting expression'. Without the (<?>)
combinator, the message would be like '...: expecting "let" or letter', which is less friendly.
(<|>) :: ParsecT s u m a -> ParsecT s u m a -> ParsecT s u m aSource
This combinator implements choice. The parser p <|> q
first applies p
. If it succeeds, the value of p
is returned. If p
fails without consuming any input, parser q
is tried. This combinator is defined equal to the [mplus](/packages/archive/base/4.5.0.0/doc/html/Control-Monad.html#v:mplus)
member of the [MonadPlus](/packages/archive/base/4.5.0.0/doc/html/Control-Monad.html#t:MonadPlus)
class and the ([<|>](/packages/archive/base/4.5.0.0/doc/html/Control-Applicative.html#v:-60--124--62-)
) member of [Alternative](/packages/archive/base/4.5.0.0/doc/html/Control-Applicative.html#t:Alternative)
.
The parser is called predictive since q
is only tried when parser p
didn't consume any input (i.e.. the look ahead is 1). This non-backtracking behaviour allows for both an efficient implementation of the parser combinators and the generation of good error messages.
lookAhead :: Stream s m t => ParsecT s u m a -> ParsecT s u m aSource
lookAhead p
parses p
without consuming any input.
If p
fails and consumes some input, so does lookAhead
. Combine with [try](Text-Parsec-Prim.html#v:try)
if this is undesirable.
class Monad m => Stream s m t | s -> t whereSource
An instance of Stream
has stream type s
, underlying monad m
and token type t
determined by the stream
Some rough guidelines for a "correct" instance of Stream:
- unfoldM uncons gives the [t] corresponding to the stream
- A
Stream
instance is responsible for maintaining the "position within the stream" in the stream states
. This is trivial unless you are using the monad in a non-trivial way.
try :: ParsecT s u m a -> ParsecT s u m aSource
The parser try p
behaves like parser p
, except that it pretends that it hasn't consumed any input when an error occurs.
This combinator is used whenever arbitrary look ahead is needed. Since it pretends that it hasn't consumed any input when p
fails, the ([<|>](Text-Parsec-Prim.html#v:-60--124--62-)
) combinator will try its second alternative even when the first parser failed while consuming input.
The try
combinator can for example be used to distinguish identifiers and reserved words. Both reserved words and identifiers are a sequence of letters. Whenever we expect a certain reserved word where we can also expect an identifier we have to use the try
combinator. Suppose we write:
expr = letExpr <|> identifier <?> "expression"
letExpr = do{ string "let"; ... } identifier = many1 letter
If the user writes "lexical", the parser fails with: unexpected 'x', expecting 't' in "let"
. Indeed, since the ([<|>](Text-Parsec-Prim.html#v:-60--124--62-)
) combinator only tries alternatives when the first alternative hasn't consumed input, the identifier
parser is never tried (because the prefix "le" of the string "let"
parser is already consumed). The right behaviour can be obtained by adding the try
combinator:
expr = letExpr <|> identifier <?> "expression"
letExpr = do{ try (string "let"); ... } identifier = many1 letter
tokenSource
The parser token showTok posFromTok testTok
accepts a token t
with result x
when the function testTok t
returns `[Just](/packages/archive/base/4.5.0.0/doc/html/Data-Maybe.html#v:Just)` x
. The source position of the t
should be returned by posFromTok t
and the token can be shown using showTok t
.
This combinator is expressed in terms of [tokenPrim](Text-Parsec-Prim.html#v:tokenPrim)
. It is used to accept user defined token streams. For example, suppose that we have a stream of basic tokens tupled with source positions. We can than define a parser that accepts single tokens as:
mytoken x = token showTok posFromTok testTok where showTok (pos,t) = show t posFromTok (pos,t) = pos testTok (pos,t) = if x == t then Just t else Nothing
tokenPrimSource
Arguments
:: Stream s m t | |
---|---|
=> (t -> String) | Token pretty-printing function. |
-> (SourcePos -> t -> s -> SourcePos) | Next position calculating function. |
-> (t -> Maybe a) | Matching function for the token to parse. |
-> ParsecT s u m a |
The parser tokenPrim showTok nextPos testTok
accepts a token t
with result x
when the function testTok t
returns `[Just](/packages/archive/base/4.5.0.0/doc/html/Data-Maybe.html#v:Just)` x
. The token can be shown using showTok t
. The position of the next token should be returned when nextPos
is called with the current source position pos
, the current token t
and the rest of the tokens toks
, nextPos pos t toks
.
This is the most primitive combinator for accepting tokens. For example, the [char](Text-Parsec-Char.html#v:char)
parser could be implemented as:
char c = tokenPrim showChar nextPos testChar where showChar x = "'" ++ x ++ "'" testChar x = if x == c then Just x else Nothing nextPos pos x xs = updatePosChar pos x
many :: ParsecT s u m a -> ParsecT s u m [a]Source
many p
applies the parser p
zero or more times. Returns a list of the returned values of p
.
identifier = do{ c <- letter ; cs <- many (alphaNum <|> char '_') ; return (c:cs) }
runParserT :: Stream s m t => ParsecT s u m a -> u -> SourceName -> s -> m (Either ParseError a)Source
The most general way to run a parser. runParserT p state filePath input
runs parser p
on the input list of tokens input
, obtained from source filePath
with the initial user state st
. The filePath
is only used in error messages and may be the empty string. Returns a computation in the underlying monad m
that return either a [ParseError](Text-Parsec-Error.html#t:ParseError)
([Left](/packages/archive/base/4.5.0.0/doc/html/Data-Either.html#v:Left)
) or a value of type a
([Right](/packages/archive/base/4.5.0.0/doc/html/Data-Either.html#v:Right)
).
runParser :: Stream s Identity t => Parsec s u a -> u -> SourceName -> s -> Either ParseError aSource
The most general way to run a parser over the Identity monad. runParser p state filePath input
runs parser p
on the input list of tokens input
, obtained from source filePath
with the initial user state st
. The filePath
is only used in error messages and may be the empty string. Returns either a [ParseError](Text-Parsec-Error.html#t:ParseError)
([Left](/packages/archive/base/4.5.0.0/doc/html/Data-Either.html#v:Left)
) or a value of type a
([Right](/packages/archive/base/4.5.0.0/doc/html/Data-Either.html#v:Right)
).
parseFromFile p fname = do{ input <- readFile fname ; return (runParser p () fname input) }
parse :: Stream s Identity t => Parsec s () a -> SourceName -> s -> Either ParseError aSource
parse p filePath input
runs a parser p
over Identity without user state. The filePath
is only used in error messages and may be the empty string. Returns either a [ParseError](Text-Parsec-Error.html#t:ParseError)
([Left](/packages/archive/base/4.5.0.0/doc/html/Data-Either.html#v:Left)
) or a value of type a
([Right](/packages/archive/base/4.5.0.0/doc/html/Data-Either.html#v:Right)
).
main = case (parse numbers "" "11, 2, 43") of Left err -> print err Right xs -> print (sum xs)
numbers = commaSep integer
setInput :: Monad m => s -> ParsecT s u m ()Source
setInput input
continues parsing with input
. The [getInput](Text-Parsec-Prim.html#v:getInput)
andsetInput
functions can for example be used to deal with #include files.
modifyState :: Monad m => (u -> u) -> ParsecT s u m ()Source
updateState f
applies function f
to the user state. Suppose that we want to count identifiers in a source, we could use the user state as:
expr = do{ x <- identifier ; updateState (+1) ; return (Id x) }