I've always wondered that as well. And I avoided using goto's because of it ( interesting side-effect being good structured code ?)

Then I learned a thing or two from developing "scripted" type applications myself ...

With Paul's permission - may I propose a theory on this ...

Scripted IF statements are usually implemented like a stack - with internalized push's and pop's - like this ...

code:

---

IF EXPRESSION (push)

 IF EXPRESSION (push)

  IF EXPRESSION (push)

  ENDIF (pop)

 ENDIF (pop)

ENDIF (pop)

---

KiX should/would always know how "deeply" IF nested it is at any given time.

When ones does a GOTO inside a deeply nested IF statement, scripting languages usually "POP" the entire stack then continue on like there's no pending (stacked) ENDIF.

I hope this doesn't start the old "GOTO/NOGOTO" debate !

Unless anyone's interested ?

Shawn.

p.s.

I did have a point to all this rant (and not just the one on my head)...

Using GOTO's in deeply nested IF's works. Sometimes it seems like the only way to go !

But I thought Jack, that you would have more to say about whether it was "COOL" or not !

Shawn..

[This message has been edited by Shawn (edited 23 May 2000).]