> Section 2.6. of the Haskell report says:
>
> A string may include a "gap"---two backslants enclosing white
> characters---which is ignored. This allows one to write long
> strings on
> more than one line by writing a backslant at the end of one
> line and at
> the start of the next. For examp
Hi,
if you've run into problems installing haskell.org/ghc Windows
Installers (.msi files) that you've downloaded with
Netscape Navigator in the past couple of weeks, this is
to let you know that the (new) web server setup has now been
fixed, so downloading with Netscape should again work OK.
Th
Hello *,
Section 2.6. of the Haskell report says:
A string may include a "gap"---two backslants enclosing white
characters---which is ignored. This allows one to write long strings on
more than one line by writing a backslant at the end of one line and at
the start of the next. For example,
"He
> The need to recompile everything after upgrading was recently
> mentioned, I think, on this list. After upgrading from .1 to .2
> (trying to get profiling on track), ghci gave me a slightly cryptic
> message about an unknow symbol ("stg_gc_enter_1"). No big deal, and
> after I removed the .o's
The need to recompile everything after upgrading was recently
mentioned, I think, on this list. After upgrading from .1 to .2
(trying to get profiling on track), ghci gave me a slightly cryptic
message about an unknow symbol ("stg_gc_enter_1"). No big deal, and
after I removed the .o's, everyth
