mgr's weblog

mgr's weblog https://blog.matroid.org:443/ mgr's weblog archives for category Lisp en Pushing the logic to the data – Running Dydra's revisioning algorithm within RonDB's data nodes https://blog.matroid.org:443/display/95 Tue, 23 Jul 2024 12:03:26 GMT <p>July 23, 2024. News release.</p> <p>Datagraph GmbH, Berlin. – We are working on ways to distribute not just data storage, but also query processing. Dydra, our graph database, can use a RonDB NDB Cluster as storage backend for large repositories of billions of triples. We discussed with Mikael Ronström of RonDB and Hopsworks how we could improve our use of RonDB and its advanced features, and proposed to investigate how extensions to the RonDB interpreted code language could make it possible to move our revision visibility test from the core of our graph database system to an implementation that runs in RonDB's data nodes. That would distribute the processing load and reduce the transferred data.</p> <p><em>That is, we could push the test to the data instead of having to pull all data to the test.</em> </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/95">whole article.</A> </I> </P> uLisp on M5Stack (ESP32):<br/> support for the LED matrix of the M5Atom Matrix https://blog.matroid.org:443/display/92 Thu, 09 Dec 2021 11:30:34 GMT <p>I got a good friend join the uLisp fun and he extended my support for the single LED of the M5Atom Lite to <a href="https://github.com/m-g-r/ulisp-esp-m5stack/commit/e7ab18e0039904afb52b4ba0e42a3220a0e2ff2c">support the 25 LEDs of the M5Atom Matrix</a>. The single LED has just the same interface as the LED matrix, as expected.</p> <p>Thanks, <a href="https://github.com/cycle-uber-space">Thorsten</a>! </p> <p>It has a nice <a href="https://github.com/m-g-r/ulisp-esp-m5stack/commit/04be8d0978587f50bd916c72924399b0305f5eb8">backwards compatible interface</a>, the functions atomled (for C) and atom-led (for Lisp) just have a new second argument <tt>index</tt>, which is <tt>0</tt> by default, for the first— or, in case of the M5Atom Lite, only—LED.</p> <p>The C function you can call like this:</p> <p><div class="code"> <pre>atomled(0x00ff00); /&ast; or: &ast;/ atomled(0x00ff00, 23);</pre></div></p> <p>where 0x00ff00 describes a RGB color in 32 bits.</p> <p>And the uLisp function you can call very similarly like this:</p> <p><div class="code"> <pre>(atom-led #xffff00) #| or: |# (atom-led #xffff00 23)</pre></div></p> <p>I have merged it to my repository <a href="https://github.com/m-g-r/ulisp-esp-m5stack">ulisp-esp-m5stack</a> already. Activate the new flag <tt>#define enable_m5atom_led_matrix</tt> in addition to <tt>#define enable_m5atom_led</tt> to use the whole LED matrix of the M5Atom Matrix instead of just the first LED.</p> <p><br> See also <a href="https://blog.matroid.org:443/display/91"><span class="title">built-in LED of the M5Atom Lite</span></a>.</p><P><I>Read the <A HREF="https://blog.matroid.org:443/display/92">whole article.</A> </I> </P> uLisp on M5Stack (ESP32):<br/> built-in LED of the M5Atom Lite https://blog.matroid.org:443/display/91 Wed, 08 Dec 2021 18:33:12 GMT <p>I just published support of the M5Atom Lite LED at <a href="https://github.com/m-g-r/ulisp-esp-m5stack">ulisp-esp-m5stack</a>.</p> <p>There is a C function that you can call like this:</p> <p><div class="code"> <pre>atomled(0x00ff00);</pre></div></p> <p>where 0x00ff00 describes a RGB color in 32 bits.</p> <p>And a uLisp function that you can call very similarly like this:</p> <p><div class="code"> <pre>(atom-led #xffff00)</pre></div></p> <p>Activate <tt>#define enable_m5atom_led</tt> to get it. That will also automatically <tt>init_atomled();</tt> in <tt>setup()</tt> after booting the ESP32.</p> <p>I have actually tried the libraries FastLED (by Daniel Garcia, version 3.4.0), Easy Neopixels (by Evelyn MAsso, version 0.2.3), and NeoPixelBus (by Makuna, version 2.6.9) as well, but settled to use the library Adafruit NeoPixel (by Adafruit, version 1.10.0). It is small, doesn't have tons of bloat, works for me and has a nice interface that makes my implementation so tiny you would think it was almost no work.</p><P><I>Read the <A HREF="https://blog.matroid.org:443/display/91">whole article.</A> </I> </P> uLisp on M5Stack (ESP32):<br/> new version published https://blog.matroid.org:443/display/90 Mon, 06 Dec 2021 15:32:16 GMT <p>I got notified that I haven't updated <a href="https://github.com/m-g-r/ulisp-esp-m5stack">ulisp-esp-m5stack</a> at GitHub for quite a while. Sorry, for that. Over the last months I worked on a commercial project using uLisp and forgot to update the public repository. At least I have bumped ulisp-esp-m5stack to my version of it from May 13th, 2021 now.</p> <p>It is a—then—unpublished version of uLisp named 3.6b which contains a bug fix for a GC bug in with-output-to-string and a bug fix for lispstring, both authored by David Johnson-Davies who sent them to my via email for testing. Thanks a lot again! It seems they are also included in the <a href="https://github.com/technoblogy/ulisp-esp/commit/21c6fc3e0def61c1569f0d727a4a121aa2ce32cc">uLisp Version 3.6b that David published on 20th June 2021</a>.</p> <p>I know there David published a couple of new releases of uLisp in the meantime with many more interesting improvements but this is the version I am using since May together with a lot of changes by me which I hope to find time to release as well in the near future. </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/90">whole article.</A> </I> </P> uLisp on M5Stack (ESP32):<br/> controlling relays connected to I2C via a PCF8574 https://blog.matroid.org:443/display/89 Mon, 18 Oct 2021 15:47:48 GMT <p><div class="center"> <a href="https://blog.matroid.org:443/files/20211018-io-expansion-relais-board/sensors-anotated-2021-09-20-172444_003__io-relais.jpg"><img src="https://blog.matroid.org:443/files/20211018-io-expansion-relais-board/sensors-anotated-2021-09-20-172444_003__io-relais_500.jpg" title="relay module connected to I2C via a PCF8574; click for a larger version (180 kB)." alt="relay module connected to I2C via a PCF8574; click for a larger version (180 kB)."></a></div></p> <p>Looking at the data sheet of the PCF8574 I found that it will be trivially simple to use it to control a relay board without any lower level Arduino library: Just write a second byte in addtion to the address to the I2C bus directly with uLisp's <a href="http://www.ulisp.com/show?1EK4">WITH-I2C</a>.</p> <p>Each bit of the byte describes the state of one of the eight outputs, or rather its inverted state as the PCF8574 has open-drain outputs and thus setting an output to LOW opens a connection to ground (with up to 25 mA), while HIGH disables the relay. (The data sheets actually say they are push-pull outputs but as high-level output the maximum current is just 1 mA which is not much and for this purpuse certainly not enough.)</p> <p>The whole job can basically done with one or two lines. Here is switching on the forth relay (that is number 3 with zero-based counting):</p> <p><div class="code"> <pre>(with-i2c (str #x20) (write-byte (logand #xff (lognot (ash 1 3))) str))</pre></div></p> <p>Here is my whole initial library: </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/89">whole article.</A> </I> </P> uLisp on M5Stack (ESP32):<br/>Stand-alone uLisp computer (with code!) https://blog.matroid.org:443/display/88 Fri, 02 Apr 2021 12:56:46 GMT <p>Last Thursday, I started to use the m5stack faces keyboard <a href="https://blog.matroid.org:443/display/82"><span class="title">I mentioned before</span></a> and wrote a keyboard interpreter and REPL so that this makes another little handheld self-containd uLisp computer. Batteries are included so this makes it stand-alone and take-along. :) </p> <p>I have made this as a present to my nephew who just turned eight last Saturday. Let's see how this can be used to actually teach a bit of Lisp. The first programming language needs to be Lisp, of course!</p> <p><div class="center"> <a href="https://blog.matroid.org:443/files/20210402-m5stack-faces-standalone-ulisp-computer/2021-03-27-114451_m5stack-standalone-ulisp-computer.jpg"><img src="https://blog.matroid.org:443/files/20210402-m5stack-faces-standalone-ulisp-computer/2021-03-27-114451_m5stack-standalone-ulisp-computer_sma.jpg" title="Programming “Hello World!” on the M5Stack with Faces keyboard; click for a larger version (252 kB)." alt="Programming “Hello World!” on the M5Stack with Faces keyboard; click for a larger version (252 kB)."></a></div> </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/88">whole article.</A> </I> </P> uLisp on M5Stack (ESP32):<br/> temperature sensors via one wire https://blog.matroid.org:443/display/87 Sat, 27 Mar 2021 20:18:40 GMT <p>I added support for Dallas temperature sensors to <a href="https://github.com/m-g-r/ulisp-esp-m5stack">ulisp-esp-m5stack</a>. Activate <tt>#define enable_dallastemp</tt> in order to use it. It bases on the Arduino libraries <tt>OneWire.h</tt> <tt>DallasTemperature.h</tt>.</p> <p>I used pin 16 to connect my sensors but you can change ONE_WIRE_BUS to use a different pin. As the OneWire library uses simple bit bagging and no hardware support, e. g. UART, any general-purpose input/output (GPIO) pin will work.</p> <p>The interface consists of four uLisp functions: INIT-TEMP, GET-TEMP, SET-TEMP-RESOLUTION, and GET-TEMP-DEVICES-COUNT. Here is their documentation:</p> <p><div class="code"> <pre>Function init-temp Syntax: init-temp => result-list</pre></p> <p><tt> Arguments and values:<br> &ensp;&ensp;&ensp;result-list---a list of device addresses; each address being a list of 8 integer values specifying a device address.</p> <p>Description:<br> &ensp;&ensp;&ensp;Detects all supported temperature sensors connected via one wire bus to the pin ONE_WIRE_BUS and returns the list of the sensors' device addresses.</p> <p>&ensp;&ensp;&ensp;All sensors are configured to use the resolution specified by default DEFAULT_TEMPERATURE_PRECISION via a broadcast. Note that a sensor might choose a different resolution if the desired resolution is not supported. See also: set-temp-resolution. </tt></div> </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/87">whole article.</A> </I> </P> "Curl/Wget for uLisp"<br/>Or: An HTTP(s) get/post/put function for uLisp https://blog.matroid.org:443/display/86 Tue, 23 Feb 2021 11:37:49 GMT <p>Oh, I forgot to continue posting… I just published a quite comprehensive HTTP function supporting put, post, get, auth, HTTP and HTTPS, and more for uLisp at <a href="https://github.com/m-g-r/ulisp-esp-m5stack">ulisp-esp-m5stack</a>.</p> <p>Activate <tt>#define enable_http</tt> and <tt>#define enable_http_keywords</tt> to get it; the keywords used by the <tt>http</tt> function are to be enabled separately as they might be used more general and not just by this function.</p> <p>Note that you need to connect to the internet first. Usually with <a href="http://www.ulisp.com/show?2B27"><tt>WIFI-CONNECT</tt></a>.</p> <p>Here is the full documentation with example calls: </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/86">whole article.</A> </I> </P> Again more features for uLisp on M5Stack (ESP32):<br/>time via NTP, lispstring without escaping and more space https://blog.matroid.org:443/display/85 Tue, 16 Feb 2021 19:41:15 GMT <p>I just pushed three small things to <a href="https://github.com/m-g-r/ulisp-esp-m5stack">ulisp-esp-m5stack</a>: Get time via NTP, add optional escape parameter to function <tt>lispstring</tt>, increased <tt>WORKSPACESIZE</tt> and <tt>SYMBOLTABLESIZE</tt> for M5Stack. </p> <p><h3>Getting time via NTP</h3> Enable <tt>#define enable_ntptime</tt> to get time via NTP. New functions <tt>INIT-NTP</tt> and <tt>GET-TIME</tt>. Note that you need to connect to the internet first. Usually with <a href="http://www.ulisp.com/show?2B27"><tt>WIFI-CONNECT</tt></a>. </p> <p><div class="code"> <pre>Function init-ntp Syntax: init-ntp => nil</pre></p> <p><tt> Description:<br> &ensp;&ensp;&ensp;Initializes and configures NTP. </tt></div></p> <p><div class="code"> <pre>Function get-time Syntax: get-time => timestamp</pre></p> <p><tt> Arguments and values:<br> &ensp;&ensp;&ensp;timestamp---a string; containing a timestamp in the format of xsd:dateTime.</p> <p>Description:<br> &ensp;&ensp;&ensp;Returns a timestamp in the format of xsd:dateTime. </tt></div> </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/85">whole article.</A> </I> </P> More features for uLisp on M5Stack (ESP32):<br/>flash support, muting of the speaker and backlight control https://blog.matroid.org:443/display/84 Mon, 15 Feb 2021 21:36:44 GMT <p>I finished the IoT sensor device prototype and shipped it last Thursday. It just has a stub bootstrap system in the flash via uLisp's Lisp Library and downloads the actual application in a second boot phase via HTTPS. More on that later.</p> <p>To make it happen I've added a bunch of things to <a href="https://github.com/m-g-r/ulisp-esp-m5stack">ulisp-esp-m5stack</a>: flash support, fixes for some quirks of the M5Stack, time via NTP, an HTTP function supporting methods PUT, POST, GET, Auth, HTTP and HTTP, temperature sensors via one wire, and more. I plan to publish all these features in the next days.</p> <p>Today you get: flash support, muting of the builtin speaker and control of the LED backlight of the builtin display. </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/84">whole article.</A> </I> </P> StumpWM: vsplit-three https://blog.matroid.org:443/display/83 Sun, 07 Feb 2021 00:19:25 GMT <p>A good ten month ago I switched away from a full desktop environment being finally tired enough that user software gets more and ever more features and tries to anticipate more and more what I <em>might want</em> but in the end my own computer never <em>actually does</em> what I want and only that. PulseAudio being the most dreaded example of a piece of code that gets more, more and more magic and complexity and in the end it never does what you actually want while at the same time telling it to do so got completely impossible because of many layers of abstractions and magic. PulseAudio has a lot of "rules", "profiles", "device intended roles", "autodetecting", "automatic setup and routing" and "other housekeeping actions". Look at this article <a href="https://gavv.github.io/articles/pulseaudio-under-the-hood/">PulseAudio under the hood</a> by Victor Gaydov (which is also the source of the terms I just quoted): It has 174 occurrences of words starting with "auto-": automatically – 106, automatic – 27, autoload<em> – 16, autospawn – 14, autodetect – 4, autoexit – 2, automate</em> – 2, auto timing – 1, auto switch – 1, and once "magically" when it is even too much for the author.</p> <p>So, more control and less clutter instead. After years again I use just a good old window manager, individual programs, and got rid of PulseAudio. </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/83">whole article.</A> </I> </P> uLisp on M5Stack (ESP32) https://blog.matroid.org:443/display/82 Thu, 28 Jan 2021 13:17:29 GMT <p>About two years I ago I bought a couple of <a href="http://www.m5stack.com">M5Stack ESP32 computers</a> on a Maker Fair. I made little use of them so far but now I started to put <a href="http://www.ulisp.com/">uLisp</a> on them and suddenly it is much more fun. </p> <p><div class="center"> <a href="https://blog.matroid.org:443/files/20210128-uLisp-esp-m5stack/20210124_233315_lev-desp-mid.jpg"><img src="https://blog.matroid.org:443/files/20210128-uLisp-esp-m5stack/20210124_233315_lev-desp-sma.jpg" title="“Hello uLisp!” on the M5Stack; click for a larger version (323 kB)." alt="“Hello uLisp!” on the M5Stack; click for a larger version (323 kB)."></a></div> </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/82">whole article.</A> </I> </P> 20 years' anniversary for SBCL https://blog.matroid.org:443/display/81 Sun, 24 Jan 2021 12:28:40 GMT <p><div class="center"> <a href="https://blog.matroid.org:443/files/20210124-20-years-SBCL/20191209-20-Years-anniversary-for-SBCL.jpeg"><img src="https://blog.matroid.org:443/files/20210124-20-years-SBCL/20191209-20-Years-anniversary-for-SBCL_sm.jpeg" title="20 years' anniversary for SBCL has started; click for a larger version (222 kB)." alt="20 years' anniversary for SBCL has started; click for a larger version (222 kB)."></a></div> </p> <p><br/> (Moving content <a href="https://blog.matroid.org:443/display/77"><span class="title">from Twitter</span></a>: <a href="https://twitter.com/RetzlaffWenger/status/1203957390351224832">originally posted on Dec 9, 2019, 9:39 AM.</a>)</p><P><I>Read the <A HREF="https://blog.matroid.org:443/display/81">whole article.</A> </I> </P> Motto: Our LISP is COMMON LISP https://blog.matroid.org:443/display/80 Sun, 24 Jan 2021 12:18:20 GMT <p><div class="center"> <a href="https://blog.matroid.org:443/files/20210124-Our-Lisp/Our-Lisp-is-COMMON-LISP_Lisp-2nd-edition_Winston-and-Horn.jpeg"><img src="https://blog.matroid.org:443/files/20210124-Our-Lisp/Our-Lisp-is-COMMON-LISP_Lisp-2nd-edition_Winston-and-Horn.jpeg" title="Our LISP is COMMON LISP, from: Lisp 2nd edition by Winston and Horn, Addison Wesley, 1984; click for a larger version (198 kB)." alt="Our LISP is COMMON LISP, from: Lisp 2nd edition by Winston and Horn, Addison Wesley, 1984; click for a larger version (198 kB)."></a></div></p> <p>Excerpt from: Lisp 2nd edition by Winston and Horn, Addison Wesley, 1984.</p> <p><br/> (Moving content <a href="https://blog.matroid.org:443/display/77"><span class="title">from Twitter</span></a>: <a href="https://twitter.com/RetzlaffWenger/status/1205503658273718277">originally posted on Dec 13, 2019, 4:04 PM.</a>)</p><P><I>Read the <A HREF="https://blog.matroid.org:443/display/80">whole article.</A> </I> </P> On the different versions of the<br/> ANSI Common Lisp Standard X3.226-1994 https://blog.matroid.org:443/display/79 Thu, 21 Jan 2021 21:21:21 GMT <p>The Common Lisp standard has had different names and annual details suffixes. The standard was developed by the Technical Committee X3J13 of the “Accredited Standards Committee X3, Information Technology” founded and accredited by the American National Standards Institute (ANSI) in <a href="https://www.incits.org/about/history">1961</a>.</p> <p>In one of my professional lives I am working in the “Accredited Standards Committee X12” (also written as “ASC X12” or just “X12”; founded in 1979) since just shy of four years now and was voted “TAS Representative” of <a href="https://x12.org/about/committees/subcommittee-x12c-communications-and-controls">“Subcommittee X12C – Communications and Controls”</a> (<a href="https://blog.matroid.org:443/files/20210119-ANSI-Common-Lisp-Standard/2021-01-19-X12C.png">local copy</a>) in January 2018, that is, I represent X12C in <a href="https://x12.org/about/committees/subcommittee-x12j-technical-assessment">“Subcommittee X12J – Technical Assessment”</a> (<a href="https://blog.matroid.org:443/files/20210119-ANSI-Common-Lisp-Standard/2021-01-19-X12J.png">local copy</a>), short “TAS”, since then. Having that background, I might be able to shed a light on the different versions of the Common Lisp standard and on how standardization committees' work looks in general.</p> <p>I have to admit that one of the reasons I liked to start working in X12 is that I knew that the Common Lisp standard was developed by X3. I did now know how standards were developed and how such a committee worked, and I was curious to change that.</p> <p>When you search in the <a href="https://webstore.ansi.org">ANSI Webstore</a> you'll find different versions: <ul> <li> <a href="https://webstore.ansi.org/Standards/INCITS/ANSIX32261994">ANSI X3.226-1994</a> <li> <a href="https://webstore.ansi.org/Standards/INCITS/ANSIINCITS2261994R1999">ANSI INCITS 226-1994 (R1999)<br/> (formerly ANSI X3.226-1994 (R1999))</a> <li> <a href="https://webstore.ansi.org/Standards/INCITS/ANSIINCITS2261994R2004">ANSI INCITS 226-1994 (R2004)</a> <li> <a href="https://webstore.ansi.org/Standards/INCITS/INCITS2261994S2008">INCITS 226-1994 [S2008]</a> </ul></p> <p>The standard was originally published (or, more precisely, approved for publication) in 1994, so the first version is just called “ANSI X3.226-1994”. The date of approval was December 8, 1994. </p> <P><I>Read the <A HREF="https://blog.matroid.org:443/display/79">whole article.</A> </I> </P> Original IBM 3-ring binders https://blog.matroid.org:443/display/78 Thu, 21 Jan 2021 21:06:53 GMT <p>Follow-up to <a href="https://blog.matroid.org:443/display/76"><span class="title">Physical dimensions of ANSI Common Lisp</span></a>: It just took two days of searching and I got these three beautiful 25+ year old IBM 3-ring binders. How nice to live in Berlin!</p> <p><div class="center"> <a href="https://blog.matroid.org:443/files/20201228-Common-Lisp-IBM-binders/DSC_1071_lev-rot-cr-mid.jpg"><img src="https://blog.matroid.org:443/files/20201228-Common-Lisp-IBM-binders/DSC_1071_lev-rot-cr-sma.jpg" title="ANSI Common Lisp in IBM 3-ring binders; click for a larger version (228 kB)." alt="ANSI Common Lisp in IBM 3-ring binders; click for a larger version (228 kB)."></a></div></p> <p>Ah, yes, much better:</p> <p><div class="center"> <a href="https://blog.matroid.org:443/files/20201228-Common-Lisp-IBM-binders/DSC_1077_lev-rot-cr2-mid.jpg"><img src="https://blog.matroid.org:443/files/20201228-Common-Lisp-IBM-binders/DSC_1077_lev-rot-cr2-sma.jpg" title="ANSI Common Lisp in IBM 3-ring binders; click for a larger version (247 kB)." alt="ANSI Common Lisp in IBM 3-ring binders; click for a larger version (247 kB)."></a></div></p> <p>And yes, if you don't want them full to the brim you need three binders for the ANSI Common Lisp standard.</p><P><I>Read the <A HREF="https://blog.matroid.org:443/display/78">whole article.</A> </I> </P> Physical dimensions of ANSI Common Lisp https://blog.matroid.org:443/display/76 Sun, 20 Dec 2020 15:42:29 GMT <p>If you ever wondered what a unit of ANSI Common Lisp weights: It's 3.1 kg!</p> <p><div class="center"> <a href="https://blog.matroid.org:443/files/20201220-Common-Lisp/DSC_0934_crlev-mid.JPG"><img src="https://blog.matroid.org:443/files/20201220-Common-Lisp/DSC_0934_crlev-sma.JPG" title="ANSI Common Lisp on a scale; click for a larger version (238 kB)." alt="ANSI Common Lisp on a scale; click for a larger version (238 kB)."></a></div></p> <p>And duplex printed on ANSI(sic!) letter paper, it's a stack of 7 cm height.</p> <p><div class="center"> <a href="https://blog.matroid.org:443/files/20201220-Common-Lisp/DSC_0989_crlev_mid.JPG"><img src="https://blog.matroid.org:443/files/20201220-Common-Lisp/DSC_0989_crlev_sma.JPG" title="Measuring the height of ANSI Common Lisp; click for a larger version (2908 kB)." alt="Measuring the height of ANSI Common Lisp; click for a larger version (2908 kB)."></a></div></p> <p>Still beautiful:</p> <p><div class="center"> <a href="https://blog.matroid.org:443/files/20201220-Common-Lisp/DSCPDC_0003_BURST20201217114402368_COVER_crlev_mid.JPG"><img src="https://blog.matroid.org:443/files/20201220-Common-Lisp/DSCPDC_0003_BURST20201217114402368_COVER_crlev_sma.JPG" title="Printout of ANSI INCITS 226-1994 (R2004) (formerly ANSI X3.226-1994 (R1999)); click for a larger version (3028 kB)." alt="Printout of ANSI INCITS 226-1994 (R2004) (formerly ANSI X3.226-1994 (R1999)); click for a larger version (3028 kB)."></a></div></p> <p>By the way, this is the "American National Standard for Information Technology – Programming Language Common Lisp", "ANSI INCITS 226-1994 (R2004) (formerly ANSI X3.226-1994 (R1999))", but more on the different revisions in a separate post.</p> <p>I've got <a href="https://www.cliki.net/cltl2">CLtL2</a> for years and use the <a href="http://www.lispworks.com/documentation/common-lisp.html">Common Lisp HyperSpec</a> for, puh, 16 years?, still I am surprised by the sheer volume and weight of this printed copy!</p> <p>Next question: Where do I get a three 3-ring binder for US letter pages in Germany? (Update, see: <a href="https://blog.matroid.org:443/display/78"><span class="title">Original IBM 3-ring binders</span></a>)</p><P><I>Read the <A HREF="https://blog.matroid.org:443/display/76">whole article.</A> </I> </P>