development release newLISP v.9.9.9

[Lutz]

newLISP house cleaning for v.10.0 continues



• changes and adjustments



file and changes notes: http://www.newlisp.org/downloads/development">http://www.newlisp.org/downloads/development

[cormullion]

newLISP house cleaning for v.10.0 continues

....

swapped parameters in 'write-line'

That's not house-cleaning - that's moving the door!



Please stop, Lutz, you're breaking my ... code. :)

[HPW]

From the newLISP-10.0-Release.html

The initialization file in either $HOME/.init.lsp or $USERPROFILE/.init.lsp or $DOCUMENT_ROOT/.init is loaded if it exists, else if $NEWLISPDIR/init.lsp exists, it is loaded.

I have a  question about the loading the init.lsp from the DLL flavour.



In the past the DLL always loads a init.lsp from the place where the DLL was loaded.

This seems no more the case.

Should it be this way now?

[Lutz]

The rules are now the same for the main executable as for the imported DLL. This way several .init.lsp (with the dot) files can exist for different users in their home directories. You always can overwrite these rules by predefining NEWLISPDIR at the os-level during os startup. Then only that directory will be searched for init.lsp (without the dot).

[itistoday]

newLISP house cleaning for v.10.0 continues

....

swapped parameters in 'write-line'

That's not house-cleaning - that's moving the door!



Please stop, Lutz, you're breaking my ... code. :)

Cormullion, I sympathize, but your code won't break if you read the changes and fix your code before upgrading.  If you want to stay on the bleeding edge all the time with these development releases then you're going to have to deal with constant changes.



One thing that I love about newLISP is that it's ... new.  It's fast, nimble, and prone to change, just like young people.  It reminds me of Apple in a lot of ways.  Like when Apple nixed the floppy drive and everyone called them crazy.  If I think of any other metaphors I'll let you know. ;)



I'd much rather have a newLISP that's constantly improving, and changes like standardizing syntax with the write-* functions helps towards that perfection.  Otherwise we'll get stuck with poorly thought-out ideas that remain fixed for the sake of compatibility.  That reminds me of what happened to M$ Windows and LISP.

[cormullion]

Don't worry - I'm just grumbling for fun... :)