Barend Gehrels wrote:
(Of course) I forgot some state transitions and had to include the no_transition function, to avoid assertions. This is all working well. I wondered if non-possible transitions could be catched compile-time, but apparently this is not possible (because of triggers and guards).
I wonder if the library can provide a debugging mode that would provide a helpful default implementation of no_transition that could help identify the unknown transition rather than requiring the user to write something? Such a function might access internal details, perhaps only provided in the said debugging mode, that would be clearer about the source state and event for which no transition was provided than would user-level code. _____ Rob Stewart robert.stewart@sig.com Software Engineer, Core Software using std::disclaimer; Susquehanna International Group, LLP http://www.sig.com IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.