TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

CL21 and thoughts on a modern lisp

5 点作者 arturventura大约 10 年前

1 comment

wtbob大约 10 年前
I agree with you re. array and hash table literals. We already have list literals; adding arrays and hash tables would be great. Fortunately, they could be added with some simple read macrods; I suggest #[] and #{}.<p>By &#x27;slice,&#x27; I assume you mean Python-like slices, not Go-like slices (which are for our purposes adjustable arrays, which CL has); what&#x27;s wrong with (subseq array start end)?<p>Yes, string manipulation could be much better. I personally always define a STRCAT which is really just (concatenate &#x27;string …). I&#x27;m actually a bit excited by some of the interpolation ideas out there. I definitely don&#x27;t want to lose FORMAT though.<p>I actually like the pathnames API, but it could stand to be better-specified for the common Unix case.<p>Agreed on more batteries included.<p>I don&#x27;t mind packages (in fact, find them highly useful), but would like a standard system definition facility. What do you find lacking with respect to packages?<p>It definitely needs to default to either downcasing or case-preserving. Upcase is so ugly. Do note that character encoding appears to be a solved problem; the Lisps I use are quite comfortable with Unicode.