[Ns-bugs] [Bug 1053] Need better error diagnostics in ns2-mobility-trace example

[code@nsnam.ece.gatech.edu]

https://www.nsnam.org/bugzilla/show_bug.cgi?id=1053

--- Comment #7 from Anirudh <sk.anirudh at gmail.com> 2012-01-09 07:47:52 EST ---
(In reply to comment #6)
> (In reply to comment #5)
> > Hi
> > 
> > I have enclosed a patch for this. Do let me know if anything else needs to be
> > done at my end. The patch is wrt ns-3-dev. In essence, I just added an
> > is_open() check to the constructor Ns2MobilityHelper() and I print an
> > NS_FATAL_ERROR if the file does not open. Hope that's fine.
> > 
> > Anirudh
> 
> I'm fine with adding such a check, but I got the impression from the original
> bug report that also making the system support relative file paths was going to
> be part of the solution.
> 
> Was that considered and dropped due to difficulty, or was the original intent
> just to check whether the file opened successfully?

I am not sure about that. The paths have to be relative to some directory and
the ns2-mobility-trace application can be run using waf from multiple
directories. How is the current working directory set, when using waf to run ns
applications ? And no matter how it is set, the above code should be able to
handle it I guess, because the arguments to open() can be absolute or relative
paths .

-- 
Configure bugmail: https://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.