The logger can freeze due to unknown methods about hfsm2 HOT 5 CLOSED

There are several reasons why I prefer the return on failure to be nullptr:
0. it's a standard failing return value

1. checking against 0 is the fastest check, typically implemented with test eax, eax without the use of any other registers or values
2. I'd rather the program crashed on error, than silently producing invalid output
3. if it did return "\0", checking for it required a pointer dereference, most likely a cache miss

from hfsm2.

Thanks for reporting, Alexis, I'll look into it.

from hfsm2.

Should be fixed in 1.2.2

from hfsm2.

I don't think it should return nullptr as examples of the logger stream the output to std::cout with no nullptr check on the data.

from hfsm2.

In the meantime, this freeze should not happen as all methods are caught. :)

from hfsm2.