- bug-fixes for new reference modes and 'setf'
- 'setf' now works on string references too
- reviewed Code Patterns and Useres Manual for v.10.0
for files CHANGES and v10.0 Release notes see:
http://www.newlisp.org/downloads/development
development release newLISP v.9.9.4
Neat! Noticed this in the previous version btw during 'make install_home' on linux, still in this one:
Code: Select all
install: cannot stat `modules/mysql.lsp': No such file or directory
make: [install_home] Error 1 (ignored)
Get your Objective newLISP groove on.
I was looking at the latest release notes, which prompted me to check the manual for 'read-expr'. I don't have a problem with the function per se; it is a handy one to have. However, when I looked at 'eval-string' and saw the two functions both take a string parameter, and both definitions use str-source not expression. I wondered why you didn't choose the name 'read-string'. That would make it consistent naming with 'eval-string'. Plus when I see 'read-expr', my first inclination is that the function is going to be reading an S-expression and doing something. If I'm not mistaken, doesn't 'read-expr' choke on expressions?[/i]
...it is better to first strive for clarity and correctness and to make programs efficient only if really needed.
"Getting Started with Erlang" version 5.6.2
"Getting Started with Erlang" version 5.6.2
'read-expr' reads only one expression from a string than stops, while 'eval-string' reads the whole string. 'read-expr' scans and translates one expression until it is finished, but does not evaluate. It only checks that the expression is well formed. The focus therefore is on expression not on string.