From: James Stevenson <james@stev.org>
To: Elias Athanasopoulos <elathan@phys.uoa.gr>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: mixing C/C++
Date: Sat, 8 Nov 2003 13:36:55 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.44.0311081335520.29371-100000@god.stev.org> (raw)
In-Reply-To: <20031108093029.GB802@velka.phys.uoa.gr>
Hi
this is because you program doesnt know what the functions
are called so you need to add protypes.
Either create a header and put a prototype of the
function name in there and include the header file
or
add the prototypes to the top of the C file.
James
On Sat, 8 Nov 2003, Elias Athanasopoulos wrote:
> Hello!
>
> I want to create Ruby bindings for a C++ project, so my first
> step is to call C++ code from C, since Ruby has a plain C API.
>
> Consider I have a Foo class which its implementation is compiled
> in a shared lib (libtest.so). I have a second wrapper lib:
>
> #include "libtest.h"
>
> extern "C" class Foo * wrap_foo_ctor() { return new Foo(); }
> extern "C" void wrap_foo_set_food(Foo *f, int i) { f->set_food(i); }
> extern "C" int wrap_foo_hello(Foo *f) { return f->hello(); }
>
> Using the above my C program is:
>
> #include <stdio.h>
> #include <stdlib.h>
>
> int main(void)
> {
> struct Foo *m = (struct Foo*) wrap_foo_ctor();
>
> wrap_foo_set_food(m, 10);
> wrap_foo_hello(m);
>
> free(m);
>
> return 1;
> }
>
> And:
>
> elathan@velka:~/src/bindings> gcc foo.c -Wall -ltest -lwrap -o foo -L/home/elathan/src/bindings
> foo.c: In function `main':
> foo.c:6: warning: implicit declaration of function `wrap_foo_ctor'
> foo.c:8: warning: implicit declaration of function `wrap_foo_set_food'
> foo.c:9: warning: implicit declaration of function `wrap_foo_hello'
> elathan@velka:~/src/bindings> ./foo
> 10
>
>
> My main question is how to silent the implicit declaration warning in
> gcc, which is, of course, correct. I want everything to compile with -Wall.
> Is there a warkaround?
>
> I tried to create a C header file, but I don't know how to make a C prototype
> of:
>
> class Foo * wrap_foo_ctor() { return new Foo(); }
>
> Or silent the 'icompatible pointer type' warning in declarations, such as:
>
> int wrap_foo_hello(Foo *f) { return f->hello(); }
>
> TIA,
>
next prev parent reply other threads:[~2003-11-08 13:36 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 [this message]
2003-11-10 15:00 ` Matthew Studley
2003-11-10 17:37 ` Elias Athanasopoulos
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=Pine.LNX.4.44.0311081335520.29371-100000@god.stev.org \
--to=james@stev.org \
--cc=elathan@phys.uoa.gr \
--cc=linux-c-programming@vger.kernel.org \
/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).