QF::newRef_ Should Support Static Events (Non-dynamic Events)

[quantumleaps]

QF::newRef_ Should Support Static Events (Non-dynamic Events)

[quantum-leaps]

The Q_NEW_REF() API is an advanced optimization, which is intended to be used only for frequent dynamic events, where such optimization is actually worth it. In all other cases, any information from an event that is needed beyond the current RTC step should be simply copied into the private data of the AO.

The QF::newRef_(), which underlines the Q_NEW_REF() macro, already asserts that the event is dynamic. This is exactly per the intent.

--MMS

[DanielLyubin]

I understand why it's needed. I'm saying that it needs to support non-dynamic events., i.e remove the assert

[quantum-leaps]

I'm not sure if removing the assert is a good idea. Without the asset the "event-reference" mechanism could be abused for static events.