From: Lyle Johnson <lyle@...>
Date: 2003-04-18T11:30:00+09:00
Subject: Re: [swig] avoiding the module name

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Simon Strandgaard wrote:

| I'm working on a embedding-tutorial with some skeleton code.
| If someone wants to extend this code with a new class,
| then he/she has to write a bunch of code, spread out
| over many different files.
|
| I'm trying to reduce this number of places where you need
| to make changes :-)

This sounds a little suspicious ;)

| Is there some way to tell SWIG that it should NOT
| encapsulate the classes in a %module module ???

SWIG 1.3.19 definitely doesn't support this. I think I could add such an
option if it proves useful but I don't want to add this feature just
because I know how to do it. The reasons for hiding a module's classes,
methods and constants in its own namespace are pretty well recognized,
whether you're talking about Ruby or any other programming language.

Can I see the tutorial, or something that might be a little more
convincing of an argument for adding this?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+n16HRy8FwLkdsRcRAuVAAKCKmfn1ool9ojI1a7k1+bZ0XSbZTACgqwe2
c+azPO2uqJp5ApFzkBtlH0o=
=seQA
-----END PGP SIGNATURE-----