newLISP® v.10.3.2 Release Notes rev 2011-7-20

10.3.2 is a stable maintenance release with bug fixes and efficiency improvements. Except for a new way to encode unicode/UTF8 characters in a string and a change int the way xfer-event bytes sizes are reported, no new functionality has been added or changes have been made.

For the original 10.3.0 release notes see here.

Additions

• Quoted strings now can contain unicode characters encoded using \u.... , where .... are four hex digits e.g.: "\u03b1\u03b2\u3b3" for the Greek letters "αβγ" (aplha, beta, gamma). When reading the string, newLISP will translate it to UTF8 encoded characters on UTF8 enabled versions.

Other improvements

• Better error message on self-referential list changes.
• Improved error messages in implicit indexing.
• Recognize MBCS characters in MS Windows pathnames.
• Siginificant speedup in functions: filter, index, clean, exists and for-all
• Significant speedup on series when second argument is a function.
• Significant speedup on find-all when the third argument is used.
• Better memory management and speed improvements for map.
• A new version of json.lsp module now processes backslashed characters as of JSON spec (thanks Ted Walther).

Bug fixes

• Fix for filter, index, clean, exists and for-all when handling empty list elements ().
• inc, dec, ++ and -- did not check for missing parameters.
• The boolean parameter in dotree could cause a crash.
• Fix for a buffer overflow in interactive multi-line mode.
• A bug fix for timer when using recursively.
• An EOF error in read-line was not cleared and made all subsequent calls to read-line fail with nil.
• xfer-event now reports netto bytes sizes transferred. Before, accumulated bytes were reported. As one get-url, put-url or post-url request can contain several subrequests, the accumulated numbers were sometimes confusing. Now the sum of the numbers reported will always reflect the total size transferred. If an accumulated number is needed, it should be calculated in the xfer-event function.

Compatibility

The minimum Mac OS X version to run this release is Leopard 10.5. This release will not run on Mac OS X Tiger 10.4, but still can be compiled on this version using the default makefile_darwin_utf8 build script for Mac OS X.

All scripts running on version 10.3.0 also run on 10.3.2 without changes, except when xfer-event is used, reported xfer sizes are not accumulated.