This continues a face-to-face discussion from last year.

It was pointed out that one downside of replacing 'enum state_kind'
with 'struct finite_state' is that when a 'struct state' is printed
using a debugger it no longer shows the 'state' as an enum.

Off hand I can think of two solutions:

- redundantly store both a 'struct finite_state' pointer, and an 'enum
state_kind' in 'struct state'
- store a copy of 'struct finite_state' in 'struct state'

My preference is for the second

Andrew
_______________________________________________
Swan-dev mailing list
[email protected]
https://lists.libreswan.org/mailman/listinfo/swan-dev

Reply via email to