[Ns-bugs] [Bug 492] It would be useful to have a pre-simulate state (and post)
code@nsnam.ece.gatech.edu
code at nsnam.ece.gatech.edu
Thu Feb 5 23:39:35 PST 2009
http://www.nsnam.org/bugzilla/show_bug.cgi?id=492
--- Comment #3 from Craig Dowell <craigdo at ee.washington.edu> 2009-02-06 02:39:34 EDT ---
> Thus, I have to ask: why can't the user call directly the
> emu/tap initialization functions at the proper time ?
The user *can* be asked to know that s/he has got to call a certain method at a
certain time. We would have to communicate to the user via documentation what
that method is and when it should be called; and rely on the user to do it
correctly. This introduces an annoying new requirement that is extremely
position dependent in a script. I don't think this is good.
I think it is better to *not* export that requirement since the device knows
when it needs to be called, how it needs to be called, and knows when it has
all of the information it needs. Currently it schedules an event to do it. It
works well. The user doesn't need to know anything about it.
It would be nice not to have to place that burden on the user and at the same
time not mess up the realtime situation at the first event time.
What I suggest would mean calling a generic function just before
Simulator::Run. Compare this with having to understand, for example, if you
want to add a tap device you have to call function X with parameters Y and Z
just before run; if you want to add an emu device you have to call function X'
with parameters a, b, and c; if you want to run some other model, you have to
call blah, blah, blah.
IMO, It's a good thing for several reasons
--
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Ns-bugs
mailing list