[Ns-bugs] [Bug 164] Config calls which take a string can fail silently

[bugzilla-daemon@nsnam-www.ece.gatech.edu]

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





------- Comment #3 from mathieu.lacage at sophia.inria.fr  2008-04-09 17:22 -------
(In reply to comment #2)
> (In reply to comment #1)
> If a match fails on a certain string, the user should be notified of that.  A
> failure is a failure...it is then up to the user to then debug and figure out
> the WHY (does he misunderstand the path, is it a typo, is he asking for wrong
> attribute/trace source, etc).  I see them as two separate issues.

No, really, you have to understand that, from the point of view of the code,
failing to match "/NodeList/0/DeviceList/0/TxQueue" against a WifiNetDevice
instance because it does not have a TxQueue is just the same as failing to have
the same string with a typo match against a CsmaNetDevice because of the typo.
In the simple case where the user has not used wildcards, yes, one is obviously
an error and the other is not. 

But, if the user has used wildcards and a mixed network (wired + wifi), then,
the code has no way to know the difference between a match failure against a
non-existent and correctly spelled attribute (which is _not_ an error when
using wildcards) and a match failure against an existent but incorrectly
spelled attribute.


-- 
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.