newLISP development release v.10.3.10

[Lutz]

Development v10.3.10 has more improvements in the extended FFI, much increased speed on read-line with file handles.



For files, release and changes notes see:

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

[tumble]

Thank you!

[alex]

I have the same problem, that HPW (see http://newlispfanclub.alh.net/forum/viewtopic.php?f=2&t=3669&p=18427&hilit=WS2_32.dll#p18427">//http://newlispfanclub.alh.net/forum/viewtopic.php?f=2&t=3669&p=18427&hilit=WS2_32.dll#p18427) with Windows2000 professional - error an starting newLISP: the procedure entry point freeaddinfo could not be located in the dinamic link library WS2_32.DLL.

[jopython]

Nice. When will this be announced as a stable release?

[HPW]

I can confirm that the problem with WIN2K is back.

Just tested it with the old PC.

So new minimum requirement?

[Lutz]

Windows XP SP2 would be the new minimum requirement. For IPv6, Windows 7 would be minimum.

[Lutz]

There are new lisp.exe and a newlisp.dll here: http://www.newlisp.org/downloads/development/inprogress/">http://www.newlisp.org/downloads/develo ... nprogress/">http://www.newlisp.org/downloads/development/inprogress/



Both the .exe and the .dll are close to what will be released next week as 10.4.0. Perhaps Hans-Peter can give it a workout on different Windows versions?

[TedWalther]

I recently discovered the joyous use of unify+bind.  But the requirement that the variables have an upper-case first letter is annoying.  Can I have a version of unify that isn't prolog-specific?  Really, I just want something to bind a list of output values to a list of symbols.

[HPW]

OK,



WIN2K no more supported. Throws the known error.

Tested newlisp-tk, neobook and pdscript integration on XP Pro german SP3 without problems.

Testing on my WIN7 tablet will happen in the evening when back home.



Edit: Also WIN7 HomePremium(64bit) run without problems (32bit).



Hans-Peter

[Lutz]

Thanks, Hans-Peter.