From: Eray Ozkural <exa@kablonet.com.tr>
To: David Fox <david.fox@lindows.com>
Cc: caml <caml-list@inria.fr>,
"Brandon J. Van Every" <vanevery@indiegamedesign.com>
Subject: Re: [Caml-list] Efficient C++ interfacing?
Date: Sun, 6 Jun 2004 21:47:52 +0300 [thread overview]
Message-ID: <200406062147.52259.exa@kablonet.com.tr> (raw)
In-Reply-To: <40C343D7.1030009@lindows.com>
On Sunday 06 June 2004 19:18, David Fox wrote:
> Unfortunately, those bindings are over three years old, and despite the
> claim of being generated automatically, are continually becoming stale
> and rarely work. There are now tools called "Kalyptus"and "Smoke" in
> the kdebindings module of the kde.org CVS server, which is used to
> generate several language bindings, none of which is C, but one of which
> is Smoke. In the smoke directory it looks like there are now
> conversions for both Qt and KDE. So maybe the pieces are all there now.
>
Yes, the smoke lib is favored among kdebindings developers. They too wish to
eliminate the manual labor that was needed before to patch the C libs... I
wonder how well the python bindings perform right now. Python too is a quite
high level language.
Regards,
--
Eray Ozkural (exa) <erayo@cs.bilkent.edu.tr>
Comp. Sci. Dept., Bilkent University, Ankara KDE Project: http://www.kde.org
http://www.cs.bilkent.edu.tr/~erayo Malfunction: http://malfunct.iuma.com
GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2004-06-06 18:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 7:41 Brandon J. Van Every
2004-05-30 11:47 ` ronniec95
2004-05-30 20:17 ` Brandon J. Van Every
2004-06-05 16:45 ` Eray Ozkural
2004-06-05 19:07 ` skaller
2004-06-06 0:31 ` Eray Ozkural
2004-06-06 3:33 ` John Goerzen
2004-06-06 7:00 ` skaller
2004-06-06 16:02 ` David Fox
2004-06-06 18:44 ` Eray Ozkural
2004-06-06 20:41 ` skaller
2004-06-07 3:04 ` Eray Ozkural
2004-06-07 7:41 ` Benjamin Geer
2004-06-07 13:38 ` Eray Ozkural
2004-06-07 14:18 ` Basile Starynkevitch local
2004-06-07 14:29 ` Eray Ozkural
2004-06-07 16:29 ` Eray Ozkural
2004-06-07 15:46 ` skaller
2004-06-06 16:00 ` David Fox
2004-06-05 21:39 ` Brandon J. Van Every
2004-06-06 16:18 ` David Fox
2004-06-06 18:47 ` Eray Ozkural [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200406062147.52259.exa@kablonet.com.tr \
--to=exa@kablonet.com.tr \
--cc=caml-list@inria.fr \
--cc=david.fox@lindows.com \
--cc=erayo@cs.bilkent.edu.tr \
--cc=vanevery@indiegamedesign.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox