Erroneous CON parser warning on "nullop"
A nullop in brackets may cause a “nullop’ found without
else’” warning.
Btw, is there a reason why the citations start with ` instead of ' ?
This legit construct can be easily avoided be removing the brackets, but is surely handy during development.
Example log excerpt (World Tour), EDuke r8865-c4e58ebe :
Including: EPISODE5BOSS.CON (8197 bytes)
EPISODE5BOSS.CON: In state 'BOSS5code':
EPISODE5BOSS.CON:377: warning: 'nullop' found without 'else'
Example code excerpt (World Tour, EPISODE5BOSS.CON):
ifhitweapon {
ifwasweapon FLAMETHROWERFLAME {
nullop
}
else {
state checkBOSS5hitstate
}
}
Edited by LeoD