5 ms·
> Development must be in LISP (typically Common Lisp, Clojure or Scheme) or English. Shouldn't that be and English? Further down: > All Entries must be coded
by chimeracoder 13y ago
> Development must be in LISP (typically Common Lisp, Clojure or Scheme) or English.
Shouldn't that be and English?
Further down:
> All Entries must be coded in LISP, typically this is Common Lisp, Clojure or Scheme. The determination of exactly what is a LISP is up to the discretion of the Judges. Haskell, Erlang and Smalltalk are not LISPs and will be disqualified.
> All Entries must be in English unless otherwise specified.
- brudgers 13y agoIt's Lisp, so writing about Lisp rather than in Lisp is potentially awesome, e.g. the ideas page lists "serious documentation projects" and "Maccarthy fanfic" as possible entry points. One of the distinguishing features of Lisp is that people write love songs to it.
- agilescale 13y agoQuality trolling. A++, would read again.
- gcr 13y agoBeing serious for a moment, quality documentation is an area where many lisps could use improvement.
- agilescale 13y agoYes, I've seen it Clojure, where the documentation is extensive, giving great coverage to its standard library... but still haves you reading the source and searching the web for examples after reading the description, especially when speaking about macros (so... does this receive a vector? Does it take its arguments as a list, or what? A mixture of both?) Racket goes full in the other direction, to a fault, even though it's much preferable.Racket's documentation is at times hard to wade through because it's so extensive. You have to scroll through the treatises and descriptions of options to find an example usage which will get you out quickly, but it's, for once, all there in the manual.
- gcr 13y agoHaha, I actually really like how Racket does it and consider them a great example to follow: - Racket's documentation is all on your local machine. Stuck without an Internet connection? F1, and you're searching your own documnetation index. - Everything -- everything -- is hypelinked. If you see a blue word in a code example, even the ones on the front page of http://racket-lang.org/ http://racket-lang.org/ , you can click on it and jump straight to that function's contract. But I agree, I wish there were a better way to jump straight to examples when you're looking at a specific function's documentation. It's confusing having the completely separate "Guide" and "Reference" halves of the documentation with no links between them.
- brudgers 13y agoMy gripe with Racket's documentation is that there is no middle ground between tutorials designed to showcase features rather than explain how Racket does and doesn't work and computer generated auto-docs. The tutorials are more geared toward selling the language to beginners, while the rest of the documentation is bereft of illustrative examples and editorial discussion.
- vadman 13y agoSurely you mean (++ A)?