Argh ... gmail totally mangled that patch. (The line that starts
with "loadObj(image)" needs to be part of the previous line).
I've put an unmangled version online at
http://cass166.ucsd.edu/~david/link-patch
___
Glasgow-haskell-users mailing list
Glas
On 1/15/07, David Kirkman <[EMAIL PROTECTED]> wrote:
The comment above seems to be begging for a
oc->image += oc->misalignment;
statement right after the call to stgMallocBytes.
This did in fact work (patch for rts/Linker.c below). And it *was* in
the 6.6 sources, so it was removed in
Visual Haskell is sensitive to the file name <-> module name mapping.
For the case of Main there could be only one module with this name for
a given package and I usually name it Main.hs. For the case of Main
there could be a special handling in Visual Haskell because the Cabal
description keeps i
Am Dienstag, 16. Januar 2007 12:12 schrieb Yitzchak Gale:
> I have observed the following weird behavior:
>
> When I define an instance of a certain MPTC
> in a separate module from the definition of
> the class, ghci's ability to recognize the
> methods of the class seems to vary depending
> on wh
Bernd Holzmüller wrote:
> I would like to match word boundaries in a regular expression but this
> doesn't seem to work with Text.Regex in GHC 6.4.2.
>
> The regular expression looks something like: "\\b(send|receive)\\b" to
> match either the keyword send or the keyword receive but not the word
>
I have observed the following weird behavior:
When I define an instance of a certain MPTC
in a separate module from the definition of
the class, ghci's ability to recognize the
methods of the class seems to vary depending
on whether or not hi files exist for the modules.
I am using the current D
I would like to match word boundaries in a regular expression but this
doesn't seem to work with Text.Regex in GHC 6.4.2.
The regular expression looks something like: "\\b(send|receive)\\b" to
match either the keyword send or the keyword receive but not the word
sending. Neither works \< and \> f
