Character escape codes in Parsec

[Tim Chevalier]

On 3/30/08, Philippa Cowderoy <flippa at flippac.org> 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!

>  My approach is simple: when in doubt, write your own lexing functions - at
>  least that way any nasty surprises are your own fault!
>

I'll do so if it comes to that, but if it's truly a bug, I'd prefer it
to be fixed so that everyone can enjoy the results (even if it's me
who ends up fixing it :-)

Cheers,
Tim

-- 
Tim Chevalier * http://cs.pdx.edu/~tjc * Often in error, never in doubt
"Accordingly, computer scientists commonly choose models which have
bottoms, but prefer them topless." -- Davey & Priestley, _Introduction
to Lattices and Order_