 |
Arminas
Wizard
Joined: 11 Jul 2002
Posts: 1265
Location: USA
|
 Posted: Thu Apr 26, 2007 2:13 am
[1.30] Improper detection of infinite loops.
|
This code triggers the infinite loop detection message.
| Code: |
| #alias loopm {#if (@numb=1) {loopm;numb=0}};numb=1;loopm |
Note that if you place the numb=0 BEFORE the loopm in the if the loop message does not come up.
This message comes up even if the IF would never be true. |
|
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Apr 26, 2007 2:21 am
|
The command that you show *does* give an infinite loop, and that is correct.
You are calling "loopm" from within itself *before* you are setting the numb=0. So this *is* an infinite loop. It never gets to the "numb=0" command.
| Quote: |
| This message comes up even if the IF would never be true. |
Not sure what you mean by that. If I enter this:
then I don't get any loop message, which is correct.
So, I don't see what the problem is that you are reporting. |
|
|
|
|
Arminas
Wizard
Joined: 11 Jul 2002
Posts: 1265
Location: USA
|
Posted: Thu Apr 26, 2007 2:51 am
|
Gotcha. 
|
|
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
|
Arminas
Wizard
Joined: 11 Jul 2002
Posts: 1265
Location: USA
|
Posted: Thu Apr 26, 2007 2:55 am
|
I would like to mention. This was NOT caught in previous versions. So looks like you fixed something you didn't know was broken.
|
|
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Thu Apr 26, 2007 3:08 am
|
Hmm, that is interesting.
|
|
|
|
|
Arminas
Wizard
Joined: 11 Jul 2002
Posts: 1265
Location: USA
|
Posted: Thu Apr 26, 2007 1:24 pm
|
I need to look at this more. I came up with a bad example of what I was trying to do.
Though it is probably already fixed by one of the quick fixes.
This particular thing did work in 1.28 and the loop was detected after installing the first version of 1.30. I don't have my code here but I was able to test my PROPERLY detected loop mentioned above on 1.28 and I received the message. So I'll post about this again tonight some time. |
|
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
|
Arminas
Wizard
Joined: 11 Jul 2002
Posts: 1265
Location: USA
|
Posted: Thu Apr 26, 2007 10:59 pm
|
It was indeed a problem with the first build of 1.30 and it is working great now so I'll shut up about this now.
|
|
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
|
|
|
|
|
|
