newLISP v.10.7.0 Stable Release

Started by Lutz, January 21, 2016, 09:11:41 AM

Previous topic - Next topic


Stable release v.10.7.0 adds functionality to existing functions, adds a new function and fixes bugs.

Release Notes:"> ... lease.html">


Thanks to everybody for their contributions and suggestions.

Ps: on Mac OS X this is the last release for the PPC CPU architecture, discontinued in 2005/6


Hello Lutz,

Thanks for the ongoing development. Getting better and better.

Also thanks for the spererate UTF-8 version's of the windows-bineries on the download-page

I updated my neobook plugin-zip with the new 10.7 Dll.



On the downloads page, I noticed that the Ubuntu packages are wrongly named:
Quote UBUNTU Debian installer newLISP v.10.7.0 for UBUNTU on i386

    UBUNTU Debian installer newLISP v.10.7.0 for UBUNTU on i386 UTF-8 enabled

though being for amd64 rather than i386.


Hello, Lutz.

I finished translartions of manuals.




There are in!1450">here.

and maybe

line 24222 in newlisp_manual v10.7.0
Quotesyntax all random functions called subsequenly like


syntax all random functions called subsequently like



Many thanks, Johu and Ralph. Everything is updated.


Thanks Lutz! I'm glad to see that updates and development still goes on =)

Newlisp makes me enjoy programming again.


Incidentally, the "UBUNTU on amd64 UTF-8 enabled" package installs nicely on Debian 8 (Jessie) as well, and probably the non-UTF-8 version does as well.

However, the zlib.lsp module needs an update to insert a path option
"/lib/x86_64-linux-gnu/" ; Debian 8, 64bit
That path option is also for Ubuntu 14.04, although there is the additional link "/usr/lib/x86_64-linux-gnu/" remnant from 12.04. I don't have a 64bit 12.04 available, so I can't (re-)confirm that the "/usr" prefix is needed for 12.04.

Note that both Ubuntu and Debian (with multi-arch installed) sport a  /lib/i386-linux-gnu/ library as well, so the 64bit path must be tested before that path. All in all, it becomes
(set 'files '(
    "/lib/x86_64-linux-gnu/" ; Ubunto 14.04 64bit, & Debian 8 64bit
    "/usr/lib/x86_64-linux-gnu/" ; Ubuntu 12.04 LTS 64bit
    "/lib/i386-linux-gnu/" ; Ubuntu 13.04
    "/usr/lib/" ; Linux, BSD, Solaris
    "/usr/lib/" ; OpenBSD 4.6
    "/usr/lib64/" ; for 64Bit CentOS 6 Linux
    "/usr/lib/libz.dylib" ; Mac OSX / Darwin
    "libz1.dll" ; MS Windows

I haven't checked all other modules.


so the 64bit path must be tested before that path.">sbobet777


Title of">// is

newLISP v.1.7.0 Release Notes...

At bottom there is

- development version 1.64

- guiserver.jar version 1.65 (probably wrong, too),


Besides this: Thanks for the ongoing work!


Hello Lutz,

I have a question.

About now function,

Linux version or newLISP in web
> (now 0 -2)


but, Windows version newLISP v.10.7.0
> (now 0 -2)


and Windows version newLISP v.10.6.2
> (now 0 -2)


In this connection, the time zone offset in minutes of Japan is 540.

Did only Windows version change?



It is incorrectly adjusting for daylight bias in 10.7.0 on Windows. This will be set back to previous 10.6.2 behavior in a future version.

The intend was to make values compatible between Unix and Windows during daylight savings time. But it breaks when outside of daylight savings time. The assumption was, that the daylight bias is only reported when daylight savings is active, which is not true at least on Windows. Unfortunately the whole daylight savings behavior is inconsistent even between different Unix flavors.


I understand.

Thank you for the detailed explanation.


Hello Lutz,">Windows API GetTimeZoneInformation's return value is
Return-value Description

   0   Daylight saving time is not used in the current time zone, because there are no transition dates or automatic adjustment for daylight saving time is disabled.

   1   The system is operating in the range covered by the StandardDate member of the TIME_ZONE_INFORMATION structure.

   2   The system is operating in the range covered by the DaylightDate member of the TIME_ZONE_INFORMATION structure.

Therefore, it may be used for (now -1) on MS Windows, though daylight bias in minutes. And it seems like Linux/Unix.

Or when the return value is 2, it may be able to adjust (now -2) for daylight bias.



Thanks Johu, for better testing, I will come back to this mid March when daylight savings time starts in the US.


... time zone offset in the 'now' function now switching fine between standard and daylight savings time on Windows:"> ... l.html#now">">