 |
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5187
|
 Posted: Tue Nov 13, 2007 10:54 pm
[2.11] Parsing error with #WAITSIGNAL {string}
|
Again a problem with the braces.
#WAITSIGNAL def
Works properly and reports def as what is being waited for.
#WAITSIGNAL {def}
Does not work and reports an erronius number as what is being waited for. The number seems to be determined by how you structured the set of commands that included the wait. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Nov 14, 2007 12:07 am
|
OK, that's definitely a bug. I'll add it to the list. The first argument isn't optional and it's marked as a "string" value for the parser, so I don't understand why the braces don't work. But this could indicate a parser bug that might be effecting some other commands too.
|
|
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Wed Nov 14, 2007 12:48 am
|
Yeah, off the top of my head, this is the 3rd command / function to have issues with braces and not interpreting them as strings.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Nov 14, 2007 11:37 pm
|
Yep, this was a problem with several of the new commands added in v2.x. I wasn't handling {string} arguments properly. Should be fixed now in 2.12.
|
|
|
|
|
|
|
|
