 |
Caled Sorcerer
Joined: 21 Oct 2000 Posts: 821 Location: Australia
|
Posted: Wed Oct 24, 2007 7:23 am
[2.08] Expression trigger bug |
Quote: |
<class name="Test" id="1">
<trigger type="Expression" priority="20" id="2">
<pattern>@testvar=1</pattern>
<value>#SHOW Testvar now equals @testvar, and it SHOULD equal 1</value>
</trigger>
<var name="testvar" id="3">0</var>
</class> |
1. Blank settings file, by hitting ESC from char selection screen.
2. Create the quoted settings.
3. Enter "testvar=1" to command line. Nothing happens.
4. Enter "testvar=0" to command line. Following line is displayed:
Testvar now equals 1, and it SHOULD equal 1
5. Show mild surprise. Enter "#sh @testvar" to command line. Following is displayed:
0
6. Show more surprise :D |
|
_________________ Athlon 64 3200+
Win XP Pro x64 |
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sat Oct 27, 2007 2:46 am |
Well, this is definitely a weird one.
After creating the trigger, click on the "Compiled Pattern" tab to see the code:
Code: |
0000 VARREF @testvar <testvar> (class untitled)
0024 INT 1
0032 NEQ |
Notice surprise when you see the last operator is "NEQ" which is the "not-equal-to" operator instead of the expected "EQ" operator! Obviously a bad parser bug. Should be fixed in 2.09 later tonight. |
|
|
 |
Zugg MASTER

Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Sat Oct 27, 2007 2:52 am |
OK, that was actually just a bug in the display of the disassembler...all of the operators AND, OR, XOR, LT, LE, GT, GE, EQ, NEQ were off by one. But it was still performing the EQ operation even though it showed NEQ, so that isn't the problem causing this expression trigger not to work. Still looking.
|
|
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|