Renamed duration -> eventDuration
Problem: We had a variable cMessage::duration for Horizon and avariable cPacket::duration from OMNeT++ itself while cPacket inheritsfrom cMessage. This might lead to the wrong variable being accessedby packets.
Solution: Renamed the Horizon variable cMessage::duration in...
[master] thread safe event ordering for EEF scheduler
[core] implemented thread-safe(r) FES ordering
[eefscheduler] encapsulated getProcessingDelay-call in the getEventDuration() of cMessageThe duration of a message is invalidated in scheduleAt and sendDirect/Delayed
[eefscheduler] solved initialization bug of t_start- now using delivd instead of t_start (t_start was redundant to delivd)- removed t_start from code- some code cleanup (some debug output removed..)
Initial import of Horizon 4 release.