Oct. 6, 2001 In This Issue SE:ISDK upgrades for C and Java, 4.30 and 4.40   ISDK/C 4.30d Errata   ISDK/C 4.40c Errata   ISDK/Java 4.30d Errata Other Newsletters DevSpace Developer Support For more information and resources, visit ScriptEase: ISDK DevSpace online. Download Center For latest updates and extensions, visit the ISDK Download Center.

Errata/Upgrade releases now available for SE:ISDK/C 4.30e, SE:ISDK/Java 4.30e, and SE:ISDK/C 4.40d Errata release now available for all 4.30 and 4.40 platforms An update is available for all of the current ScriptEase:ISDK platforms. This release incorporates all of the errata updates that have been documented at the errata site for previous releases. New: Improved internal debugging You may have noticed that there were a lot of errata items published soon after the most recent ISDK releases. Many of these involved circumstances that were very unusual, or rare, and had never actually shown up in any product released or in-development with the SE:ISDK. These unusual and unlikely errata items were found because have enhanced the internal debugging algorithms; in debug mode this will always check the state of the jsecontext, jsestacks, jsevariables, and garbage collector, with the assumption that if anything can go wrong, it will. The result is greater reliability for development and use. The code looks different, is this just a minor errata release? If you compare the files between this release and the previous release (e.g. 4.30e vs 4.30d) you'll see a lot more changes than you'd expect from just the published errata items. So it Is reasonable to worry that this is a large change, and not just a plug-it-in minor errata release. (The number of errata items and code changes should decrease with each minor release, right?) But if you look at those changes, you will see they are related to the higher-level of internal debugging that has been added to the core engine, and nearly all these changes apply only if NDEBUG is not defined (i.e. they apply only when compiling in debug mode). Should you upgrade? Yes. This higher level of internal ScriptEase debugging will mean that your own applications are more robust, especially if you exercise internal debugging by testing your applications in a debug configuration and check your debug.log files. To receive your upgrades visit http://support.nombasxxx.com/ with information about platforms and version needed. Have a question about how to use ScriptEase:ISDK? Let Dr. Scripter know at http://support.nombasxxx.com/

 Errata

   ISDK/C 4.30d

• function.arguments deprecated: The arguments property of a Function object is an old leftover from erly javascript, and has been deprecated in current EcmaScript standards. For most applications function.arguments is a drawback because it may lock in varaibles longer than is wanted and may slow overall execution. [details]

• Object comparisons with wrong hint - Date comparisons fail: Object comparison (<, <=, >, >=) are not correctly following the hint logic specified in section 11.8.5 (The Abstract Relational Comparison Algorithm) of the ECMAScript specification. This is most likely to show up as a problem when comparing instances of the Date object. [details]

• ToNumber() returns incorrect values for "+" and "-": When ToNumber() is called with either "+" or "-" as its argument, the return value should be NaN. Instead, ToNumber() is returning Infinity and -Infinity, respectively. [details]

• Unix version of SElib.dynamicLink not locating shared object path: On unix systems, when calling SElib.dynamicLink(), that shared object may not be located via LD_ELF_LIBRARY_PATH or LD_LIBRARY_PATH. [details]

• global C variables conflict for multiple threads: The Ecma libraries contain globals which should be initialized only once, but in multiple threads may be initialized many times, potentially leading to invalid data or crashes. [details]

• COMOBJ C++ code contains global variables used for debugging: The COMOBJ C++ code contains global variables used for debugging. If run within multiple threads these globals will conflict. [details]

 Errata

   ISDK/C 4.40c

• Object comparisons with wrong hint - Date comparisons fail: Object comparison (<, <=, >, >=) are not correctly following the hint logic specified in section 11.8.5 (The Abstract Relational Comparison Algorithm) of the ECMAScript specification. This is most likely to show up as a problem when comparing instances of the Date object. [details]

• SEObjectWrapper not deleting createVariable() objects: The underlying variable reference created by SEObjectWrapper::createVariable() is not being destroyed when the SEObjectWrapper C++ object is deleted. [details]

• ToNumber() returns incorrect values for "+" and "-": When ToNumber() is called with either "+" or "-" as its argument, the return value should be NaN. Instead, ToNumber() is returning Infinity and -Infinity, respectively. [details]

• error marking more than MARK_STACK_SIZE objects: If there are more than MARK_STACK_SIZE tied to the call->Global object, then some objects may never be marked and so may be freed while still in use. [details]

• Unix version of SElib.dynamicLink not locating shared object path: On unix systems, when calling SElib.dynamicLink(), that shared object may not be located via LD_ELF_LIBRARY_PATH or LD_LIBRARY_PATH. [details]

• toString(radix) not returing correct value for 0: When toString is used with a radix (e.g. (0).toString(10)) the result is a blank string. [details]

• altering "arguments" causes assertion failure: Buffer.prototype.getString() is not terminating strings at the first null character, as specified in the documentation. [details]

• global C variable in Date object conflict for multiple threads: The Ecma Date library contains globals which should be initialized only once, but in multiple threads may be initialized many times, potentially leading to invalid data or crashes. [details]

• COMOBJ C++ code contains global variables used for debugging: The COMOBJ C++ code contains global variables used for debugging. If run within multiple threads these globals will conflict. [details]

 Errata

   ISDK/Java 4.30d

• Object comparisons with wrong hint - Date comparisons fail: Object comparison (<, <=, >, >=) are not correctly following the hint logic specified in section 11.8.5 (The Abstract Relational Comparison Algorithm) of the ECMAScript specification. This is most likely to show up as a problem when comparing instances of the Date object. [details]

• ToNumber() returns incorrect values for "+" and "-": When ToNumber() is called with either "+" or "-" as its argument, the return value should be NaN. Instead, ToNumber() is returning Infinity and -Infinity, respectively. [details]

• toString(radix) not returing correct value for 0: When toString is used with a radix (e.g. (0).toString(10)) the result is a blank string. [details]

• toString on functions concatenates some indentifiers: When a function is being converted to a string, a required space may not be displayed after some variables. [details]

• eval does not propogate the "this" of its caller: eval() does not propogate the 'this' of its caller. [details]

• static Array initializer is not instanceof Object: When an Array object is initialized with a static Array Initialiser (e.g. var foo = [ 1, 2, 3 ];) it is recognized as "instanceof Array" but is not recognized as "instanceof Object". [details]

• empty Object initializer creates an Array object; should be an Object object: When an object is initialized with the empty set (e.g. var foo = { };) it is initialized as a type Array object, although it should be an Object object. [details]

• "continue" within "switch" statement jumps to wrong condition: When creating tokens with jseCreateCodeTokenBuffer, floating point numbers are written incorrectly. [details]