 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
 Posted: Sat Mar 22, 2008 11:08 am
[2.20] Reparse trigger type and #STATE causes loop
|
This seems to be an infinite loop and is a rather bad thing. The idea I was having in trying this is to make a trigger such that one reparse state will stop further testing of the trigger. Most likely not the best way to go about it, but an infinite loop should still not be caused by this.
Procedure
1. Launch CMud
2. Close Sessions window (ESC)
3. Enter at the command line
| Code: |
| #TRIG {ab} {};#COND {a} {#STATE ab 0} {reparse};#COND {b} {} {reparse} |
4. Enter at the command line
|
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Sat Mar 22, 2008 11:21 am
|
I dunno what it is that makes your usage different from mine, but mine is working fine. Entering
| Code: |
| #TRIG {ab} {};#COND {a} {#STATE ab 0} {reparse};#COND {b} {} {reparse};#say ab |
on the command line caused CMUD to freeze. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Sat Mar 22, 2008 4:36 pm
|
Seems like something reasonable that should work, so I've added it to the bug list.
|
|
|
|
|
|
|
|
