"Simon Marlow" <[EMAIL PROTECTED]> writes:
> 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.
Might the cpp -traditional flag mitigate this? Will it also use the
newer lexing rule?
I noticed today that new versions of gcc's cpp (already?) lex the input
into tokens based on the C syntax, and do not guarantee to preserve
horizontal whitespace. We already know that Haskell identifiers
with a single prime fall foul of the C lexing rules unless you use
-traditional, but are we also in danger of losing indentation layout
through cpp?
Regards,
Malcolm
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
