Re: [Swig-user] Breaking up large module

[Brendon C. <br...@ch...>]

> What do you mean by a "single" module?  Can each .cpp file result in its
> own sub-module, which are then grouped into a directory with an
> appropriate __init__.py file?
>

Basically i have a number of classes in a namespace in C++:

namesapce EDoc
{
   class File {...};
   class Type {...};
   class FunctionType {...};
   class Function {...};
   class CodeBlock {...};
   ...
}

I hope to have these accessible from python like:

v = edoc.File()
v = edoc.Type()
v = edoc.FunctionType()
v = edoc.Function()
v = edoc.CodeBlock()
...

So they will all belong to the "edoc" module in python NOT sub-modules like:

edoc.func.Function()
edoc.type.Type()
...

But i would like to place the wrapper code for each class into a
seperate cpp file (or at least a couple of classes in a cpp file each).
So i have:

File.i
Type.i
FunctionType.i
...

Which currently produce:
edoc_wrap.cpp

I would like to produce:
edoc_wrap.cpp
edoc_wrap_File.cpp
edoc_wrap_Type.cpp
...

which all link together to make the _edoc.la module.

Sorry, if that was a bit verbose...

Is this sort of think possible? Is what you were mentioning that i could
have seperate sub-modules (say call the module edocimpl) as you said and
have a single native python module called "edoc.py"  that does something
like "from edocimpl.func import *" for each sub-module?

Thats not my preferred option, but it might work.

Thanks for the reply,
Brendon.