[Ns-developers] ns-3 modular python bindings => merged
gjcarneiro at gmail.com
Thu Mar 17 08:46:47 PDT 2011
On Thu, Mar 17, 2011 at 14:01, Mathieu Lacage <mathieu.lacage at gmail.com>wrote:
> On Mon, Mar 14, 2011 at 19:07, Gustavo Carneiro <gjcarneiro at gmail.com>
> > 4. When a module includes a header of another module, all the types of
> >>> other module are imported by its python module. Maybe it is possible
> >>> detect which types are actually needed by the current module's bindings
> >>> import just those types; I'll have to check if I have time.
> > This would be an optimization, not that important.
> My intuition is that this is more than an optimization because if I
> make an API modification/addition in the 'core' module, then I get to
> rescan all modules ? This is not going to be fun at all :/
It's not clear yet how a change in the core module will impact other modules
that depend on it. But, in principle, only if you remove a class from the
core module (or rename) will you need to rescan every other modules.
Modifying a class' methods or functions inside a module will not have
impact on other modules.
I think not all the problems can be immediately foreseen. We have to try,
and see how it works.
 there will likely be exceptions, like, adding a pure virtual methods
that makes a class abstract, where before it was not, has a big impact, even
on other modules.
Gustavo J. A. M. Carneiro
INESC Porto, UTM, WiN, http://win.inescporto.pt/gjc
"The universe is always one step beyond logic." -- Frank Herbert
More information about the Ns-developers