Create abstract class for all VCI events about shadow HOT 3 CLOSED

I was thinking all events in shadow would follow the same pattern instead of having event "subtypes". This means the non-vci events (DTIMER, SIMOP, TICKTOCK) would also be refactored to extend the abstract class.

Or would it be better to differentiate "virtual" communication events (i.e. one node creating an event for itself or for another) from "physical" communication events (i.e. one process or thread creates events for another process or thread)?
Thoughts?

from shadow.

It seems that it is definitely possible to have just one abstract event class which is used both for virtual and physics events. However, there would seem to be quite a few variables that would just be used by the VCI events, and I would think having two separate abstract classes would allow for easier expansion for events that needed to be added to either the physical or virtual event class, especially if they differed in some major way.

For now I'll just go ahead and create a separate abstract class for non-vci events, but if at any point it's decided that it's better to have just one abstract class, it should be a relatively easy to make that change.

from shadow.

Any part of this that may not have been done will be cleaned up during the re-write of the threading engine.

from shadow.