Merge branch 'release/v.10.7.3'

Author: kosh04

Makefile

@@ -24,8 +24,8 @@
 # and file LOCALIZATION for details
 #
 
-VERSION = 10.7.1
-INT_VERSION = 10701
+VERSION = 10.7.3
+INT_VERSION = 10703
 
 default: makefile_build
 	make -f makefile_build

configure-alt

@@ -1,7 +1,7 @@
 #!/bin/sh
 
 PACKAGE=newlisp
-VERSION=10.7.1
+VERSION=10.7.3
 
 rm -f config.h makefile_build makefile_install
 

doc/CHANGES

@@ -7145,10 +7145,10 @@ Dec 6, 2009
     A illegal symbol when trying to create a context could crash the system,
     when referenced again after the error message.
 
-10.7.0 version 10.6.5 released as stable release January 2016.
+10.7.0 verson 10.6.5 released as stable release January 2016.
 
 
-10.7.1 
+10.7.1 stable release Jan 21st 2017
     GMT - offset now includes a potential daylight savings bias, when
     daylight savings time is active on Windows and Unix-like OSs.
 
@@ -7180,3 +7180,45 @@ Dec 6, 2009
     when the symbol is too long. The 'contect' and 'sys'
     functions already threw an error message.
 
+10.7.2
+   Fixing out-of-sink of file positions when mixing 'search' and 'seek' 
+   with 'read-line' on IO-streams introduced a new errror making
+   the newlisp-10.x.x/examples/upload.cgi script fail.
+
+10.7.3
+   Supress loading of startup init.lsp when -h option is present. Before
+   only the -n and -x options supressed init.lsp.
+
+   Change in modules/gsl.lsp to make it work on locales using comma separator.
+
+   Ability to use 'open', 'rename-file', 'delete-file', 'make-dir' and 
+   'remove-dir' with UTF16 filenames in UTF8 versions on Windows when
+   using the UTF8 version of newLISP. The functions 'file-info', 'file?', 
+   'change-dir' and 'dir? already worked on UTF16 filenames when using the UTF8 
+   version of newLISP on Windows.
+
+   Thanks to Michael Sabin who started the work a few years back writing the 
+   win-path.c file with functions translating between UTF8 and UTF16. 
+
+   When using the UTF8 version of newLISP on Windows in a command shell, that
+   command shell program also should be able to handle/display UTF8 (not UTF16).
+   On Windows and Linux the Java based frontend newLISP-GS handles UTF8.
+   On Mac OS the terminal program handles UTF8.
+
+   Fixed a wrong 'symbol protected message' when a protected symbol is 
+   part of a nested espression, but not a symbol with its content to be 
+   modified.
+
+   New modules/postscript.lsp changes description of ps:drawto.
+
+   Fixed flushing problem on 'print' to stdout on Mac OS and other BSDs.
+
+   '(read-key true)' with the 'true' parameter is now non-blocking.
+
+   (trim str) on some strings containing 0's would overrun memory and 0's
+   where not trimmed from the left. All character <= 32 (space) should
+   be trimmed from the left and right ends of the string buffer. When the 
+   entire string is valid ASCII or UTF-8 with no 0s, ‘trim’ behaves 
+   like in older versions.
+
+

doc/CodePatterns.html

@@ -92,8 +92,8 @@
 
 <center>
 <h1 class="title">Code Patterns in newLISP<font size="-1">&#174;</font>
-</h1>Version 2015 July 11th<sup>rd</sup><br/>
-<a href="http://newlisp.org">newLISP</a> v.10.6.2
+</h1>Version 2017 Augusr 11<sup>th</sup><br/>
+<a href="http://newlisp.org">newLISP</a> v.10.7.3
 </center>
 
 <br/><br/><br/>
@@ -2335,7 +2335,12 @@ <h3>Using <tt>exec</tt></h3>
 <p>This method is only suited for short exchanges, executing one command and receiving the output.</p>
 
 <pre>
