Hmm.. I'll take a look at it. I recently fixed a bug relating to the
typing of Absurd, it could be related.
When jhc does something odd, it is a good idea to run it with -flint,
it won't fix the problem but it may give more information that will
help in tracking it down.
John
On Thu, Feb 10, 2011 at 4:21 PM, Dr. ERDI Gergo
On Tue, 8 Feb 2011, Dr. ERDI Gergo wrote:
I'm trying to use jhc with Parsec. However, while reimplementing some Parsec.Token functionality, I've encountered a strange error message. I've created a hopefully minimal example (see attached).
I've managed to create an even simpler program exhibiting a similar problem:
main = getLine >>= (print . parse (eof) "")
jhc's output:
jhc -flint -fffi -fjgc parsec-error.hs -o parsec.jhc -p parsec jhc 0.7.7 (0.7.6-53) Finding Dependencies... Using Ho Cache: '/home/cactus/.jhc/cache' Main [parsec-error.hs] Typechecking... [1 of 1] Main (.............................................) Compiling... [1 of 1] Main <..................................................> Collected Compilation... -- typeAnalyzeMethods jhc: Types don't match:(Char, Jhc@.Absurd.*)
--
.--= ULLA! =-----------------. \ http://gergo.erdi.hu \ `---= gergo@erdi.hu =-------' Men are stupid, women are crazy.
_______________________________________________ jhc mailing list jhc@haskell.org http://www.haskell.org/mailman/listinfo/jhc