274 Release Notes

• Fixed: There was a bug in the '+' operator when one of the arguments was a text string constant but others were not.

• Fixed: variables declared inside of a loop, but which had no initial value specified, were not getting re-initialized to null in each iteration.

• Fixed: the security setting of worlds hosted directly in DS was getting set by the first world and retained for subsequent worlds. So if you loaded an ultrasafe world first, closed that, and then loaded a safe world (ie one in its own directory), the second world would be stuck in ultrasafe mode, which means it would generate annoying security prompts every time it tried to access any of its own files.

• When an object is deleted, all procedures in execution belonging to that object or being called by that object were getting immediately terminated. It no longer terminates procedures that were called by the deleted object but it still terminates procedures belonging to that object. (That's how it behaved prior to release 273.) When execution returns to the deleted object's procedures, they immediately terminate and return to the caller. Having it terminate code called by the deleted object (but not belonging to that object) was causing subtle problems in recursive situations. The only change retained from the 273 modification is that sleeping operations (sleep(), input(), shell(), and so on) being directly called by the deleted object are immediately terminated.

  Note that you can always disassociate a procedure from its object by setting src to null, but the default behavior is almost always what you want.