4 ms·
Some notes based on my (brief) experience toying with Common Lisp: * Why hasn't anyone made a more eye-frendly version of the Common Lisp Hyper Spec ? Having g
by znpy 10y ago
Some notes based on my (brief) experience toying with Common Lisp:
* Why hasn't anyone made a more eye-frendly version of the Common Lisp Hyper Spec ? Having good, easily-browsable documentation is a core-problem.
* The relation between the various native data-types were quite unclear to me.
* dealing with the external world was quite a mess. Many project/libraries implementing only half of something and then got abandoned.
* some libraries had a compatibility matrix... with common lisp implementations. that seemed weird to me.
- TeMPOraL 10y ago> Why hasn't anyone made a more eye-frendly version of the Common Lisp Hyper Spec ? Having good, easily-browsable documentation is a core-problem. A friend of mine is working on that as we speak. The CLUS, or Common Lisp UltraSpec: https://phoe.tymoon.eu/clus/doku.php https://phoe.tymoon.eu/clus/doku.php That said, CLHS isn't bad - it's lightweight, available off-line, and on-line you can pretty much always find what you're looking for by searching for "clhs [term of interest]". > some libraries had a compatibility matrix... with common lisp implementations. that seemed weird to me. Common Lisp has a pretty good standard, but it's a bit old so it didn't predict some things we're currently using, and also left some other things to the implementers. So some features are only available via vendor-specific extensions, which makes it necessary for some projects - especially compatibility libraries - to be tested across plethora of CL implementations. The flip side is that you have a few commercial and open source implementations to choose from, which is valuable if your project can exploit strengths of a particular one.
- db48x 10y agoAh, this is something to follow. Sadly it doesn't seem to have a permuted symbol index, which is what I really love about the CLHS. Still, I suppose they have to start somewhere.
- sedachv 10y ago> Why hasn't anyone made a more eye-frendly version of the Common Lisp Hyper Spec I mostly access the HyperSpec using Erik Naggum's hyperspec.el while programming in Emacs, configured to bring up Lynx. A lot of other people probably do something similar, so there has not been much interest in adding CSS.
- aidenn0 10y ago> Why hasn't anyone made a more eye-frendly version of the Common Lisp Hyper Spec ? Having good, easily-browsable documentation is a core-problem. The hyperspec is only distributed under a restrictive license. The TeX sources of actual last draft of the ANSI specification is public domain though. This means that someone would need to retranslate from the TeX sources rather than modifying the hyperspec.
- aidenn0 10y ago> The relation between the various native data-types were quite unclear to me. I'm not sure what was unclear. Perhaps you cuold give a specific example of something that confused you?
- phoe-krk 10y ago> * The relation between the various native data-types were quite unclear to me. http://sellout.github.io/media/CL-type-hierarchy.png http://sellout.github.io/media/CL-type-hierarchy.png
- znpy 10y ago> http://sellout.github.io/media/CL-type-hierarchy.png http://sellout.github.io/media/CL-type-hierarchy.png Indeed. Take for example base-char, which is a type. base-char derives (derives? the straight solid black line is not represented in the legend) from character, which is a built-in class (according to legend). So is character a class too? does base-char encapsulate a character or something like it? Before anyone comment, please keep in mind that this comment doesn't want to start a flame or be critical in any way.
- lispm 10y agohttps://pbs.twimg.com/media/C56V5kyWMAAi0DD.jpg https://pbs.twimg.com/media/C56V5kyWMAAi0DD.jpg Blue are CLOS classes. Brown are structure classes. Red are built-in classes. Black are types without any classes. This is the hierarchy for types in LispWorks, packages CLOS and CL.
- db48x 10y agoTypes in Common Lisp may or may not be represented by classes (all classes are types, not all types are classes). In this case, character is indeed a class, while base-char is not. It's definitely true to say that base-char is a subtype of character, in that some characters are also base-chars, while others are not. (The spec defines that there are at least 96 standard characters, all of which are of type standard-char, and thus also of type base-char. Implementations may add others. Interestingly, the spec doesn't define how those characters are encoded; of course most modern implementations use some variant of Unicode.) Some examples: (typep #\A 'base-char) ⇒ true (typep #\A 'standard-char) ⇒ true (typep #\A 'extended-char) ⇒ false (typep #\A 'character) ⇒ true (typep #\𝀽 'base-char) ⇒ false (typep #\𝀽 'extended-char) ⇒ true etc.