Apr. 18, 2002 In This Issue SE:ISDK/C 5.00 upgrade   SE:ISDK/Java 5.00 initial release   Nombas support site upgrade   ISDK/C 5.00b Errata   ISDK/C 4.40e Errata   ISDK/C 4.30f Errata   ISDK/Java 4.30f 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.

SE:ISDK/C 5.00c upgrade now available SE:ISDK/C version 5.00c errata release is now available. This 5.00c release includes: An entirely new debugger integrated into the WorkShop, and a new debug-API defined for debugging remotely over TCP/IP. This replaces the versions of the debugger and debug API for all previous 4.x and 5.x releases. Updates for all of the errata items from version 5.00b Additional internal testing, when NDEBUG is not defined, to ensure proper use of the stack and of lifetime management of objects and strings New APIs for locking and freeing strings retrieved from seGetString Speed and memory optimizations for short strings (which average around 50% of all strings used) Support for RIM/Blackberry platform Core allocation failures no longer abort, but instead create ecmascript error objects and return normally (i.e. no more mustmalloc in the core; the next release will complete our work removing mustmalloc) SEDynamicWrapper updated so it no longer requires STL, and will work with older C++ compilers seEnableDynamicMethod API function has been restored COMOBJ for Win32 has been updated for the version 5 API To receive your SE:ISDK/C 5.00c upgrades contact http://support.nombasxxx.com/ with information about platforms and version needed. SE:ISDK/Java 5.00c initial release The gold-medal benefits of the new Version 5 API, as described in the January 11 Newsletter, are now available for SE:ISDK/Java application developers. This initial release is called 5.00c, to match the version number of the C release. This release includes the core engine and all of the standard libraries converted to the version 5 API. This 5.00c Java release does not yet have a finished document, and is not yet integrated with the workshop and the debugger. To receive SE:ISDK/Java 5.00c upgrades visit http://support.nombasxxx.com/. Support site upgrade On April 17 and 18 we upgraded our Nombas Help & Support Site for improved performance, query options, and privacy. On these two days the support system was often disabled. I don't think we lost any support issues, but there was a period where we were unable to respond to incidents. The system is now up and working and we're getting through all incidents quickly. I apologize for any delays in support during this upgrade period. Over the next couple of weeks we will continue to upgrade features of our support system, but we do not expect any more periods where it will be disabled. Have a question about how to use ScriptEase:ISDK? Let Dr. Scripter know at http://support.nombasxxx.com/

 Errata

   ISDK/C 5.00b

• 5-character variables names incorrect if either of last two characters is '$': In many cases, internal representation of variable names will be incorrect if the string is 4 or 5 characters long and either of the last two characters are '$'. For example, the names "book" and "book$" would conflict and both represent the same variable. [Details]

• seEval(...SE_FUNC...) does not generate exception if object is not a function: Calling seEval() with a function (the SE_FUNC flag) will return False but will not generate an exception and will not call the seAttErrorFunc or sePrintErrorFunc. [Details]

• string slice() function is not accepting zero parameters: String.prototype.slice() will report an error if it is passed no parameters. [Details]

• C++ compilation errors in selink.h if JSE_LINK options is not defined: If compiling a C++ file, with JSE_LINK not defined in jseopt.h, the compiler will warn of mis-matched extern "C" directives. [Details]

• SE_SI_DEPTH wrong for global code and for first function: SE_SI_DEPTH was wrong. Outside of any function ought to be depth 0, in the first function depth 1, etc. Instead, both outside and the first function were 0. [Details]

• If interpreting very long text lines, // comments may extend over multiple lines: If interpreting seEval(...SE_TEXTSE...) where any line of the raw text string is very long (usually many hundreds of characters), and if within the line there is an end-of-line comments (//), that comment may wrongly extend until the end of the buffer. [Details]

• Documentation incorrect about lifetime of seGetInternalString(): The documentation for seGetInternalString() states that the returned pointer is valid as long as the sestring is valid. That statement is incorrect. [Details]

• Function.prototype.apply() not accepting null for thisObj parameter: Function.prototype.apply() should accept null or undefined as the first parameter, using the global object for these cases. Instead an error message is generated. [Details]

 Errata

   ISDK/C 4.40e

• 5-character variables names incorrect if either of last two characters is '$': In many cases, internal representation of variable names will be incorrect if the string is 4 or 5 characters long and either of the last two characters are '$'. For example, the names "book" and "book$" would conflict and both represent the same variable. [Details]

• setting array length to 0 does not remove all indexed properties: Setting the length property of an Array instance to zero does not remove the properties, although it does set the length to 0. [Details]

• string slice() function is not accepting zero parameters: String.prototype.slice() will report an error if it is passed no parameters. [Details]

• If interpreting very long text lines, // comments may extend over multiple lines: If interpreting jseInterpret(...SourceTrext...) where any line of the raw text string is very long (usually many hundreds of characters), and if within the line there is an end-of-line comments (//), that comment may wrongly extend until the end of the buffer. [Details]

• Documentation incorrect about lifetime of jseGetInternalString(): The documentation for jseGetInternalString() states that the returned pointer is valid as long as the jseString is valid. That statement is incorrect. [Details]

• Function.prototype.apply() not accepting null for thisObj parameter: Function.prototype.apply() should accept null or undefined as the first parameter, using the global object for these cases. Instead an error message is generated. [Details]

 Errata

   ISDK/C 4.30f

• setting array length to 0 does not remove all indexed properties: Setting the length property of an Array instance to zero does not remove the properties, although it does set the length to 0. [Details]

• string slice() function is not accepting zero parameters: String.prototype.slice() will report an error if it is passed no parameters. [Details]

• Documentation incorrect about lifetime of jseGetInternalString(): The documentation for jseGetInternalString() states that the returned pointer is valid as long as the jseString is valid. That statement is incorrect. [Details]

 Errata

   ISDK/Java 4.30f

No new Java errata.