September 2009 - jhc - Haskell.org

jhc-0.7.1 and parsec-2.1.0.1
by Christian Maeder 19 Nov '09

19 Nov '09

Hi, I've tried to compile (part of) parsec-2.1.0.1 with jhc-0.7.1 and Parsec.Combinator had several problems with do-expression as infix arguments, which should be simple to fix for you. I.e. do{ p; return ()} <|> return () needed explicit parenthesis: (do{ p; return ()}) <|> return () (also if layout is used instead of curly braces) Cheers Christian name: parsec version: 2.1.0.1 exposed-modules: Text.ParserCombinators.Parsec.Error, Text.ParserCombinators.Parsec.Char, Text.ParserCombinators.Parsec.Combinator, Text.ParserCombinators.Parsec.Pos, Text.ParserCombinators.Parsec.Prim, Text.ParserCombinators.Parsec

3 7

darcs patch: use appropriate mingw gcc in targets.ini
by David Roundy 23 Sep '09

23 Sep '09

This works on debian, at least. We'd need to all the likely names for mingw gcc to get better coverage... but I suspect this already covers the big three of debian, ubuntu and fedora. David Wed Sep 23 07:35:32 EDT 2009 David Roundy <roundyd(a)physics.oregonstate.edu> * use appropriate mingw gcc in targets.ini

2 1

darcs patch: add System.IO.Pipe.
by David Roundy 23 Sep '09

23 Sep '09

Hi John, This patch adds support for popen/pclose. It's a bit hokey, and doesn't quite work right. In particular, I get an error if I try to use getErrno in openPipe. gcc complains about errno not being defined, because errno.h isn't included. For the moment, openPipe just doesn't check for errors, but that isn't a great long-term solution. So far as I can discern, this is portable code, at least to mingw, which is as far into windows as I care to venture. David P.S. I'd much rather have System.Process ported, but gave up on doing this myself after realizing that I'd have to implement much of GHC.Handle in order to do this, since we'd have to work with file descriptors rather than FILE *. :( Sun Sep 20 18:20:21 EDT 2009 David Roundy <roundyd(a)physics.oregonstate.edu> * add System.IO.Pipe.

4 6

including C source files?
by David Roundy 23 Sep '09

23 Sep '09

Hi all, I was wondering what we are supposed to do to include C source files, accessed via the FFI? Including them on the command line (as I was tempted to do) just results in a complaint that they aren't haskell. Do I need to compile it separately with gcc and then pass the object file on the command line? I guess I could just experiment, but I'm feeling lazy, so I'm asking instead... This is with regard to getting jhc support to support the franchise test suite. It's a little embarassing that it fails the ffi portion. :( David

4 6

JHC Archlinux AUR Package
by Mathew de Detrich 22 Sep '09

22 Sep '09

For anyone using Archlinux, there is now an AUR package for JHC http://aur.archlinux.org/packages.php?ID=30332

2 2

How to add Num instance to Foreign.C.Types.CLong?
by David Roundy 20 Sep '09

20 Sep '09

Hello, I'm wondering how one would go about adding a Num instance to CLong? So far as I can see in lib/jhc/Foreign/C/Types.hs it's a completely opaque data type, so I've no idea how to go about adding instances. Of course, most of these type would benefit from being members of a whole slew of classes, but I can't see how to go about doing this. Any hints? -- David Roundy

2 1

darcs patch: allow selecting libraries by hash or name-version
by John Meacham 16 Sep '09

16 Sep '09

Wed Sep 16 02:20:17 PDT 2009 John Meacham <john(a)repetae.net> * allow selecting libraries by hash or name-version

1 0

bug in handling of -p flag
by David Roundy 14 Sep '09

14 Sep '09

Hi John, It looks like the handling of the -p flag is buggy, or at least counterintuitive. I've started playing with your new --list-libraries output, and I can now figure out which packages export which modules, which is great. What's not so great is that there doesn't seem to be a way to uniquely specify the package that I want to import. It seems that only the BaseName is supported with -p, so I can't use either the Name, or the FilePath, or the hash of the library I want. It's not a huge deal, since usually one wants the first version of the library in the path, but it'd be much nicer to allow us to specify any of those four specifiers, BaseName, Name, FilePath *or* hash. I'm not sure what I'd want franchise to do. Either FilePath or hash is unique, and FilePath is much friendlier to read. But neither is as user-friendly as Name. -- David Roundy

2 1

Another bug
by David Roundy 13 Sep '09

13 Sep '09

Here's another bug, Compiling the attached file, I get $ jhc test.hs jhc test.hs jhc 0.7.3 (0.7.2-30) Finding Dependencies... Using Ho Cache: '/mnt/home/droundy/.jhc/cache' Main [test.hs] Typechecking... [1 of 1] Main (.............................................) Compiling... [1 of 1] Main <..................................................> src/FrontEnd/Representation.hs:98:0: No instance nor default method for class operation Data.Binary.put If I uncomment the type signature for main, the file compiles. It's not an important sort of program, but a compiler bug is a compiler bug, and I imagine it might manifest itself in some non-trivial program. -- David Roundy

1 1

darcs patch: removed use of RecordWildCards, which is buggy in ghc ...
by David Roundy 10 Sep '09

10 Sep '09

I'd prefer for this misfeature not to be used even if it *weren't* buggy! What a terrible idea, to introduce a syntactic sugar that shadows an existing binding with a totally different value of a different type, in such a way that you can only discover what has been done by searching some different file! If you did this by hand, compiling with -Werr -Wall would lead to a compile error---and rightly so. David Wed Sep 9 06:46:53 EDT 2009 David Roundy <droundy(a)darcs.net> * removed use of RecordWildCards, which is buggy in ghc 6.8.

3 4