RE: ghc 6.2 possible bug with gcc 3.3.x, strange parse error

> Sorry to trouble you with an already known bug.
> 
> Don's mail has answered my question.
> 
> In case you are curious, here is a link to a previous
> mention of the bug/problem:
> 
>    
> http://www.mail-archive.com/glasgow-haskell-bugs@xxxxxxxxxxx/m
sg05854.html 

Incedentally, GCC 3.4 will make this situation even worse.  They have
now taken the approach that a backslash followed by whitespace at the
end of the line should be interpreted as a line continuation (and a
warning is emitted).  So the hack from the Users' Guide for string gaps
will no longer work with GCC 3.4.  

I can't see a workaround, so it might be that string gaps will not be
useable with CPP from now on.

Cheers,
        Simon