I apologize for extra 'noise' by not realizing that Benedikt posted reply on the tracker explaining the workaround with working example. Hi Gour, sorry for the late reply. To clarify, I ported c2hs to use language.c (my summer of code

On 30.10.2008, at 22:38, Gour wrote: project), which fixes a few bugs in the C frontend. Additionally, I fixed a few additional bugs in c2hs, and, as a little bonus, implemented enum define hooks. Enum define hooks aren't essential though, you can easily simulate them using inline C. I've chatted with duncan a while ago, and he told me that manuel or he will take a look at the patches when there's time, but they're quite busy now I suppose (with the upcoming release of ghc 6.10). Anyway, I'm still available for questions or help. best regards, benedikt p.s.: It would be nice if the tracker would support CC emails, to stay in touch with updates on tickets

Thanks a lot!

Sincerely, Gour

--

Gour | Zagreb, Croatia | GPG key: C6E7162D ---------------------------------------------------------------- _______________________________________________ C2hs mailing list C2hs@haskell.org http://www.haskell.org/mailman/listinfo/c2hs

Still, 'enum define' hooks are nice add-on and it enhances c2hs functionality. Yes, they're certainly easier to manage from the library author's

/me would like to see c2hs as ffi-tool-of-choice for Haskell users.

Atm, however, most of pkgs use hsc2hs...it looks having some more examples/docs of using c2hs would be great - like having example from the Real World Haskell book (FFI chapter) done in c2hs or something... At least there's gtk2hs, but they use a private fork of c2hs - I think

On 06.11.2008, at 14:35, Gour wrote: point of view. Improving automatic type mapping seems to be a good idea as well. there were plans to merge them at some point though.

Benedikt> I've chatted with duncan a while ago, and he told me that Benedikt> manuel or he will take a look at the patches when there's Benedikt> time, but they're quite busy now I suppose (with the upcoming Benedikt> release of ghc 6.10).

Right. He told me it's on todo list, but in the meantime I'll use your branch.

Benedikt> Anyway, I'm still available for questions or help.

Private email or sending here? It's probably best to send general suggestions and comments to the list. If you have some questions/bug fixes specific to the port, I'm fine with private email, too.

best regards, benedikt