5 ms·
I don't like the case-sensitive symbols. Nor do I like the implicit quote on symbols...it doesn't make much sense to me but that might because there aren't many
by omouse 20y ago
I don't like the case-sensitive symbols. Nor do I like the implicit quote on symbols...it doesn't make much sense to me but that might because there aren't many good code samples on the site.
Is it too much to ask for a nice looking website with lots of good code samples? And a reference link for all the functions that work in the language would be nice.
As much as some people dislike newLISP, it at least has a good clear/concise website: http://newlisp.org/ http://newlisp.org/ The purpose is clearly stated, and right away you know on what it can run and where to look for comparisons to other Lisps.
Not much of a competitor to Arc in my opinion. But pg, please show us some more Arc code :P
- Goladus 20y agoI'm no lisper but it seems to me that the implicit quote and the resulting need to use square brackets to delineate lists would make it more difficult to write macros.
- omouse 20y agoIt depends on how he's defined the implicit quote syntax. You could make it so it doesn't have any effect in a def-macro call or something but that increases complexity just a tiny bit for a feature that doesn't do much for the developer. Off-topic-ish: The square brackets are kind of neat but not for that purpose. If instead he allowed the interchange of square brackets and parenthesis, i.e. (+ 2 [ 3 2]), that would be neat and useful...it would allow someone to differentiate between nested lists slightly. And of course, it's easier to click [ instead of Shift+[ to get ( :p
- shiro 20y agoI suspect the need of special syntax for list construction came from the introduction of currying. If you want currying you need to know arity of procedures, so you lose variable arity procedures such as 'list'.