I try to do this:
Parse a Text in the form:
Some Text #{0,0,0} some Text #{0,0,0}#{0,0,0} more Text #{0,0,0}
into a list of some data structure:
[Inside “Some Text “,Outside (0,0,0),Inside ” some Text “,Outside (0,0,0),Outside (0,0,0),Inside ” more Text “,Outside (0,0,0)]
So these #{a,b,c}-bits should turn into different things as the rest of the text.
I have this code:
module ParsecTest where
import Text.ParserCombinators.Parsec
import Monad
type Reference = (Int, Int, Int)
data Transc = Inside String | Outside Reference
deriving (Show)
text :: Parser Transc
text = do
x <- manyTill anyChar ((lookAhead reference) <|> (eof >> return (Inside "")));
return (Inside x)
transc = reference <|> text
alot :: Parser [Transc]
alot = do
manyTill transc eof
reference :: Parser Transc
reference = try (do{ char '#';
char '{';
a <- number;
char ',';
b <- number;
char ',';
c <- number;
char '}';
return (Outside (a,b,c)) })
number :: Parser Int
number = do{ x <- many1 digit;
return (read x) }
This works as expected. You can test this in ghci by typing
parseTest alot “Some Text #{0,0,0} some Text #{0,0,0}#{0,0,0} more Text #{0,0,0}”
But I think it’s not nice.
1) Is the use of lookAhead really necessary for my problem?
2) Is the return (Inside "") an ugly hack?
3) Is there generally a more concise/smarter way to archieve the same?
1) I think you do need
lookAheadas you need the result of that parse. It would be nice to avoid running that parser twice by having aParser (Transc,Maybe Transc)to indicate anInsidewith an optional followingOutside. If performance is an issue, then this is worth doing.2) Yes.
3)
ApplicativesYou may want to rewrite the beginning of
reference2using a helper likeaux x y z = Outside (x,y,z).EDIT: Changed
textto deal with inputs that don’t end with anOutside.