Re: Character escape codes in Parsec

On Sun, 30 Mar 2008, Tim Chevalier wrote:

On 3/30/08, Philippa Cowderoy wrote:

...

My guess is it's not particularly "supposed" to be doing much, but it munches Char and so Unicode input is a distinct possibility. I'd also guess that after the \ it just reuses the existing hex literal function which definitely does need to handle arbitrary length .

Well, yes, but I'd like to know what the spec is. If there is one, anyway!

Having just poked at the manual (http://legacy.cs.uu.nl/daan/download/parsec/parsec.html if you've not found it already), the spec for anything not specifiable in a LanguageDef is "per the Haskell lexing rules". It implements that correctly. -- flippa@flippac.org The task of the academic is not to scale great intellectual mountains, but to flatten them.