Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Kumar

Pages1
#1
Whither newLISP? /
February 04, 2003, 12:16:52 PM
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.
#2
Whither newLISP? /
February 04, 2003, 12:06:26 PM
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 suppose that's hard to get ?



Now, how could I have a look at the mySQL interface from my Windos-box ?

SQL from Lisp, and forget about C++ ... I think that would be a sure winner !   My guess, you have to win a 'niche' in which you are at least slightly superior, and then push hard through it. And newLisp is superior in simplicity and availability. Speed is quite good, and the speed bottle neck in database programming might be the SQL engine, not the outer envelope / interface. At least, for some applications.



Quiz:  Whats a commmon-lisp programmer ?

<Someone who every other week checks out how 'setf' behaves. >
#3
Whither newLISP? / copy-list and other improvements
February 03, 2003, 06:33:53 PM
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 list. I know you can write it down simply in terms of slice or select.

(define (copy-list L)

  (slice L 0 (length L)))



But it would be nice to have it hard-coded.



Another first-look improvement would be to be able to type multiline expressions at the main tk window, (error 'missing parentheses' in mine).  More so since there is no integrated editor. Would that be so hard ?



Thanks and congratulations.
#4
Anything else we might add? /
February 03, 2003, 02:14:17 PM
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 there for a long time, and left everyone satisfied.



On other more specialised functions, I'd rather encourage the creation and sharing of specialized libraries. -after all, thats what Lisp escells at -modular, reusable code - just paraphrasing Paul Graham !

Still , I think any Lisp should be proudly strong on list-managing functions !
Pages1