Gez wrote:Does it actually have a noticeable impact?
It may not have an impact performance wise, but it might be a nice tip for those who may be having problems with runaway scripts. I know there was a thread about a non-infinite loop runaway at least once.
Edit: At the very least it may be worth documenting these things so that if someone finds old code using it they understand what it means. Even if we don't document it on the page for each function where it applies.
Zippy wrote:While it is a little aggressive, it does serve its primary point: any new maps created after the point of deprecation should never use the feature; instead using the replacement feature. While it can technically, and in a lot of ways completely safely, be gotten away with, its still a point of both principle and caution. So anyone who feels they know better may certainly disregard it (at their own peril if the case actually merits it), but for the people who don't know any better or actively refuse learn better, if the extra aggressiveness just convinces them even more that they should be using the correct new feature out of some imagined risk then really what harm is there in it?
My point is the ZDoom wiki is often used as a general reference for things even outside of ZDoom. While there may be a better alternative in ZDoom, someone writing a Hexen compatible script may not want to use the alternative. Thus the deprecation warning is kind of out of place in this one specific instance.
