newlispfanclub.alh.net

Development release version 10.3.9 adds a new data structuring function to the extended FFI interface.

For files, release and changes notes see:
http://www.newlisp.org/downloads/development

Hello, Lutz.

A new function, struct is fine.

By the way, symbol 'struct is used at functions' example of bind and unify in User Manual and Reference v.10.3.9

and also at Destructuring nested lists in Code Patterns in newLISP


And I wish to add struxt at Importing libraries' table in User Manual and Reference

Maybe, when Maintenance Release.

Thanks,

Thanks Johu, all corrected now here:

http://www.newlisp.org/downloads/develo ... anual.html

and here:

http://www.newlisp.org/downloads/develo ... terns.html

no, unfortunately the problem is still there.
Opening Code Patterns and the Manual in any web browser and making a search in the page for "struct" as one word will show a number of uses in which "struct" is a var name, not a newlisp operator.

It's not worth it to list the conflicts here, and probably unnecessary to supply a patch - the search will highlight them all and the fix should be very quick.

Thanks, now we got them all:

http://www.newlisp.org/downloads/develo ... anual.html

I had not tested the latest dev-versions carefully, and today I installed 10.3.9 and noticed that DLL-calling from my neobook plugin and DLL-calling from pdScript enviroment is broken (Crashes).
Not sure where it throws the access violation.
I reverted back to last stable 10.3.3 and all works fine.

Unfourtunatly I had not stored the dev-installer from 10.3.4 to 10.3.8 so I am not sure which version did work correctly.

I try to further investigate.

Linking has changed, and has changed again in 10.3.10. I have put an .exe and .dll here:
http://www.newlisp.org/downloads/develo ... nprogress/

Do these work for you?

ps: the change happened in 10.3.8 in win32dll.c

Still throws an access violation error message (read access at xxxxx) at the end of my first initialisation call.
But it rans then and I can call further lisp-calls which works.
All initialisation seems to have happend. Rest of demo works then.

Strange.

How about now: http://www.newlisp.org/downloads/develo ... nprogress/

Great, works fine again in both enviroments.
;-)