Sure. Learning Parsec took me a few hours, whereas John's parsing task might be done in much less time, if it's simple enough. OTOH, there's value in being able to use Parsec, so it's a good excuse to learn.
> -----Original Message----- > From: Graham Klyne [mailto:[EMAIL PROTECTED] > Sent: 30 September 2004 10:34 > To: Bayley, Alistair; 'John Goerzen'; [EMAIL PROTECTED] > Subject: Simple example using Parsec (was: [Haskell-cafe] > Rethinking OO idioms) > > At 09:01 30/09/04 +0100, Bayley, Alistair wrote: > >Ben suggested using Parsec for reading the config file. > Parsec is a fine > >library, but there is a learning curve, and you might find > it quicker to do > >the parsing yourself, if it's very simple. Your call. > > Hmmm... Parsec *can* be simple too. Here's one I did earlier: > http://www.ninebynine.org/Software/HaskellUtils/RegexParser.hs > > #g ----------------------------------------- ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. ***************************************************************** _______________________________________________ Haskell-Cafe mailing list [EMAIL PROTECTED] http://www.haskell.org/mailman/listinfo/haskell-cafe
