Text only | Text with Images

newLISP Fan Club

Forum => newLISP newS => Topic started by: Lutz on March 16, 2010, 08:05:25 AM

Title: newLISP stable release 10.2.0
Post by: Lutz on March 16, 2010, 08:05:25 AM
Stable release v.10.2.0 introduces mutable objects in FOOP and other changes and additions.



Release notes: http://www.newlisp.org/downloads/newLISP-10.2-Release.html

Downloads: http://www.newlisp.org/index.cgi?page=Downloads
Title: Re: newLISP stable release 10.2.0
Post by: m35 on March 16, 2010, 10:14:49 AM
Congratulations Lutz. Looking good as always.



Few notes.
Quote from: "newLISP v.10.2 Release Notes"Before they would be reported as part of a define function callint it.

Quote from: "newLISP v.10.2 Release Notes"The probabilities calculated by prob-chi2 where to low for odd numbers of degrees of freedom.

Quote from: "newLISP v.10.2 Release Notes"The Chi2 values calculated by crit-chi2 where to low for odd numbers of


Quote from: "newLISP v.10.2 Release Notes"The editor syntax highlighting files in the util subdirectory of the source distribution have been updated]
Aww, no jEdit?  ;)
Title: Re: newLISP stable release 10.2.0
Post by: Lutz on March 16, 2010, 10:41:54 AM
Thanks for the corrections (now online), and isn't jEdit covered by your generator?



http://www.newlisp.org/code/jedit-newlisp-mode-generator.lsp.src.html



and linked from here:



http://www.newlisp.org/index.cgi?Code_Contributions
Title: Re: newLISP stable release 10.2.0
Post by: kks on March 17, 2010, 12:26:29 AM
Thanks Lutz and the community for all your contribution to newLISP!



After trying the new version, I've found some bugs??:



1. `setf` redefines `nil` if the place argument is a non-existing `assoc`:
Code Select

(setf (assoc 'a '()) '(a 1))
nil   # => (a 1)

   By the way, is it possible to implicitly add an assoc if it does not exist?:
Code Select

(setq L '((a 1)))  (setf (assoc 'b L) '(b 2))  L   # should return ((b 2) (a 1))
(setq L '((a 1)))  (setf (lookup 'b L) 2)  L   # should return ((b 2) (a 1))


2. It seems that `pretty-print`'s `str-fp-format` option also affects `string`:
Code Select

(pretty-print 80 " " "%1.3f")
(string 1.2)   # => "1.200" instead of "1.2"
Title: Re: newLISP stable release 10.2.0
Post by: Lutz on March 17, 2010, 05:01:55 AM
Number 1. is a severe bug and I decided to retract all downloads of the new version 10.2.0, until this is fixed.



Number 2. is by design. Changing the default format in 'pretty-print' will affect all function using it, e.i. 'source' is affected too. For specific formatting use 'format'.
Text only | Text with Images