Aug 14, 2002 In This Issue SE:ISDK/C 5.00 upgrade   ISDK/C 5.00c 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.00d upgrade now available, with new features and new platforms SE:ISDK/C version 5.00d errata release is now available. In addition to fixing all known 5.00c errata items, this 5.00d release includes: New Platforms J2ME - SE:ISDK/Java is now available for J2ME. This is downloadable now for the RIM/Blackberry J2ME platform. Let us know if you need a different J2ME platforms supported. PalmOS - The 5.00 API makes the results smaller and faster than ever. VxWorks - SE:ISDK/C for VxWorks/Tornado is now available. Epoc32 - The coding is complete for supporting the needs of the EPOC platforms, although the complete test and download bundle is not yet available. Contact us if you need the Epoc code and makefiles. Mac OS X / Darwin - SE:ISDK/C has been updated for Apple's newest platform. New Features Debugger for Java - The workshop debugger now supports Java and J2ME platforms. Low-memory exception handling - All memory allocation routines now filter through a common point to recover (through GC) from low-memory situations. If post-GC allocation still fails then, in almost all cases, a proper ecmascript memory exception is generated and propagated up through the call stack. (I.E., no more aborts through MustMalloc.) The new API memory functions are seGCMalloc(), seGCRealloc(), seGCStrdup(), seGCStrndup(), and seGCFree(). SE_PS_USEPOINTER, SE_PS_BORROWPOINTER - These can be used to make sePutString() more efficient by preventing extra allocation and copying of strings. seShareReadObject() - This new API function allows multiple threads to share objects. The most common expected use is to initialize a global set of libraries and scripts, and then have multiple threads share that initial object, thus saving memory and startup time. (This is independent from fibers which can be very efficient but are expected to cooperatively share the processor.) XML - This first release of our small XML library allows XML data to be mapped to an intuitive script format. #link libraries and SE:RTEx - All of the standard #link libraries have now been ported to the 5.00 API. These include SEDBC, SOCKET, and COMOBJ libraries. The SE:RTEx kit is also now available to allow anyone to write these or other libraries as #link extensions to the ScriptEase engine. Upgrade Now All 5.00 users are strongly encouraged to upgrade to 5.00d, because of the number of errata items addressed, and the further extensive testing we've added since the 5.00c release (a complete regression test now takes nearly 24 hours). To receive your SE:ISDK/C 5.00d upgrades send email to 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.00c

• Compilation errors if JSE_CONDITIONAL_COMPILE not defined: If jseopt.h does not #define JSE_CONDITIONAL_COMPILE then there are compilation problems. [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]

• 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. In release builds, this would result in a slight memory leak. [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]

• seEval() with SE_REPORT_ERRORS is not clearing the error flag: seEval() with SE_REPORT_ERRORS not correctly leaving the context with no error after it is reported. [Details]

• errors with SE_OPT_DEBUGGER: SE_OPT_DEBUGGER does not work correctly. [Details]

• #include statement inserts null-character into source stream: When processing the #include "filespec" directive within seEval() or sePrecompile(), a null character will be written at the end of filespec. This is a problem if the original source is from SE_TEXT and that original text must not be overwritten (must be re-used or is in read-only memory). [Details]

• sePutNumber(NaN) where NaN!=jseNaN are not recognized: If your code gives the interpreter any representation of NaN that is not bitwise identical to jseNaN, then it may not be recognized as NaN during internal math operations. [Details]

• Win32 compilation errors if JSE_WIN_ALL defined: Win32 builds on se500 with the JSE_WIN_ALL libraries turned on have compile errors. [Details]

• JSE_MIN_MEMORY builds truncate SE_SERVICES,SE_VALUE pointer: Putting a pointer to SE_SERVICES,SE_VALUE in a min-mem build causes the pointer to be truncated to 16 bits. [Details]

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

• decodeURI is missing from standard ECMA libraries: The standard ECMAScript function "decodeURI" has been wrongly names "decodedURI". [Details]

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

• seDestroyContext cannot be called within seEval: seDestroyContext cannot be called from within seEval. [Details]

• seIsFunc() error for non-objects: seIsFunc generates an error if called on a non-object. [Details]

• fields of call structure may not be initialized: Some fields of the call structure may not be initialized. [Details]

• invalid getArrayLength() results if no .length member: On some systems, getArrayLength() returns 2+ billion for the length on objects that do not have a LENGTH member. [Details]

• SElib.interpret() with no flags turns on all flags: Not passing the flags argument to SElib.interpret can turn on all the flags rather than turning on none. [Details]

• Unix SElib.directory() function is broken: Unix SElib.directory() function is broken. [Details]

• On Unix, some library functions mis-convert NaN and omitted arguments: Certain Unix library functions improperly handle a NaN argument (and an omitted argument). [Details]

• array.slice(), string.indexOf(), and string.slice() errors on Unix and PalmOS: array.slice(), string.indexOf(), and string.slice() don't work properly on Unix in certain cases. This applies to the palm as well. [Details]

• some unix data parameters can be off: Some data parameters in unix are off, especially those referring to DST and offset from GMT. [Details]

 Errata

   ISDK/C 4.40e

• parseInt() treating characters ":;<=>?@" as digits 3 through 9: When evaluating a string, parseInt() is treating the characters from ":" to "@" (\x3A to \x40) as the digits 3 through 9. [Details]

• variables on stack may be uninitialized during garbage collection: Temporary variables pushed on the stack may be uninitialized when the garbage collector executes. This may lead to corrupt script variables. [Details]

• fields of call structure and api_string structure may not be initialized: Some fields of the call and api_string_block structures may not be initialized. [Details]

 Errata

   ISDK/C 4.30f

• parseInt() treating characters ":;<=>?@" as digits 3 through 9: When evaluating a string, parseInt() is treating the characters from ":" to "@" (\x3A to \x40) as the digits 3 through 9. [Details]

• func.prototype undefined if #define JSE_AUTO_OBJECT 0: If compiling with the JSE_AUTO_OBJECT options off (i.e. #define JSE_AUTO_OBJECT 0) a script cannot extend the prototype member of a script function. [Details]

 Errata

   ISDK/Java 4.30f

No new Java errata.