clus-data
clus-data copied to clipboard
phoe
Data for Common Lisp UltraSpec - http://phoe.tymoon.eu/clus/
This is a post that lists people who might want to contribute to CLUS in the future. If you want yourself added/removed, let me know. @krrrcks Kamil Ziemian loke from...
``` 01:16 possible relevant: https://github.com/inters/geneva#open-geneva and https://github.com/eugeneia/maxpc#maxpc the former uses the latter to parse a markdown-like language, in case you want to see an involved example (grammar.lisp) ```
> https://github.com/can3p/ansi-spec - this one fully parses the spec, > although with errors > > https://github.com/can3p/dpANS-parser - this one > fails to parse full spec but correctly parses one of...
``` 11:34 < beach> The Common Lisp HyperSpec is not great with links and such. 11:35 < beach> Frequently, the link goes to the glossary, and then there is no...
As we know, accessor description in CLHS is often missleading, using accessor term exchangable with function (see slot-value function in CLHS). I consider this to be suboptimal approach. I propose...
sorry if you ain't takin this kind of complaint but the notes in with-accessors (ch7 objects), which you have copied from the clhs, have symbol-macrolet bindings like (variable-name () (accessor-name...
https://www.hexstreamsoft.com/articles/notes-tips-standard-common-lisp-symbols/ I got this link and I need to check this out someday.
https://github.com/UltraSpec is the future target for housing all UltraSpec data.
https://github.com/Hexstream/common-lisp-format-reference Unlicensed, and therefore free for incorporating in the CLUS.