Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Lutz

#1
newLISP newS / Re: Happy Birthday newLisp
December 13, 2021, 05:09:25 PM
Thanks!!!
#2
You can find a macOS executable here:

http://www.newlisp.org/downloads/development/inprogress/macOS/">http://www.newlisp.org/downloads/develo ... ess/macOS/">http://www.newlisp.org/downloads/development/inprogress/macOS/
#3
At the moment I only can compile on FreeBSD 12.2 (Intel CPU), OpenBSD 5.5 (amd64 CPU) and MacOS 11.2.2 (Intel).

No access to Windows or Linux at the moment. What do your need?
#4
This is fixed here: http://www.newlisp.org/downloads/development/inprogress/">http://www.newlisp.org/downloads/develo ... nprogress/">http://www.newlisp.org/downloads/development/inprogress/



Was a bug in 'char' when used by 'setf'.
#5
newLISP in the real world / Re: newlisp 10 changes
November 20, 2020, 07:52:42 AM
http://www.newlisp.org/downloads/newlisp-10.7.5/doc/CHANGES">http://www.newlisp.org/downloads/newlis ... oc/CHANGES">http://www.newlisp.org/downloads/newlisp-10.7.5/doc/CHANGES
#6
newLISP newS / Re: Stable Release newLISP v.10.7.5
November 11, 2020, 08:38:47 PM
This seems to be happening inside the PCRE regex library and only on Windows. Still researching this ...
#7
newLISP in the real world / Re: pow function problem
October 19, 2020, 08:24:17 AM
The newLISP function pow works like the Perl and Python function pow:



>>> pow(3, 0.33)
1.4369776521848516
>>> pow(-3, 0.33)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: negative number cannot be raised to a fractional power
>>>


All use the Standard C Library function pow(a,b) using double floats.
#8
Yes, some sites redirect from http to https. On Mac, Linux and other UNIX like system you could use:
(exec "curl 'https://www.amazon.com'")
Not sure if the curl utility is also available on Windows.



Or you could use the  library module from here: http://www.newlisp.org/code/curl.lsp">http://www.newlisp.org/code/curl.lsp



This module was contributed by a user a long time ago, have never used it myself.
#9
newLISP can be compiled without readline support by taking out: -DREADLINE from the compile line in the make file and take out: -lreadline and: -lncurses from the linkline in the make file.



Here is a new recompile without readline support:



http://www.newlisp.org/cgi-bin/newlisp">http://www.newlisp.org/cgi-bin/newlisp



compiled using: makefile_bsdLP64_utf8 and shouldn't complain about any library missing.



In case this still doesn't work, expand newlisp-10.7.5.tgz and recompile yourself on your server using:



make -f makefile_bsdLP64_utf8
#10
When NearlyFreeSpeech.NET Support contacted me, we had a longer email exchange. This is the solution I offered:



lutz mueller <lutz.email@gmail.com>

Apr 17, 2020, 1:05 PM

to [NearlyFreeSpeech.NET
Hi Jeff,

You can find a current executable compiled and tested on your server here: http://www.newlisp.org/cgi-bin/newlisp

[newlisp /home/public/cgi-bin]$ ./newlisp
newLISP v.10.7.5 64-bit on BSD IPv4/6 UTF-8 libffi, options: newlisp -h

>

Best regards - Lutz


There where relying on newlisp to be compiled by the FreeBSD organization web site. But FreeBSD organization did not have updated to v10.7.5.



My own scripts on NearlyFreeSpeech.NET all use:



#!/home/public/cgi-bin/newlisp



in the .cgi files. You could just download:



http://www.newlisp.org/cgi-bin/newlisp">http://www.newlisp.org/cgi-bin/newlisp



and do the same.
#11
newLISP in the real world / Re: Timing function problem
September 20, 2019, 09:58:50 AM
Over time envrironment and stack memory gets fragmented by certain functions. The error forces a total low level freeing and reallocation of this memory. There is nothing we can do about it without slowing down everywhere, but it is a rare enough problem. Until now, I have never seen this before.
#12
newLISP in the real world / Re: Timing function problem
September 20, 2019, 08:09:03 AM
Yes, using your definition of 'merge', time is increasing on my system too.


> ./merge-time
2837.097
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
3596.99
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
4144.72
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
4526.995
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
5021.806
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
5475.793
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
5927.577
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
6196.546
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
6451.934
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
6576.566
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
8244.489
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
10133.406
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
7734.864
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
7595.829
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
9027.866
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
7656.296
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
7687.444
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
7974.064
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
8514.397000000001
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
8105.182
(598 576460752303423488 418 3 0 2048 0 10878 10705 1411)
~>

Also printing (sys-info) and you can see, there is no increase in stack levels or lisp cells between the calls to merge. I guess the answer is in stack and memory management of the underlying OS.


(dotimes (i 20)
(println (time (merge (sequence 1 500) (sequence 1 200) <) 500))
(println (sys-info)))
#13
newLISP in the real world / Re: Timing function problem
September 20, 2019, 07:05:06 AM
On my system: MacBook (Retina, 12-inch, Early 2016), macOS Mojave v10.14.6

it looks different:



newLISP v.10.7.5 64-bit on OSX IPv4/6 UTF-8 libffi, options: newlisp -h

> (define (merge lstA lstB op) (sort (append lstA lstB) op))
(lambda (lstA lstB op) (sort (append lstA lstB) op))
> (time (merge (sequence 1 500) (sequence 1 200) <) 500)
2260.89
> (time (merge (sequence 1 500) (sequence 1 200) <) 500)
2276.979
> (time (merge (sequence 1 500) (sequence 1 200) <) 500)
2238.431
> (time (merge (sequence 1 500) (sequence 1 200) <) 500)
2217.015
> (time (merge (sequence 1 500) (sequence 1 200) <) 500)
2238.752
> (time (merge (sequence 1 500) (sequence 1 200) <) 500)
2239.723
> (time (merge (sequence 1 500) (sequence 1 200) <) 500)
2217.198
>


It is going up and down in an oscillating manner.
#14
Yes, if you go directly to the download directory:



http://www.newlisp.org/downloads/">http://www.newlisp.org/downloads/



you find SHA1.txt text files containing check-sums in all sub-directories. The SHA1.txt for the newlisp-10.7.5.tgz package has been added a few minutes ago.
#15
Thanks Johu. Updated here:



http://www.newlisp.org/newlisp_manual-jp.html">http://www.newlisp.org/newlisp_manual-jp.html

http://www.newlisp.org/CodePatterns-jp.html">http://www.newlisp.org/CodePatterns-jp.html



Links can also be found on the documentaion page:



http://www.newlisp.org/index.cgi?Documentation">http://www.newlisp.org/index.cgi?Documentation