[Ns-developers] Modular bindings: status
gjcarneiro at gmail.com
Mon Mar 28 09:43:12 PDT 2011
I have been working on modular Python bindings, and at this point I think
they are becoming stable to the point that I might consider switching the
default to the modular bindings instead of the monolithic ones. I think the
all the functionality of the old bindings has been ported over to the new
ones. The generated code is not as efficient as it could be, but nothing
major. When modular bindings are enabled, a compatibility 'ns3' virtual
module is generated, which makes the modular bindings appear as a 'ns3'
module, for backward compatibility. But for the sake of efficiency, a
deprecation warning is given when ns3 is imported instead of ns.
What is developers opinions for ns 3.11?
1. Build modular bindings by default, monolithic is a configure option;
2. Build monolithic bindings by default, modular is a config option;
3. Build modular bindings by default, monolithic bindings are just removed
to avoid confusion;
My personal opinion is option 1 for now. The previous (current) plan used
to be option 2, because I wasn't sure if I could make modular bindings
stable in time.
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