On Tue, Aug 10, 2010 at 10:25 AM, John Meacham
are you passing '-p parsec' on the command line? it is the equivalent of ghc's -package flag more or less.
My bad, I didn't know I had to do that. I apologise for wasting your time, as indeed the User manual makes it clear. I could have saved myself quite some time, had I read it. So it compiles and works with the command line.
This is actually the 3rd or 4th time someone has had this issue, clearly I need to improve the documentation or something. What I was
I don't think you have. It's my fault entirely. Being used to ghc, I didn't expect to have to specify anything on the command line. Other imports worked fine too : Data.List, Data.Maybe, Control.Monad, etc.
thinking of was to have it look for unrecognized modules in available packages and provide a better error message, something like:
That'd be cool, but I'm sure there's many things higher on the priority list. Fools like me just have to read the (adequate) existing documentation.
I don't want to do the stateful thing ghc does with package registration and exposed/hidden packages and whatnot, it always felt fairly hacky. In jhc you get what you specify on the command line and thats it. (though, you can always create custom profiles in your targets.ini file)
But the drawback is every time you add an import from a new library, you have to also change your compile script. Not a big deal though. David. P.S. The cool thing is that the stripped executable is 79588 bytes with jhc vs 608036 with ghc !