On Fri, 2007-12-21 at 10:25 +0100, Gour wrote:
On Thu, 20 Dec 2007 03:41:21 +
Duncan Coutts [EMAIL PROTECTED] wrote:
In gtk2hs we use both. We use c2hs for all function calls and we use
hsc2hs to help us write Storable instances for a few structures.
It looks that c2hs does more
On Thu, 20 Dec 2007 03:41:21 +
Duncan Coutts [EMAIL PROTECTED] wrote:
The main advantage of c2hs over hsc2hs is that c2hs generates the
correct Haskell types of foreign imports by looking at the C types in
the header file. This guarantees cross language type safety for
function calls. It
stevelihn:
On Dec 11, 2007 11:16 PM, Don Stewart [EMAIL PROTECTED] wrote:
2. It offers strong support for integration with other languages and
tools
(FFI? Is the support strong?)
2. The FFI in Haskell is perhaps the most powerful out there.
You can import C or
On Wed, 2007-12-19 at 19:07 -0800, Don Stewart wrote:
There are three approaches, depending on the size of your project.
Write your ow FFI decls manually.
- Good when you have a small job
- and the C types are simple
- example:
strlen
Use