-(exec "ls *.c") → ("." ".." "util.c" "example.ls")
+> (exec "ls *.c")
+("newlisp.c" "nl-debug.c" "nl-filesys.c" "nl-import.c" "nl-list.c" "nl-liststr.c" 
+ "nl-math.c" "nl-matrix.c" "nl-sock.c" "nl-string.c" "nl-symbol.c" "nl-utf8.c" "nl-web.c" 
+ "nl-xml-json.c" "pcre-chartables.c" "pcre.c" "unix-lib.c" "win-dll.c" "win-path.c" 
+ "win-util.c")
+> 
 </pre>
 
 <p>The <tt>exec</tt> function opens a process pipe for the Unix command-line utility <tt>ls</tt> and collects each line of STDOUT into a list of strings.</p>
@@ -3010,7 +3015,7 @@ <h3>Stateless server with inetd</h3>
 
 <p>After configuring <tt>inetd</tt> or <tt>xinetd</tt> either process must be restarted to re-read the configuration files. This can be accomplished by sending the Unix <tt>HUP</tt> signal to either the <tt>inetd</tt> or <tt>xinetd</tt> process using the Unix <tt>kill</tt> or Unix <tt>nohup</tt> utility.</p>
 
-<p>On Mac OS X the <tt>launchd</tt> facility can be used in a similar fashion. The newLISP source distribution contains the file <tt>org.newlisp.newlisp.plist</tt> in the <tt>util/</tt> directory. This file can be used to launch newlisp server during OS boot time as a persistent server.</p>
+<p>On macOS the <tt>launchd</tt> facility can be used in a similar fashion. The newLISP source distribution contains the file <tt>org.newlisp.newlisp.plist</tt> in the <tt>util/</tt> directory. This file can be used to launch newlisp server during OS boot time as a persistent server.</p>
 
 <h3>Test the server with telnet</h3>
 
@@ -3378,7 +3383,7 @@ <h3>Media types in HTTP modes</h3>
 <a name="toc-23"></a>
 <h2>23. Extending newLISP</h2>
 
-<p>newLISP has an import function, which allows importing function from DLLs (Dynamic Link Libraries) on Win32 or shared libraries on Linux/Unix (ending in .so, ending in .dylib on Mac OS X).</p>
+<p>newLISP has an import function, which allows importing function from DLLs (Dynamic Link Libraries) on Win32 or shared libraries on Linux/Unix (ending in .so, ending in .dylib on macOS).</p>
 
 <h3>Simple versus extended FFI interface</h3>
 
@@ -3439,7 +3444,7 @@ <h3>A shared library in C</h3>
 
 <h3>Compile on Unix</h3>
 
-<p>On Mac OS X and Linux/Unix we can compile and link <tt>testlib.so</tt> in one step:</p>
+<p>On macOS and Linux/Unix we can compile and link <tt>testlib.so</tt> in one step:</p>
 
 <pre>
 gcc testlib.c -shared -o testlib.so
@@ -3700,7 +3705,7 @@ <h3>Extracting return values</h3>
 
 <h3>Writing library wrappers</h3>
 
-<p>Sometimes the simple version of newLISP's built-in import facility cannot be used with a library. This happens whenever a library does not strictly adhere to <tt>cdecl</tt> calling conventions expecting all parameters passed on the stack. E.g. when running Mac OS X on older PPC CPUs instead of Intel CPUs, the OpenGL libraries installed by default on Mac OS X cannot be used.</p>
+<p>Sometimes the simple version of newLISP's built-in import facility cannot be used with a library. This happens whenever a library does not strictly adhere to <tt>cdecl</tt> calling conventions expecting all parameters passed on the stack. E.g. when running macOS on older PPC CPUs instead of Intel CPUs, the OpenGL libraries installed by default on macOS cannot be used.</p>
 
 <p>Since newLISP version 10.4.0, the problem can be solved easiest using the newer extended syntax of <tt>import</tt>, which automatically resolves platform and architectural differences. On very small systems or whenever the needed <tt>libffi</tt> system library is not present on a platform, a special wrapper library can be built to translate <tt>cdecl</tt> conventions expected by newLISP into the calling conventions expected by the target library.</p>
 
@@ -3801,7 +3806,7 @@ <h3>Registering callbacks in external libraries</h3>
 <h2>24. newLISP as a shared library</h2>
 
 <p>On all platforms, newLISP can be compiled as a shared library. On Win32, the library
