Merge branch 'release/v.10.7.1' into develop

Author: kosh04

Makefile

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

configure-alt

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

doc/CHANGES

@@ -7147,3 +7147,36 @@ Dec 6, 2009
 
 10.7.0 version 10.6.5 released as stable release January 2016.
 
+
+10.7.1 
+    GMT - offset now includes a potential daylight savings bias, when
+    daylight savings time is active on Windows and Unix-like OSs.
+
+    Like on UNIX the last field in the 'now' function shows similar to UNIX 
+    more info about usage of daylight savings time. In older Windows versions 
+    the daylight savings bias was shown all year.
+
+    'set' with multiple args leaked memory under certain conditions.
+
+    New not yet documented (history) returnst list of call history
+
+    Thanks to Sergio Durigan Junior for contributing changes and makefiles
+    for kFreeBSD. Debian GNU/kFreeBSD is a general purpose operating system, 
+    an official Debian GNU distribution using the kernel of FreeBSD instead 
+    of the Linux kernel. 
+
+    Fixed bug in 'search' and 'seek' with 'read-line' on some platforms.
+    Stream and raw handle file position went out of sink. 
+
+    'mat' with a scalar second argument was broken on 64-bit when scalar
+    was not a float.
+
+    fixed a problem in -- ++ when passing a 'nil' not contents of a 
+    symbol
+
+    symbol length extended from 255 to 1023 characters 
+    (1022 when using the hash function). Creating symbols
+    using a hash functor will now throw an error message
+    when the symbol is too long. The 'contect' and 'sys'
+    functions already threw an error message.
+

doc/CodePatterns.html

@@ -92,8 +92,8 @@
 
 <center>
 <h1 class="title">Code Patterns in newLISP<font size="-1">&#174;</font>
-</h1>Version 2015 July 11<sup>th</sup><br/>
-<a href="http://newlisp.org">newLISP</a> v.10.6.4
+</h1>Version 2015 July 11th<sup>rd</sup><br/>
+<a href="http://newlisp.org">newLISP</a> v.10.6.2
 </center>
 
 <br/><br/><br/>
@@ -282,7 +282,7 @@ <h1 class="title">Code Patterns in newLISP<font size="-1">&#174;</font>
   <li>Simple versus extended FFI interface</li>
   <li>A shared library in C</li>
   <li>Compile on Unix</li>
-  <li>Compile a DLL on MS Windows</li>
+  <li>Compile a DLL on Win32</li>
   <li>Importing data structures</li>
   <li>Memory management</li>
   <li>Unevenly aligned structures</li>
@@ -2277,7 +2277,7 @@ <h3>Closed transaction</h3>
 (net-send-udp "host.com" 1001 "Hello")
 </pre>
 
-<p>MS Windows and Unix's show different behavior when sending less or more bytes than specified on the receiving end.</p>
+<p>Win32 and Unix's show different behavior when sending less or more bytes than specified on the receiving end.</p>
 
 <h3>Multi-cast communications</h3>
 
@@ -2501,8 +2501,8 @@ <h2>17. Semaphores, shared memory</h2>
 #
 # usage of 'fork', 'wait-pid', 'semaphore' and 'share'
 
