Nov 13, 2002 In This Issue SE:ISDK/C 5.00 upgrade   ISDK/C 5.00d Errata   ISDK/C 4.40e Errata   ISDK/C 4.30f Errata   ISDK/Java 5.00d 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 5.00e upgrade now available SE:ISDK version 5.00e errata release is now available for C/C++ and Java & J2ME. In addition to fixing all known 5.00d errata items, this 5.00e release includes important improvements, API Additions, and support for new platforms. It's worth the upgrade. Improvements Lower memory use - For small-memory builds, sevars have been reduced by 1/3 and objects have been reduced by almost 1/2. Most of the memory used by large scripts is in sevars and objects, and so the overall reduction in memory use is significant. For example, a 32-bit min-memory build can now initialize the engine and all libraries in less than 10K RAM. Low-memory recovery - When memory is extremely limited, SE:ISDK/C 5.00e will take extreme measures (garbage collection, dumping of pools, reducing request sizes, and trying again) to recover. If all else fails an out-of-memory object is returned to all exception handlers (the engine or libraries cannot abort due to insufficient memory). The new MEMFAIL tester is included to automate testing of out-of-memory conditions. Faster compilation - Scripts now compile faster. Typical scripts compile about 40% faster than in earlier releases. Browser Library Updated - The browser library has been rewritten to be as small as possible, as fast as possible (especially on startup), and to comply with emerging browser expectations. By creating data only when first accessed, this new library loads up immediately and uses no more memory than necessary. Faster SE_DYNA_UNDEF objects - Dynamic objects created using the SE_DYNA_UNDEF flag (so most objects do not need lookups) are now nearly as fast as standard objects (about 1% performance loss on standard members). This makes a big difference in overall script performance when the global object has dynamic callbacks. Workshop/Debugger - The Workshop has been updated as a complete product, as described by the new included manual. API Additions seExistsDirect()/seExistsEx() - Check for whether a member exists without following prototype chain seAssignEx() - Get the same SE_GF flags as seGetXXX and sePutXXX functions JSE_LINE_CONTINUATION - This compile-time flag allows a backslash at the end of a line to mean that the string continues on the next line sePtrXXX() - sePtrXXX() helper methods (e.g. sePtrAddObj(), sePtrFromObj(), etc...) provide validation and inheritance of SE_OBJECT_DATA associated with C/C++ objects seGetCallbacks() - Retrieve the dynamic C callbacks associated with an object SE_GF_UNDEF_OBJ_OK - This flag for seGetObjectEx() prevents an exception from being generated if the object does not exist and so cannot be converted to an object seObjectMemberCountDirect() - Retrieve number of object members without inheritance JSE_TRACK_MEMUSE added as default - This provides complete descriptions for how memory is used when seGarbageCollect(...SE_COLLECT_AND_ANALYZE...) is called SE:ISDK/Java now supports shared read-only objects, so multiple contexts can share shared a common set of global scripts and libraries New Platforms DOS 16-bit - Large- and medium-memory models are supported for the MSVC 1.52 DOS 16-bit compiler J2ME-MIDP - A J2ME configured for MIDP is now available Upgrade Now This is a very robust release. All 5.00 users should upgrade to 5.00e. To receive your SE:ISDK/C 5.00e upgrades contact 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 5.00d

• Clib.system() does not return exit code on Solaris: Solaris Clib.system doesn't return exit code of child properly. [Details]

• very short variable names incorrect if character > 0x7f: If a variable name or identifier is 3 characters or less, and any of the characters is a value between 0x7f and 0xff (inclusive) (e.g. foo["\xb9"]) it will be converted incorrectly. [Details]

• string.split() incorrect if regular expression used as separator: String.prototype.split(separator) returns the wrong results when separator is a regular expression and does not match the first character of the string. [Details]

• dynamic get is not being called if hasProp callback is NULL: If an object has dynamic callbacks via seSetCallbacks, but does not implement a hasProp callback, then the get callback should be called to determine if the object has the given property. [Details]

• virtual-stack growth if retrieving values after an exception: If an exception is generated during a call to the SE API, items may be left on the script stack. [Details]

• sedbc bugs with long binary data: SEDBC can crash when reading from or writing to database columns representing any of the large binary data types. [Details]

• during script compilation peephole optimizer accesses invalid memory: The peephole optimizer can access invalid memory during script compilation. In rare circumstance this may cause a crash. [Details]

• default_this parameter ignored in seEval(...SE_CONSTRUCTOR...): Using the SE_CONSTRUCTOR option of seEval()ing a function, if you set a default_this in the params structure, it is ignored. [Details]

• Errors with extremely large Date values: Date values larger than the maximum allowable to new Date() can cause nearly-infinite loops. [Details]

• seCreateFiber reinitializes function libraries: seCreateFiber is reinitializing the function libraries. [Details]

