IG for c++

luc <>
Mon Oct 30 10:14:03 CET 2000

first, thanks for IG. i spent yesterday experimenting with erl_interface
ang IG, and that's quite neat (after one week experimenting doing all by
hand, what a progress in productivity!  but , at least, i understand the
problem better now).

now, my problem : i d like to wrap a C++ lib.
my question : how complex is it to modifiy IG to handle C++ ?
 this can get from simple to not so simple :
- a) adding # ifdef _cplusplus , external "C" {.... at the begining and
end of headers files. supposely no big deal.
- b) creating wrapper C for C++ members (functions, variables) by:
    - extending the parsing headers to understand class:functions(arg)
instead of simply functions(arg)
    - directly parsing the class file headers class X {.....}

how complex is the grammar extension ? the parser ? is it generated with
Yecc ? (the history from the doc tends to make me thinking the opposite,
but there is a .y files in the sources ?


First, they ignore you.
Then, they laugh at you.
Then, they fight you.
Then, you win.
--- Gandhi
Working code is what matter, not your market capitalization.--Kurt granroth
This is not a matter of waiting for something to happen. Instead, it is a matter of making something happen. -- Matthias:

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20001030/0174961b/attachment.html>

More information about the erlang-questions mailing list