A complete analysis of TCO for both approaches from the point of view
of a scenario writer is left as an exercise for the reader (drop it on
this list in a message with subject 'get the facts').
And the argument must be in favor of the switch/case solution then :-)
Well, I won't be so sure: having multiple cooperative thread (right now
glob2 preempt threads if they use too much instruction per steps, and
preemption is syncronous!) allow to specify one behaviour per thread,
which is much cleaner, easier to understand and maintain that a big
state machine. If you doubt, see how our big states machines in units
and buildings are a mess and you'll get an idea of why we should avoid
giant state machines whenever possible.
Steph
_______________________________________________
glob2-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/glob2-devel
