Re: SWIG

new topic     » goto parent     » topic index » view thread      » older message » newer message

Tone Skoda wrote:

> David, what's up with that your swig_eu?
> How finished is it and why did you abandon it?

Well, I was using Win95 and the BCC (Borland C Compiler). At the time (some
time in August), BCC was having trouble generating code on Win95 - something
about putting garbage out on page boundaries. I installed the fixes, but
continued to have problems.

After my initial release of the SWIG library, I couldn't ever get it to
compile properly - even the working version that I had submitted crashed and
burned. After a couple weeks of this, I threw up my hands and tried writing
a version in Euphoria. I wrote Ox (my version of YACC for Euphoria) to help,
but got distracted and wrote Py instead.

I got back on track and started writing a version of SWIG for Euphoria
again, with the goal of wrapping wxWindows. The scope of this tool is a bit
smaller than SWIG - it requires that you clean up the input file before it
can be processed - but it works. It doesn't handle typedefs yet, and other
things need to be cleaned up. But wrapping wxWindows into a DLL isn't
entirely trivial, so that project got put on hold...

I should be working on the project in a couple weeks, though, since I'll
need it for something else that I'm doing.

> Why weren't any C/C++ libraries wrapped with it
> (GLUT/OpenGL, SciTech MGL, Allegro/Win32)?

See above.

> I'm willing to devlop this project further.

Go for it! The problem with what I wrote is that it doesn't integrate into
the SWIG type mechanism, because I really didn't understand it when I wrote
it. It's been a couple of months since I've checked the site - they might
actually have documentation for the new version of SWIG by now.

-- David Cuny

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu