>It's harder to develop this
>way because the important routines end up getting scattered over
>several handlers, but is the only way to go, especially for
>time-critical applications like games.
I had come to assume this is what you referred to as "spaghetti code",
Scott, and I have even gone so far as to wonder what the better way was.
What is spaghetti code and how should one avoid it?
Rob Cozens, CCW
http://www.serendipitysoftware.com/who.html
"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."
from "The Triple Foole" by John Donne (1572-1631)
