newlispfanclub.alh.net

chi, (...) This function modifies its code during evaluation, so it runs indefinitely although there is no loop or recursion. (...) I wrote about it (...) Hello Kazimir, thank you very much for your explanation. Now I do understand! I think, you are right, that this is not normally possible via CL ...

Oops, perhaps I posted too fast! Suddenly I am not sure, if I interpreted the line in the release notes lambda functions (not lambda-macro) now allow for large or infinite running bodies without stack impact correctly! My Scheme example will crash the newLISP interpreter due to stack size. So perhap...

(...) I think CL and Scheme have no equivalent, since their functions are not just lambda lists, but results of evaluation of lambda lists. (...) At least Scheme ought to have this feature. To be a Scheme, the system has to support two important features: call/cc and tail recursion optimization . F...

From the new sqlite3.lsp test routines: try to drop table fruits via SQL injection attack ... no luck, table was safe against SQL injection. nice :-) I am glad, you like it! :-) I did some further testing (for memory leaks and 64-bit newLISP on OpenBSD and Mac OS X) and everything seems to be fine....

Thanks for the information Chi. You can just email or pm me the file sqlite3.lsp and I include it in the upcoming 10.0.6 development release. I sent you the extended file just a few moments before to the address you told me below. Thank you for considering to include my enhancement :-) I assume you...

Is it something like this, you are doing? (sql3:sql (format "select * from fruits where name = %s;" '("grapes"))) No, as this statement would be easily attackable via SQL injection attack. To avoid that, I use the sqlite3_bind_*() calls to bind a value to a host variable mentioned in the SQL statem...

Hello, I am interested in newLISP for some time now. I read in the forum and studied several code examples. Now I intend to use newLISP for a small project at work. For that, I have enhanced sqlite3.lsp a bit. I introduced the possibility of host variable bindings in the SQL statement of (sql3:sql) ...