- Joined
- Jul 2, 2011
- Messages
- 2,161
Hello
I have a bug to report with our jass checker.
Jass checker seems to be unable to identify when an if statement is active and when it's completely off. Resulting in leak errors for every if statement you have.
This problem shouldn't be too hard to check. Simply write in a code that checks the values of the if statement(what it is looking for) and compare that value with every other if statement in that trig. If the if statement doesn't match any other statement value they you know that it activates separately from the other statements and thus can be excluded.
An example of this would be to create a for loop
for (int j=0;j<100;j++)
{
if(j==0){do action with location}
destroy location
}
If all your if statements activate at different times then you know that their locations need to only be destroyed once....
I hope this makes sense
I have a bug to report with our jass checker.
Jass checker seems to be unable to identify when an if statement is active and when it's completely off. Resulting in leak errors for every if statement you have.
This problem shouldn't be too hard to check. Simply write in a code that checks the values of the if statement(what it is looking for) and compare that value with every other if statement in that trig. If the if statement doesn't match any other statement value they you know that it activates separately from the other statements and thus can be excluded.
An example of this would be to create a for loop
for (int j=0;j<100;j++)
{
if(j==0){do action with location}
destroy location
}
If all your if statements activate at different times then you know that their locations need to only be destroyed once....
I hope this makes sense