Probably we more or less agree, but have different ways of expressing what we mean. Graham is good, but I think it's dangerous to rely too much on what he says. Just as an example, he seems to have a disdain for the loop macro that just isn't shared by the community at large, and if unduly under his influence one might neglect to use it even in situations where it's clearly the easiest and best solution. But (like Perl) there's room enough in Lisp for everyone, at least IMHO. :-)
One should be careful about relying on tail recursion being optimized in Common Lisp, too. The spec doesn't require it (unlike Scheme which does). I think most implementations will do it under certain but not all circumstances. For example, in the one I use, you need to have debug set below 3 in the code to be compiled. I don't have a good enough sense of history to speculate whether this is because of or the cause of Common Lispers being a lot more willing to iterate than Schemers.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
