[Ns-bugs] [Bug 123] SetInterfaceId is too easy to forget

bugzilla-daemon@nsnam-www.ece.gatech.edu bugzilla-daemon at nsnam-www.ece.gatech.edu
Wed Jan 2 06:39:47 PST 2008


http://www.nsnam.org/bugzilla/show_bug.cgi?id=123





------- Comment #3 from mathieu.lacage at sophia.inria.fr  2008-01-02 09:39 -------
(In reply to comment #2)
> I hate the fact that this ruins my python bindings. :-(

I am willing to make a patch for your bindings to ease integration of this
patch. Would you mind explain what exactly in this patch makes the
automatically-generated bindings cry ?

> I have a suggestion: why not make the Object::Object constructor require an
> InterfaceId argument, and make this base constructor call AddInterfaceId?  This
> way if you forget the InterfaceId you get a compile time error, and it's easy
> to fix the code.

The problem with the approach you suggest is that it is going to require you to
propagate the interface id from a subclass up to the base class: if there are 2
or 3 intermeditate classes, this is a lot of work.

Another problem is that this patch is the base of a larger set of patches which
aim at improving/adding features to the Object framework.


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


More information about the Ns-bugs mailing list