??? 10, 2003 In This Issue SE:ISDK/C 5.00 upgrade   ISDK/C 5.00f Errata   ISDK/C 4.40f Errata   ISDK/C 4.30g Errata   ISDK/Java 5.00f 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.

QQQSE:ISDK 5.00f 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.   servalot - more than what we had last time? multiple inheritence - more than what we had last time? shared objects checking on typos - add more new svelte way-better java version servalot demo - more on this Linux support/version of workshop created SE_RELEASE_MODE for NDEBUG SE_GF_NOCALLBACKS SE_GF_CALL_HINT new jsemem_coookie and support options getponter and putpointer use real pointers 64bit handling our own regexp - unicode, etc, about 2/3 sizeof old one SE_RELEASE_BUILD is new, add to jseopt.h add SE_DEBUGPRINTF flag to jseopt.h add JSE_MEMDOUBLE_LIMIT to jseopt.h add SE_LOCK_PROTOTYPE_CACHE to jseopt.h add SE_FUNCTION_GLOBAL         qqqImprovements qqq 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. qqqLow-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. qqqFaster compilation - Scripts now compile faster. Typical scripts compile about 40% faster than in earlier releases. complete product, as described by the new included manual. NAME_KLUDGE enabled by default API Additions qqqseExistsDirect()/seExistsEx() - Check for whether a member exists without following prototype chain qqqseAssignEx() - Get the same SE_GF flags as seGetXXX and sePutXXX functions qqqJSE_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 qqqsePtrXXX() - sePtrXXX() helper methods (e.g. sePtrAddObj(), sePtrFromObj(), etc...) provide validation and inheritance of SE_OBJECT_DATA associated with C/C++ objects qqqseGetCallbacks() - Retrieve the dynamic C callbacks associated with an object qqqSE_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 qqqseObjectMemberCountDirect() - Retrieve number of object members without inheritance qqqJSE_TRACK_MEMUSE added as default - This provides complete descriptions for how memory is used when seGarbageCollect(...SE_COLLECT_AND_ANALYZE...) is called qqqSE:ISDK/Java now supports shared read-only objects, so multiple contexts can share shared a common set of global scripts and libraries New Platforms qqqDOS 16-bit - Large- and medium-memory models are supported for the MSVC 1.52 DOS 16-bit compiler qqqJ2ME-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.00f

• qqqqqseParseVar(...SE_VP_CREATE) is not making sub-properties of objects: seParseVar() with the SE_VP_CREATE flag should create any members that do not already exist, but this is not happening if the members are more than one level deep. [Details]

• qqqcompilation error if JSE_MUTLIPLE_GLOBAL==1 && JSE_COMPACT_LIBFUNCS==0: If jseopt.h defines JSE_MULTILE_GLOBAL but does not define JSE_COMPACT_LIBFUNCS, then there is a coompilation error. [Details]

• qqqNumber toPrecision() incorrect: Number.prototype.toPrecision(precision) is converting precision digits beyond the decimal, when it should be converting precision-1 digits. [Details]

• qqqNumber toExponential() incorrect if fractionDigits not specified: Number.prototype.toExponential(fractionDigits) is treating fractionDigits as 0 if unspecified. [Details]

• qqqdot-named parse not recognizing dynamic objects: Our dot-named parser, used in code such as 'function foo.goo() { }', was not fully recognizing dynamic objects in the name. [Details]

• qqqSE_NUM() cannot accept negative values: The manual implies that SE_NUM() can accept any integer, but it really takes only positive integers. [Details]

• qqqError in timezone calculation for Windows CE: Timezone offset from GMT is miscalculated in the Date object in Windows CE. [Details]

• qqqalmOS samples treat seInitialize() as a boolean: The PalmTst and EvalBox samples treat the return value from seInitialize() as a boolean, which is incorrect. [Details]

• qqqpotential 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.40f

• qqqqcomobj times miscalculate DST: In converting times between a script and a COM object, the daylight-savings time calculation may be off by one hour. [Details]

• qqqunknown preprocessor directive, if very long, crashes: If a preprocessor directive is very long (e.g. #OIJOJOIJOIQJOIJEWOJWOEOIJOIJ...) then a crash may occur while preparing an error message. [Details]

• qqqjsePutString() may overwrite previous results if JSE_C_EXTENSIONS is disabled: If compiling with JSE_C_EXTENSIONS 0, then when jsePutString() or similar calls are used to assign to a variable (especially via dynamic callbacsk as in the RegExp global object), existing string data may be overwritten. [Details]

• qqqstack corruption with long mode parameter to Clib.fopen() and Clib.freopen(): If the mode parameter to Clib.fopen() or Clib.freopen() parameter is longer than 18 characters, a stack buffer overflow will occur. [Details]

• qqqduring 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]

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

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

• qqqstring.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.30g

• qqqqcomobj times miscalculate DST: In converting times between a script and a COM object, the daylight-savings time calculation may be off by one hour. [Details]

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

• qqqstring.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]

• qqqsedbc 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]

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

• qqqstring.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.00f

• qqqRegExp.$x and RegExp.lastParen not overwriting previous results with "undefined": When the results of a regular expression call should result in undefined for for RegExp.$1...RegExp.$9 or RegExp.lastParen, the results of the most-recent previous call are not over-written with undefined. [Details]

• qqqNumber toExponential() incorrect if fractionDigits not specified: Number.prototype.toExponential(fractionDigits) is treating fractionDigits as 0 if unspecified. [Details]

• qqqNumber toPrecision() incorrect: If an exception is generated during a call to the SE API, items may be left on the script stack. [Details]

• qqqdiscrepencies using delete on global variables: When delete is used on global variables that were not created with the var keyword, the variables are not being deleted or the wrong boolean is being returned. [Details]

• qqqstring replace, if no matches found, is not returning the initial string: If String.prototype.replace() is called and no replacement is made, then the original string should be returned. [Details]

• qqqFunction.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]

• qqqseEval(...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]