[Ns-developers] NS-3 Python

craigdo@ee.washington.edu craigdo at ee.washington.edu
Fri Jan 18 10:43:26 PST 2008


[ ... ]

> > Comments/objections?
> 
> Yes, my main question is:
>   - as a developer, what do I have to do to bind new models I add to
> ns-3 ?
>   - as a developer, what do I have to do to make sure that I do not
> break the bindings if I change the ns-3 API ?

Obviously getting the code in and starting to use it is the most important
thing, so this isn't really on any critical path; but I'm curious:

- Is it easy to tell which parts of the ns-3 API are covered and which are
not (especially with respect to Mathieu's "new models" comment)?
- Is how to find and use the Python APIs intuitively (or at least
relatively) obvious?
- How are we going to (initially and eventually) document the Python API if
bindings are automagically generated?

Regards,

-- Craig




More information about the Ns-developers mailing list