Custom whiteSpace using Haskell Parsec?

Sadly, I don't think there is a way. The local definitions used in makeTokenParser refer recursively to themselves, and so, as you've noted lexeme uses whiteSpace as defined there, rather than the whiteSpace record member you replace in your lexer object The code is taunting because is uses the same names as both local functions in makeTokenParser and as record members of the TokenParser constructor. They are in fact totally distinct entities.

Sadly, I don't think there is a way. The local definitions used in makeTokenParser refer recursively to themselves, and so, as you've noted, lexeme uses whiteSpace as defined there, rather than the whiteSpace record member you replace in your lexer object. The code is taunting because is uses the same names as both local functions in makeTokenParser and as record members of the TokenParser constructor.

They are in fact totally distinct entities.

1 Now if only the TokenParser were written with type classes, we'd be good to go. – Steve Apr 15 '10 at 7:36 .. and if it could make monadic parsers (in Parsec 3) rather than be hardwired up to Identity. – Edward Kmett Apr 20 '10 at 19:30.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.