> And note that no compiler/interpreter currently rejects a string
> containing a literal tab character.
My working version of GHC does :-)
Simon
___
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-h
> 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
> > 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
On Tue, Oct 23, 2001 at 03:24:56PM -0400, Sengan wrote:
> > module Test where
>
> > chars = "
> > foo
> > bar"
Try this instead:
> module Test where
> chars = "\n\
> \foo\n\
> \bar"
Ian
___
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http
