Jan 13, 2003 In This Issue What's new in the lab   ISDK/C 5.00e Errata   ISDK/C 4.40e Errata   ISDK/C 4.30f Errata   ISDK/Java 5.00e 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.

What's developing in Dr. Scripter's laboratory The weather has been firigidly cold here in New England, and so everyone in Dr. Scripter's labs has been keeping their bunsen burners on high as we work to improve the ScriptEase ISDKs. Our next version 5 release (expected in February) will contain solutions to the most common needs that have been expressed by you, our customers. Our R&D continues to be guided by the needs of our customers. It's important that we get your feedback about how we're doing and on what you need for the future. If any of the following items are of special importance to you, if you want to work with a prerelease of any of these items, or if we're leaving something out that you feel is important, then let us know at the Nombas Support Site. Here's what's cooking in Dr. Scripter's labs: Workshop/IDE - Version 2.0 of the ScriptEase Workshop will include Linux - A native Linux version of Workshop will be available, in addition to the Windows version Debugger optimizations - Better performance on the most common debugger operations Enhancements - Miscellaneous enhancements to the editor and IDE shell Performance - A script engine can never be too fast... Faster compilation - Compilation time is reduced Java class rewrite - Most of the core-engine Java classes are being rewritten to run much faster while using less memory Faster globals - The global-variable caching algorithms are being improved for faster access to global variables Libraries - A new library and enhancements to old libraries: Multiple Inheritance - The Multiple Inheritance Object, sample, and source, allow a script class to inherit the properties and behaviors of multiple base classes SEDBC for devices - The SEDBC library has been updated to work with the Oracle Lite database, and so SEDBC is available for PalmOS and WinCE systems Buffer Object comparisons - .equal() and .compare() methods have been added for instances of the Buffer Object Threads - We're testing and developing tools for better overall performance of large multi-threaded environments ServALot - This new sample let's us develop, test, and demonstrate recommended methods for supporting many simultaneous script threads Shared Objects - Helper functions are being added to support sharing of writeable data between script threads (in addition to seShareReadObject which is already supported) Semaphore support - Routines for simple script-based semaphores Miscellaneous - Tools to make improve your ISDK experience Unix build simplification - The make process for all Unix build is being streamlined Compiler validation - Compilation modes are being added for a higher level of compile-time script validation Low-memory testing - More-strenuous testing of low-memory situations Have a question about how to use ScriptEase:ISDK? Let Dr. Scripter know at the Nombas Support Site

 Errata

   ISDK/C 5.00e

• object-members passed as parameters to functions passed incorrectly: When a script passes an object member to a function, the function may receive the wrong parameter. [Details]

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

• allocation error in Unicode version of EvalBox demo: Memory corruption can occur if a string with newlines is written to the output window in Unicode versions of the EvalBox demo. [Details]

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

• Blob.put() loses existing settings for Buffer object: If Blob.put() is called to alter an exsting buffer, then a new buffer is created that loses all non-default information of the old buffer. [Details]

• non-floating-point version of sprintf functions using %x or %X may overwrite memory: If JSE_FLOATING_POINT is not defined (i.e. integer only), and %x or %X is used in the formatting string of any in any of the sprintf functions (e.g. se_vsprintf, sprintf_sechar, etc...), then memory may be overwritten at the end of the string buffer. [Details]

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

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

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

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

• seInitializeObject() helper function may not free object reference: 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]

• compilation errors for vxWorks and EPOC min-memory options: vxWorks and Symbian compiler errors when using JSE_MIN_MEMORY or the defaults asociated with JSE_MIN_MEMORY (!JSE_INLINES, SEASSERT_TINY_VERSION). [Details]

• script functions in shared objects are not locking all data: When a script function is being created as a shared object via seShareReadObject(), not all of its constants, strings, and varname are being locked. [Details]

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

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

• In Unicode builds, size of Buffer and BLOb objects is miscalculated: When building with JSE_UNICODE, the size of Buffer and BLOb objects is being doubled erroneously. [Details]

• Allocation error during compilation may leave some identifiers locked: If memory allocation fails during compilation, it is possible for local identifiers to remain locked or not immediately freed. [Details]

• array sort return invalid when array.length==1: If array.length==1, then array.sort() will return undefined. [Details]

• RegExp.$x and RegExp.lastParen not overwriting previous results with "undefined": sePutXXX is often not returning true on member creation. [Details]

• Typo in seEval() errata: An earlier 5.00e errata mistakenly placed a semi-colon at the end of an if clause. [Details]

• Bug in seIsFunc() or seFunctionAsText() if out-of-memory: If an out-of-memory condition occurs while caling seIsFunc() or seFunctionAsText(), then invalid memory may be referenced and a possible crash. [Details]

• seEnd() terminating an seEval(...SE_FUNC|SE_START...) asserts: Using seEnd() to terminate an seEval using the SE_FUNC option (and SE_START obviously) will cause asserts to trigger. [Details]

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

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

 Errata

   ISDK/C 4.40e

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

• jsePutString() 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]

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

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

• array sort return invalid when array.length==1: If array.length==1, then array.sort() will return undefined. [Details]

• SEDBC Database methods assume an open database: Some methods of the Database object assume that the .connect() method succeeded. If .connect() did not succeed then these methods may crash. [Details]

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

• function.protoype.constructor does not exist for all objects: Script functions, which may be called with the new operator, do not automatically have a prototype.constructor property as documented in many books on javascript. [Details]

 Errata

   ISDK/C 4.30f

• jsePutString() 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]

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

• array sort return invalid when array.length==1: If array.length==1, then array.sort() will return undefined. [Details]

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

 Errata

   ISDK/Java 5.00e

• RegExp.$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]

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

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

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

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