• string.replace crashes or consumes all memory when replacing with null string: When using string.replace() to delete a character from a string, by replacing it with "", the call may crash or use too much memory. [Details]

• JSE_COMPACT_LIBFUNCS may crash while expanding used functions: Extensive testing shows that in a worst case, a crash may occur while expanding functions added with JSE_COMPACT_LIBFUNCS in effect. [Details]

• seGetAttribs may cause asser error, or return wrong value: seGetAttribs will not work correctly under certain circumstances. [Details]

• some objects made read-only with seShareReadObject() may never be freed: Some objects made read-sharable are not freed. [Details]

• JSE_COMPACT_LIBFUNCS not saving any memory: Date values larger than the maximum allowable to new Date() can cause nearly-infinite loops. [Details]

• seGetXXX() functions ignore dynamic object's hasProp when retrieving an object value: seGetXXX ignores a dynamic object's hasProp when trying to get an object member's value. [Details]

• sePutXXX() not returning TRUE as documented: sePutXXX is often not returning true on member creation. [Details]

• potential crash with arguments object when receiving many parameters: possible memory leak and/or crashes with arguments object in certain configurations. [Details]

 Errata

   ISDK/C 4.40e

• very short variable names incorrect if character > 0x7f: If a variable name or identifier is 3 characters or less, and any of the characters is a value between 0x7f and 0xff (inclusive) (e.g. foo["\xb9"]) it will be converted incorrectly. [Details]

• string.split() incorrect if regular expression used as separator: String.prototype.split(separator) returns the wrong results when separator is a regular expression and does not match the first character of the string. [Details]

• sedbc bugs with long binary data: SEDBC can crash when reading from or writing to database columns representing any of the large binary data types. [Details]

• during script compilation peephole optimizer accesses invalid memory: The peephole optimizer can access invalid memory during script compilation. In rare circumstance this may cause a crash. [Details]

• Errors with extremely large Date values: Date values larger than the maximum allowable to new Date() can cause nearly-infinite loops. [Details]

• invalid_regexp_instance.toString() crash: Calling the RegExp toString operator on an object that is not a valid RegExp instance will crash. [Details]

• string.replace crashes or consumes all memory when replacing with null string: When using string.replace() to delete a character from a string, by replacing it with "", the call may crash or use too much memory. [Details]

 Errata

   ISDK/C 4.30f

• useCache field of Call structure may not be initialized: The call->useCache field is not initialized for new levels of interpret. [Details]

• string.split() incorrect if regular expression used as separator: String.prototype.split(separator) returns the wrong results when separator is a regular expression and does not match the first character of the string. [Details]

• sedbc bugs with long binary data: SEDBC can crash when reading from or writing to database columns representing any of the large binary data types. [Details]

• invalid_regexp_instance.toString() crash: Calling the RegExp toString operator on an object that is not a valid RegExp instance will crash. [Details]

• string.replace crashes or consumes all memory when replacing with null string: When using string.replace() to delete a character from a string, by replacing it with "", the call may crash or use too much memory. [Details]

 Errata

   ISDK/Java 5.00d

• seCreateFiber reinitializes function libraries: seCreateFiber is reinitializing the function libraries, when they should be shared. [Details]

• Errors with extremely large Date values: Date values larger than the maximum allowable to new Date() can cause nearly-infinite loops. [Details]

• virtual-stack growth if retrieving values after an exception: If an exception is generated during a call to the SE API, items may be left on the script stack. [Details]

• dynamic get is not being called if SEHasPropCallback not implemented: If an object has dynamic callbacks via seSetCallbacks, but does not implement a hasProp callback, then the get callback should be called to determine if the object has the given property. [Details]

• string.split() incorrect if regular expression used as separator: String.prototype.split(separator) returns the wrong results when separator is a regular expression and does not match the first character of the string. [Details]

• seDestroyContext cannot be called within seEval: seDestroyContext was written with the assumption that no seEvals would be currently executing inside it when called. This assumption is wrong.. [Details]

• crash with eval() in nested function: Crash in eval() inside nested function calls. [Details]

• STACK_INFO crashes within nested seEval(): Using STACK_INFO within nested interprets can crash. [Details]

• stock objects passed to seEval with SE.FUNC will not work: When calling seEval() with stock objects and the SE.FUNC flag (e.g. seEval(...,SE.THIS,...,SE.FUNC,...)) the stock object will not be recognized. [Details]

• assert() or memory leak from seEval(...SE_FUNC..) if run-time error in script function: When using seEval() to call a function, errors in the function could trigger assertions. [Details]

• SE_NEW_GLOBALS flag for seEval() doesn't work: Specifying a new global in calls to seEval using the seEval parameters structure can fail to take effect. [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]

• 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. [Details]