-(when (= ostype "Windows")
-    (println "this will not run on Windows OS")
+(when (= ostype "Win32")
+    (println "this will not run on Win32")
     (exit))
 
 (constant 'wait -1 'sig 1 'release 0)
@@ -3102,7 +3102,7 @@ <h3>Evaluating remotely</h3>
 result: (7 11 15 19 23)
 </pre>
 
-<p>When running Unix and using an <tt>inetd</tt> or <tt>xinetd</tt> configured newLISP server, the servers and programs can be run on just one CPU, replacing all IP numbers with <tt>"localhost"</tt> or the same local IP number. The <tt>indetd</tt> or <tt>xinetd</tt> daemon will then start 5 independent newLISP processes. On MS Windows 5 state-full newLISP servers could be started on different port numbers to accomplish the same.</p>
+<p>When running Unix and using an <tt>inetd</tt> or <tt>xinetd</tt> configured newLISP server, the servers and programs can be run on just one CPU, replacing all IP numbers with <tt>"localhost"</tt> or the same local IP number. The <tt>indetd</tt> or <tt>xinetd</tt> daemon will then start 5 independent newLISP processes. On Win32 5 state-full newLISP servers could be started on different port numbers to accomplish the same.</p>
 
 <p>Instead of collecting all results at once on the return of <tt>net-eval</tt>, a callback function can be used to receive and process results as they become available:</p>
 
@@ -3133,7 +3133,7 @@ <h3>Evaluating remotely</h3>
 ("192.168.1.104" 4711 23)
 </pre>
 
-<p>For testing on just one CPU, replace addresses with <tt>"localhost"</tt>; the Unix <tt>inetd</tt> or <tt>xinetd</tt> daemon will start a separate process for each connection made and all listening on port <tt>4711</tt>. When using a state-full server on the same MS Windows CPU specify a different port number for each server.</p>
+<p>For testing on just one CPU, replace addresses with <tt>"localhost"</tt>; the Unix <tt>inetd</tt> or <tt>xinetd</tt> daemon will start a separate process for each connection made and all listening on port <tt>4711</tt>. When using a state-full server on the same Win32 CPU specify a different port number for each server.</p>
 
 <h3>Setting up the 'net-eval' parameter structure</h3>
 
@@ -3378,7 +3378,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 MS Windows 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 Mac OS X).</p>
 
 <h3>Simple versus extended FFI interface</h3>
 
@@ -3408,7 +3408,7 @@ <h3>Simple versus extended FFI interface</h3>
 
 <h3>A shared library in C</h3>
 
-<p>This chapter shows how to compile and use libraries on both, MS Windows and Linux/Unix 
+<p>This chapter shows how to compile and use libraries on both, Win32 and Linux/Unix 
 platforms. We will compile a DLL and a Linux/Unix shared library from the following 'C' program.</p>
 
 
@@ -3451,7 +3451,7 @@ <h3>Compile on Unix</h3>
 gcc testlib.c -bundle -o testlib.dylib
 </pre>
 
-<p>The library <tt>testlib.so</tt> will be built with Linux/Unix default <tt>cdecl</tt> conventions. Importing the library is very similar on both Linux and MS Windows platforms, but on MS Windows the library can be found in the current directory. You may have to specify the full path or put the library in the library path of the os:</p>
+<p>The library <tt>testlib.so</tt> will be built with Linux/Unix default <tt>cdecl</tt> conventions. Importing the library is very similar on both Linux and Win32 platforms, but on Win32 the library can be found in the current directory. You may have to specify the full path or put the library in the library path of the os:</p>
 
 <pre>
 &gt; (import "/home/newlisp/testlib.so" "foo1")
@@ -3476,9 +3476,9 @@ <h3>Compile on Unix</h3>
 
 <p>Again, the number returned from <tt>foo2</tt> is the string address pointer and get-string can be used to access the string. When using get-string only character up to a zero byte are returned. When returning the addresses to binary buffers different techniques using unpack are used to access the information.</p>
 
-<h3>Compile a DLL on MS Windows</h3>
+<h3>Compile a DLL on Win32</h3>
 
-<p>DLLs on MS Windows can be made using the MinGW, Borland or CYGWIN compilers. This example shows, how to do it using the MinGW compiler.</p>
+<p>DLLs on Win32 can be made using the MinGW, Borland or CYGWIN compilers. This example shows, how to do it using the MinGW compiler.</p>
 
 <p>Compile it:</p>
 
@@ -3501,7 +3501,7 @@ <h3>Compile a DLL on MS Windows</h3>
 dllwrap testlib.o --def testlib.def -o testlib.dll -lws2_32
 </pre>
 
-<p>The library <tt>testlib.dll</tt> will be built with default MS Windows <tt>stdcall</tt> conventions. The following shows an interactive session, importing the library and using the functions:</p>
+<p>The library <tt>testlib.dll</tt> will be built with default Win32 <tt>stdcall</tt> conventions. The following shows an interactive session, importing the library and using the functions:</p>
 
 <pre>
 &gt; (import "testlib.dll" "foo1")
@@ -3800,10 +3800,10 @@ <h3>Registering callbacks in external libraries</h3>
 <a name="toc-24"></a>
 <h2>24. newLISP as a shared library</h2>
 
-<p>On all platforms, newLISP can be compiled as a shared library. On MS Windows, the library
+<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
 BSDs, the library is called <tt>newlisp.so</tt>. Makefiles are included in the source 
-distribution for most platforms. Only on MS Windows, the installer comes with a precompiled 
+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>
 
 <h3>Evaluating code in the shared library</h3>
@@ -3896,14 +3896,14 @@ <h3>Registering callbacks</h3>
 #!/usr/bin/newlisp
 
 ; path-name of the library depending on platform
-(set 'LIBRARY (if (= ostype "Windows") "newlisp.dll" "newlisp.dylib"))
+(set 'LIBRARY (if (= ostype "Win32") "newlisp.dll" "newlisp.dylib"))
 
 ; import functions from the newLISP shared library
 (import LIBRARY "newlispEvalStr")
 (import LIBRARY "newlispCallback")
 
 ; set calltype platform specific
-(set 'CALLTYPE (if (= ostype "Windows") "stdcall" "cdecl"))
+(set 'CALLTYPE (if (= ostype "Win32") "stdcall" "cdecl"))
 
 ; the callback function
 (define (callme p1 p2 p3 result)
@@ -3933,7 +3933,7 @@ <h3>Registering callbacks</h3>
 99999
 </pre>
 
-<p>Note that MS Windows  and many Unix flavors will look for <tt>newlisp.dll</tt> 
+<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> 
 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 

doc/INSTALL

@@ -70,15 +70,15 @@ and
 
 For a minumum install, only the executable file: newlisp (or newlisp.exe
 on Win32) needs to be moved to a directory in the executable path, i.e. 
-/usr/bin/newlisp on Unix. No other files are required. This installation
+/usr/local/bin/newlisp on Unix. No other files are required. This installation
 is recommended for ISPs and other server installations. If modules are
 installed the environment NEWLISPDIR should be defined to point to
 the modules parent directory. If NEWLISPDIR is not defined, newLISP sets
-it to /usr/share/newlisp during startup.
+it to /usr/local/share/newlisp during startup.
 
 To reduce an exisiting UNIX install to a minimum installation, remove all 
-files in /usr/share/newlisp and /usr/share/doc/newlisp and the executable 
-files /usr/bin/newlisp-edit and /usr/bin/newlispdoc.
+files in /usr/share/newlisp and /usr/local/share/doc/newlisp and the executable 
+files /usr/local/bin/newlisp-edit and /usr/local/bin/newlispdoc.
 
 On Mac OX X remove also the files under the Applications icon in the 
 Applications folder. On Windows remove all file except newlisp.exe in 
@@ -179,9 +179,7 @@ For questions and support for configure-alt, please contact:
      Ted Walther <ted@reactor-core.org>.
 
 Note thet configure-alt uses a version-numbered directory for the 
-installation. By default it also uses /usr/local instead of /usr
-as a prefix for the bin, man, share/newlisp and share/doc/newlisp
-directories.
+installation. 
 
 Avoid having installs from the standard 'configure' and alternate
 'configure-alt' script on the same machine!
@@ -277,10 +275,10 @@ or if installed with: make install_home
 
 To manually uninstall on Win32 remove all files in c:\Program files\newlisp
 
-On Mac OS X and other UNIX remove all files in /usr/share/newlisp and
-/usr/share/doc/newlisp and the executable files /usr/bin/newlisp,
-/usr/bin/newliso-edit and /usr/bin/newlispdoc. On Mac OX X also remove
-the newLISP icon in the Applications folder.
+On Mac OS X and other UNIX remove all files in /usr/local/share/newlisp and
+/usr/share/doc/newlisp and the executable files /usr/local/bin/newlisp,
+/usr/local/bin/newliso-edit and /usr/local/bin/newlispdoc. On Mac OX X also 
+remove the newLISP icon in the Applications folder.
 
 
 (8) RUNNING newLISP IN A SHELL OR CONSOLE WINDOW
@@ -292,7 +290,7 @@ On all platforms simply execute:
 
 On Win32 the execution path of newlisp.exe was added to the environment 
 during installation. On all other platforms the newlisp binary is in 
-/usr/bin/newlisp or when using the home install in $HOME/bin
+/usr/local/bin/newlisp or when using the home install in $HOME/bin
 where $HOME is the the home directory of the user taken from the environment
 variable HOME.
 
@@ -318,9 +316,9 @@ Java for OS X 10.7 Lion from here: http://support.apple.com/kb/DL1421
 
 By default the configure script uses the following install directories:
 
-/usr/bin/
-/usr/share/newlisp
-/usr/share/doc/newlisp
+/usr/local/bin/
+/usr/local/share/newlisp
+/usr/local/share/doc/newlisp
 
 As an alternative the configure-alt script can be used. Do a:
 

doc/TRU64BUILD

@@ -6,5 +6,5 @@ C compiler for the Alpha CPU:
 
 	make
 
-Please contact Peter van Eerten (peter AT gtk-server DOT org) for any 
+Please contact Peter van Eerten at peter@gtk-server.org for any 
 remaining questions.