Re: REMOVE the prior argument from activate
kgmuller <kgmuller <at> xs4all.nl>
2008-03-14 08:23:12 GMT
I support Tony's proposal, although I am the one who put
the "prior" clause into activate. It comes from Simula, my model for the SimPy
API.
What is wrong with "prior" is its semantics: what does it
mean (in modelling terms) to put an event notice ahead of all event
notices at the same time? What is the ordering of truly simultaneous
events?
If one wishes to model one process to be executed before
another process, one should model this explicitly by putting these processes
into a priority queue.
Klaus Muller
I propose that the prior argument be removed from the
activate and reactivate functions and the start method.
The command has the following syntax:
activate(p,
p.pemname([args])[,{at=now()|delay=0}][,prior=False])
Setting
prior = True
allows one to ensure that a process object (entity) is given priority over
other objects activated at the same time.
I suggest this is of
little use, I have not heard of anyone using it, and I believe it makes
maintaining the ordering of the event list more complicated. I can think
of a number of methods of obtaining the same effect so why should we retain
it? SimPy syntax is already too cluttered and we should work to
simplify it.
Does anyone actually use this? Would anybody object if
Klaus removed it?
Tony Vignaux
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Simpy-users mailing list
Simpy-users <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/simpy-users