From: Elias Athanasopoulos <elathan@phys.uoa.gr>
To: Matthew Studley <matthew.studley@uwe.ac.uk>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: mixing C/C++
Date: Mon, 10 Nov 2003 19:37:43 +0200 [thread overview]
Message-ID: <20031110173743.GA975@velka.phys.uoa.gr> (raw)
In-Reply-To: <003301c3a79b$643573e0$caba0ba4@uwe.ac.uk>
On Mon, Nov 10, 2003 at 03:00:31PM -0000, Matthew Studley wrote:
> Have you considered using SWIG to automatically generate your wrappers?
>
> ... SWIG is a software development tool that connects programs written in C
> and C++ with a variety of high-level programming languages. SWIG is
> primarily used with common scripting languages such as Perl, Python, Tcl/Tk,
> and Ruby...
Yes, I have tried it. I found it quite complicated in the sense
that I can't control stuff; it's difficult to hack the auto-generated
swig files. Also, it lacks compatibility with Ruby 1.8.
Thanks for your reply.
Regards,
--
University of Athens I bet the human brain
Physics Department is a kludge --Marvin Minsky
next prev parent reply other threads:[~2003-11-10 17:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 9:30 mixing C/C++ Elias Athanasopoulos
2003-11-08 13:36 ` James Stevenson
2003-11-10 15:00 ` Matthew Studley
2003-11-10 17:37 ` Elias Athanasopoulos [this message]
2003-11-12 4:35 ` convert INT to CHAR but print's BEEP J.
2003-11-12 7:11 ` Mikael Aronsson
2003-11-13 1:26 ` convert INT to CHAR - SOLVED J.
2003-11-13 6:36 ` convert INT to CHAR but print's BEEP Jeff Woods
-- strict thread matches above, loose matches on Subject: below --
2003-11-24 11:10 mixing C/C++ Elias Athanasopoulos
2003-11-24 12:18 ` Steven Shaw
2003-11-24 17:55 ` Elias Athanasopoulos
2003-11-25 2:21 ` Steven Shaw
2003-11-25 10:49 ` elathan
2003-11-25 11:42 ` Glynn Clements
2003-11-25 13:12 ` elathan
2003-11-26 2:09 ` Glynn Clements
2003-12-02 18:22 ` Elias Athanasopoulos
2003-11-25 16:32 ` Steven Shaw
2003-11-24 18:44 ` Dari'o Mariani
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=20031110173743.GA975@velka.phys.uoa.gr \
--to=elathan@phys.uoa.gr \
--cc=linux-c-programming@vger.kernel.org \
--cc=matthew.studley@uwe.ac.uk \
/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;
as well as URLs for NNTP newsgroup(s).