-is called <tt>newlisp.dll</tt>, on Mac OS X <tt>newlisp.dylib</tt> and on Linux and
+is called <tt>newlisp.dll</tt>, on macOS <tt>newlisp.dylib</tt> and on Linux and
 BSDs, the library is called <tt>newlisp.so</tt>. Makefiles are included in the source 
 distribution for most platforms. Only on Win32, the installer comes with a precompiled 
 <tt>newlisp.dll</tt> and will install it in the <tt>Program Files/newlisp/</tt> directory.</p>
@@ -3934,7 +3939,7 @@ <h3>Registering callbacks</h3>
 </pre>
 
 <p>Note that Win32  and many Unix flavors will look for <tt>newlisp.dll</tt> 
-in the system library path, but Mac OS X will look for <tt>newlisp.dylib</tt> 
+in the system library path, but macOS will look for <tt>newlisp.dylib</tt> 
 first in the current directory, if the full file path is not specified. The 
 program above can also be found as <tt>callback</tt> in the source distribution 
 in the <tt>newlisp-x.x.x/examples</tt> directory.</p>

doc/newLISP-10.7.1-Release.html

@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html>
+<head>
+<title>newLISP  v.1.7.3 Release Notes </title>
+
+<style type="text/css" media="screen">
+
+h1 {
+	font-family:Optima, Georgia, Times New Roman, Times, serif; 
+	font-size: 200%;
+	font-weight: 500;
+	color: #404040;
+	}
+
+h2, h3 {
+	font-family: Lucida Sans, Helvetica,  sans-serif;
+	color: #404040;
+	line-height: 120%;
+ 	}
+
+body, p {
+	font-family: Lucida Sans, Helvetica,  sans-serif;
+	color: #404040;
+	line-height: 120%;
+	font-size: 110%;
+	max-width: 900px;
+ 	}
+
+tt {
+	font-family: Courier;
+	color: #606060;
+	line-height: 120%;
+	}
+
+em {
+	font-family: Courier;
+	color: #606060;
+	}
+
+li {
+	margin-bottom: 15px;
+    }
+	
+
+</style>
+
+</head>
+
+<body>
+<h1>newLISP<font size=-1>&#174;</font> v.10.7.3 Development Release
+<font color="red" size="-1">2017-10-09</font></h1>
+
+<p>This development release fixes bugs and adds functionality.</p>
+<p>For newer macOS versions legacy Java 6 runtime has to be installed. 
+It can be downloaded from Apple 
+<a href="https://support.apple.com/kb/DL1572?locale=en_US">here</a>. 
+
+<h3>Bug fixes</h3>
+
+<p>Better handling of UTF-16 encoded filenames on MS Windows. 
+Filenames in newLISP UTF-8 versions should be given encoded in UTF-8 but 
+will be correctly encoded to UTF-16 format on Windows. When reading from 
+the Windows file system, they will be correctly translated to UTF-8.</p>
+
+<p>Fixed a wrong 'symbol protected message' when a protected symbol is
+part of a nested espression, but not a symbol with its content to be
+modified.</p>
+
+<p>Fixed a flushing problem on <tt>print</tt> to stdout on macOS and 
+other BSDs.</p>
+
+<p><tt>(trim str)</tt> on some strings containing <tt>0</tt>'s would overrun 
+memory and <tt>0</tt>'s where not trimmed from the left. All characters less 
+than space (32) should be trimmed from both ends of the string buffer. When the
+entire string is valid ASCII or UTF-8 with no <tt>0</tt>s, <tt>trim</tt> behaves
+like in older versions.</p>
+
+<h3>New Features</h3>
+
+<p>Supress loading of startup file <tt>init.lsp</tt> when <tt>-h</tt> option 
+is present. In older versions only the <tt>-n</tt> and <tt>-x</tt> options 
+supressed <tt>init.lsp</tt>.</p>
+
+<p><tt>(read-key true)</tt> with the <tt>true</tt> parameter is now 
+non-blocking.</p>
+
+<h3>Compatibility with previous versions</h3>
+<p>This version is compatible with the previous versions in the 10.7.x series.</p>
+
+<center>&part;</center>
+
+</body>
+</html>
+

doc/newLISP-10.7.3-Release.html

@@ -1,4 +1,4 @@
-.TH newlisp 1 "April 2014" "version 10.6.0" "Commandline Parameters"
+.TH newlisp 1 "May 2017" "version 10.7.2" "Commandline Parameters"
 .SH NAME
 newlisp \- lisp like programming language
 .SH SYNOPSIS