> On the contrary I'm glad to see that the Haskell standard is so sensible.
> I edit Haskell using XEmacs, and I don't want to have to do an octal
> or hexadecimal dump of my source code to determine whether a string
> contains a tab, newline, return, line feed, Unicode en-space (there are
> sev
Malcolm Wallace wrote:
[snip]
> No he isn't. At least, I can't find anything in the Report which
> disallows literal newline characters in a string literal.
> Oh, hold on. The production
>
> string -> " { graphic_<"|`> | space | escape | gap } "
>
> does seem to disallow newline characte
> > chars = "
> > foo
> > bar"
> You *are* violating the Haskell 98 spec, I'm afraid :)
No he isn't. At least, I can't find anything in the Report which
disallows literal newline characters in a string literal.
Oh, hold on. The production
string -> " { graphic_<"|`> | space | escape | ga
> I've attached a diff of the changes I've made so far - they
> are changes
> to make it work rather than the correct way to fix it, though.
Thanks. I've fixed the 'ld -x' problem. You also appear to need an
extra -L path to find the readline library - we don't have proper
provision for this a
> > module Test where
>
> > chars = "
> > foo
> > bar"
>
> > this line is in error and it is line 7
>
> ghc test.lhs
> test.lhs:5: parse error on input `in'
>
> It turns out that in the script I am writing
> (semi-automatic generation of a grammar file)
> being able to use the above notation
