----- Original Message -----
From: "Phil Tomson" <ptkwt / shell1.aracnet.com>
Newsgroups: comp.lang.ruby
To: "ruby-talk ML" <ruby-talk / ruby-lang.org>
Sent: Saturday, August 03, 2002 1:35 AM
Subject: embed or swig?


> Then it hit me... we alreay wrap all of our C++ objects with Swig so that
> we can do unit testing in Ruby using Test::Unit so why not take it a step
> further and use Ruby to tie together all of our C++ objects.  The idea
> being that instead of embedding Ruby into our C++ application we'll use
> Ruby to manipulate the objects defined by C++.  All of the comutationally
> intensive stuff is already done in those C++ classes so there won't be any
> performance hit.  We won't define a main() function on the C++ side, we'll
> just create the shared library from the swig wrappers and instantiate
> those objects in Ruby.

This sounds very interesting to me... can you
explain how this actually works?

I've never really looked at SWIG. I didn't
realize it was quite this powerful...

Hal