July 25, 2003 In This Issue SE:ISDK/C 5.01 released   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.

SE:ISDK 5.01 released Version 5.01 of SE:ISDK/C and SE:ISDK/Java has just been released. In addition to including fixes for all known 5.00 errata, version 5.01 includes: minor but useful enhancements to the API version 2 of the workshop and debugger new ways to save memory 5.00 users can learn more about 5.01 differences in What's new in 5.01 Should you move to 5.01? In addition to 5.01 improvement, we have added many more test setups for this 5.01 release, especially under the many Unix options. This means that we have isolated and worked around more quirks of the various systems; the more test situations we execute, the more we are likely to have encountered all of the possible bugs. For these is reason, (and the many 5.01 improvements) we would recommend planning a move to 5.01. All of your 5.00 code should work directly in 5.01 with very few exceptions as noted in What's new in 5.01 - Coding Changes. When you reach the point in your development/release cycle where you would have upgraded to a next 5.00 errata release, then you should instead plan on moving to 5.01 (we do not expect to release a 5.00g version). To receive your SE:ISDK/C 5.01a upgrades visit 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

• Socket() should return null on error: If a call to Socket() fails it should return null (as documented). Currently it is always returning an object. [Details]

• SEObjectWrapper has too many contexts; may be NULL: The SEObjectWrapper class, used for auto-wrapping C++ classes, defines two fields to hold the current context. They are not both updated together and one may be NULL when needed. This may cause a crash if the NULL value is used. [Details]

• seBrowserCreateEvent, in browser framework, always makes an undefined event: The seBrowserCreateEvent() function, for creating HTML browser events if using our browser framework, is ignoring the specified event text and always creating an undefined event. [Details]

• Function constructor may fail if dynamic global object overrides getters and putters: If the function constructor is called to make an anonymous function, and if the global object is dynamic and the getters and putters do not accept "anonymous" as a real variable, then no function is created. [Details]

• global VariableObject (activation) is not adjusted if global object changes: If the VariableObject is the same as the global object (i.e. in global scope) and the global object is changed the variable object retains its old value. [Details]

• conversion of strings to numeric sestrings may make non-unique identifiers: When string identifiers are converted to sestrings (the internal representation of all identifiers), some strings may be wrongly treated as if they were integer indices and may produce non-unique internal identifiers. [Details]

• Invalid conversion of strings to number on PalmOS when strings ends in decimal point: On the PalmOS, a string ending in a decimal point is not recognized as a valid number. [Details]

• semicolon required after assignment of function literals: An error may be generate after a script line initiating a function literal but not ending with a semicolon. [Details]

• when converting numbers to strings, rounding will not occur in some locales: In locales that use a comma to separate fractional parts of floating-point numbers (e.g. 3,145). JSE_NUMTOSTRING_ROUNDING will not round. [Details]

• system can become corrupted if number of objects in use is greater than MARK_STACK_SIZE: If the number of objects in use is greater than MARK_STACK_SIZE (defined in call.h) then memory may become corrupted. [Details]

 Errata

   ISDK/C 4.40f

• when converting numbers to strings, rounding will not occur in some locales: In locales that use a comma to separate fractional parts of floating-point numbers (e.g. 3,145). JSE_NUMTOSTRING_ROUNDING will not round. [Details]

• system can become corrupted if number of objects in use is greater than MARK_STACK_SIZE: If the number of objects in use is greater than MARK_STACK_SIZE (defined in call.h) then memory may become corrupted. [Details]

 Errata

   ISDK/C 4.30g

• when converting numbers to strings, rounding will not occur in some locales: In locales that use a comma to separate fractional parts of floating-point numbers (e.g. 3,145). JSE_NUMTOSTRING_ROUNDING will not round. [Details]

 Errata

   ISDK/Java 5.00f

• system can become corrupted if number of objects in use is greater than MARK_STACK_SIZE: If the number of objects in use is greater than MARK_STACK_SIZE (defined in Call.jh) then memory may become corrupted. [Details]