StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POParsec-Parser works alright, but could it be done better?
primarykey
Id
7852484
data
AcceptedAnswerId
7853464
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-10-21T16:34:31.817
FavoriteCount
0
LastActivityDate
2011-10-24T02:09:08.980
LastEditDate
2011-10-24T02:09:08.980
LastEditorUserId
61289
OwnerUserId
546402
ParentId
0
PostTypeId
1
Score
4
ViewCount
288
LastEditorDisplayName
text
Body
I try to do this: Parse a Text in the form: <blockquote> Some Text #{0,0,0} some Text #{0,0,0}#{0,0,0} more Text #{0,0,0} </blockquote> into a list of some data structure: <blockquote> [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)] </blockquote> So these #{a,b,c}-bits should turn into different things as the rest of the text. I have this code: <pre><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) } </code></pre> This works as expected. You can test this in ghci by typing <blockquote> parseTest alot "Some Text #{0,0,0} some Text #{0,0,0}#{0,0,0} more Text #{0,0,0}" </blockquote> But I think it's not nice. 1) Is the use of <code>lookAhead</code> really necessary for my problem? 2) Is the <code>return (Inside "")</code> an ugly hack? 3) Is there generally a more concise/smarter way to archieve the same? 
Tags
<parsing><haskell><parsec>
Title
Parsec-Parser works alright, but could it be done better?
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USLogan Capaldo
UserOwnerUserId
1. USSecoe
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POParsec-Parser works alright, but could it be done better?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POParsec-Parser works alright, but could it be done better?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POParsec-Parser works alright, but could it be done better?
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.