Also in abstraction level, newLisp is a crack. So, fitted to a fast database engine, with good pattern-matching and language manipulating functions, its got to be... Data mining ? No, data exploding !
end do.
Search found 4 matches
- Tue Feb 04, 2003 8:16 pm
- Forum: Whither newLISP?
- Topic: copy-list and other improvements
- Replies: 4
- Views: 7463
- Tue Feb 04, 2003 8:06 pm
- Forum: Whither newLISP?
- Topic: copy-list and other improvements
- Replies: 4
- Views: 7463
So thats all ! simple So I may assume theres no need for setf either. Everything can be either 'set' or 'replaced'. In the edit window, it would be phantastic to be able to evaluate a single expression, by 'dragging' it (the same you do with cut&paste), or placing the cursor just after it... but I s...
- Tue Feb 04, 2003 2:33 am
- Forum: Whither newLISP?
- Topic: copy-list and other improvements
- Replies: 4
- Views: 7463
copy-list and other improvements
Hi I'm new to the forum, so bear with me.... I think this a wonderful lisp interpreter. True to the original lisp spirits. I miss the useful copy-list function, especially since there are quite a few 'destructive' functions, for instance sort, that often must rely on previous copying of original lis...
- Mon Feb 03, 2003 10:14 pm
- Forum: Anything else we might add?
- Topic: setq
- Replies: 11
- Views: 16985
I like subseq as a substring/sublist substitute. Severals reasons: -Its already in Common Lisp, it reminds you better about what it does. it reminds also where does it come from, i.e. substring/sublist Functions' names should be 'selfexplanatory', as far as possible. As for setq, I agree it has been...