newlispfanclub.alh.net

'let*' and 'letrec' are the same thing, they are just differently named in different LISPs. Scheme has both let* and letrec, and they are not the same thing. let* allows each expression to refer to variables defined above it. It guarantees that expressions will be evaluated in order. Common Lisp ha...

I believe you are using telepathy to transport your words to your keyboard? An expression like "and uses ideas abandoned years ago. " is not very smart... So, is it possible to implement the List Processing shootout entry correctly and efficiently in newLisp, so the comparison can be fair? I'm not ...

Actually I started criticism because of the name "newLisp". If it was some random language, I would not notice, but it tries to paint itself as a successor of Lisp, while in my eyes it does not qualify as a Lisp at all, and uses ideas abandoned years ago. Anyway, the problem with unfair benchmark is...

Who cares about 'cons' cells if you can solve programming problems without it. One concept less to learn, when learning the language. Who cares about 'garbage collection' if you can to automatic memory management a different more efficient way. What is the largest application written in newLisp? A ...

I'm indeed more a theoretician than a practician, although I aim at creating a practical product this time. It is 10 times younger than newLisp, but already works well and hosts its own compiler. Regarding newLisp, I'm afraid it is (from my point of view) broken beyond hope of repair. It could be im...

As I say......"A programming language is a mirror of the creator"... The source code is included...bring me the ultimate or bring me Kogut! I'm not sure if I understand you. Anyway, I'm afraid this forum is not appropriate for talking about other languages. I am happy to discuss Kogut, but it's off...

If you need bignum handling so much, why don't you create a 'C' library for newLISP with bignum.lsp interface file to import it and use it. It will not be returned by file-info, nor accepted by print, <, + etc. They are not extensible for user types; they have hardwired knowledge about builtin type...

Automatically throwing a system into bignum mode seems to be giving a false sense of security to those who haven't thought about the numerical side of their programming. Oh, really? I have a file of size of 10GB. newLisp's file-info function returns nil for it. Could this be fixed? For example Pyth...

I'm not complaining that the behavior is just different than in Scheme or Common Lisp. I'm complaining that it repeats past mistakes of old Lisps and old Perls which were later fixed, and that it's simply not useful in several cases. (3) Dynamic scoping Is not a 'bad idea' per se, it is just a diffe...

Icon passes by value. Not true: procedure change(l) l[1] := 10 end procedure main(args) local l l := [1,2,3] change(l) write(l[1]) end Result: 10 Furthermore, KSH, BASH, (...) ZSH I said that Unix shells are exceptions. They support no data structures except strings (and sometimes arrays). They are...

In fact, only C-pointers pass objects by reference and only Java/C++ know a kind of garbage collecting. Almost all interpreted languages pass 'objects' by value. Which scripting languages? Python, Ruby, Icon pass objects by reference. Perl passes them by reference when calling functions and makes a...

The name "newLISP" would suggest that it builds on old Lisp experience, but in fact it ignores Lisp history and uses rules which have been tried and rejected as bad ideas, like dynamic scoping by default. "Excepting symbols and built-in primitives, each object is referenced only once in the system a...