 |
Dwoggurd
Wanderer
Joined: 29 Jan 2008
Posts: 63
|
 Posted: Tue Jun 24, 2008 6:14 pm
[2.28] Compatibility report and #BREAK
|
Compatibility report suggest that command #BREAK is not supported.
This is just an obsolete message or should I really trust it?
I mean #BREAK out of a loop. |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Tue Jun 24, 2008 6:40 pm
|
The compatability report doesn't know about all the new commands, it's a known bug. I guess this is another one it doesn't know about.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Jun 24, 2008 7:23 pm
|
Well, it reports that because it assumes you are running the compatibility report on imported zMUD scripts, and the #BREAK command in zMUD performed a completely different function (setting a breakpoint for the debugger). So if someone has a #BREAK command in their zMUD script, it is very important to flag that as a possible compatibility problem.
So this isn't actually related to the "bug" that Fang was mentioning. The actual bug in past versions was that the new #PRINT command was being confused with the #PRIORITY command, which the compatibility report was testing using the pattern "#PRI". I changed the pattern to "#PRI[^N]" in 2.28 so that bug is fixed.
Reporting the #BREAK command as a *possible* compatibility issue is not a bug. |
|
|
|
|
|
|
|
