[Ns-bugs] [Bug 631] RealtimeSimulatorImpl not compatible with python bindings

[code@nsnam.ece.gatech.edu]

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





--- Comment #6 from Mathieu Lacage <mathieu.lacage at sophia.inria.fr>  2009-07-13 07:23:16 EDT ---
(In reply to comment #5)
> IMHO we should avoid threads in non-realtime simulator due to performance
> issues and portability issues.  I think the RunOne solution is so simple, why
> don't you like it?  It is surely a lot simpler than any threaded solution you
> may want to throw at it.

Because it makes it impossible to support the realtime scheduler, the mpi
parallel scheduler, and, the threaded parallel scheduler. To summarize, nothing
but the simplest default simulator works with RunOne. So, yes, it's simple,
but, it kills our ability to do fancy things underneath: it is exposing too
much from the event loop so, I would rather kill it.

> The realtime scheduler problem is a different one.  But a solution to it is not
> trivial.  I think we should just add some way to find out whether the
> implementation supports RunOne and avoid calling it if not.  Naturally if we do
> not call RunOne then we'll not catch Ctrl-C, but at least the simulator will
> work from python automagically.
> 
> After that we can try to get Ctrl-C to work again, maybe using threads as you
> suggest, but to be honest I think it is more work than the feature is worth...

I have other features in mind.


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