Yay, I'm glad we've come to a conclusion on this, this way I can update Dragonfly to support existing versions of newLISP and this upcoming one.Lutz wrote:Yes, 'term' absolutely works and it is short too and a beautiful word! 'term' will be introduced in the coming release version 10.2.0 (or any development version before it).
Will the caller function be in the next release too?
How about modifying newLISP to include a deprecated map of functions?Ps: a quick check in the standard modules shows, that gmp.lsp, mysql.lsp, odbc.lsp, postgres.lsp sqlite.lsp and stat.lsp are affected. So perhaps we keep both for some time and let 'name' die slowly through deprecation; having the reference entry for 'name' saying: "please use 'term' instead", but keep it working for some time.
The evaluator would work like this:
- Attempt to resolve symbol
- If fails, attempt to resolve symbol in deprecated map
- If found, use that old version and print an warning message to stderr saying that the function is deprecated and will be removed in a future version
For example, in the next release, someone could write this code with no problem:
Code: Select all
(set 'name 5)
Code: Select all
(name 'Foo:bar)