When you write a comprehensive test suite you will most likely need to repeat the same set up and tear down process multiple times because a lot of the tests will test the same basic scenario in a slightly different way. Testing frameworks address this code repetition problem with 'fixtures'. FiveAM also has this concept, although slightly limited. FiveAM implements fixtures as a wrapper around defmacro. The documentation states: NB: A FiveAM fixture is nothing more than a macro.

Since the term 'fixture' is so common in testing frameworks we've provided a wrapper around defmacro for this purpose. There are no examples in the documentation on what such a fixture-macro should look like. Do you need the usual macro symbology like backticks and splicing or not? This can be difficult to decipher if you are not fluent in reading macros.

The single example in the source code is making things worse because it does include backticks and splicing. FiveAM defines a macro def-fixture which allows you write your fixtures just like normal functions with the one exception that there is an implicit variable &body to represent your test code. No fiddling with complex macros! This is a simple example: (def-fixture in-test-environment 'Set up and tear down the test environment.' (setup-code) (&body) (teardown-code)) (def-test a-test 'Test in clean environment.'

(with-fixture in-test-environment (is-true (some-function)))) The fixture implementation provides an easy-to-use definition syntax without any additional processing. If you need more complex macros than what def-fixture can handle you can write normal Lisp macros as usual without interfering with FiveAM's operation.

Sharing here a small collection of documents by Douglas B. Lenat related to design AM and EURISKO that I assembled over the years.

These are among the most famous programs of symbolic AI era. They represent so-called 'discovery systems'. Unlike expert systems, they run loosely-constrained heuristic search in a complex problem domain. AM was Lenat's and the first attempt of such kind. Unfortunately, it's all described in rather informal pseudocode, a decision that led to a number of misunderstandings in follow-up criticism. Lenat has responded to that in one of the better known publications,.

AM was built around concept formation process utilizing a set of pre-defined heuristics. EURISKO takes it a step further, adding the mechanism of running discovery search on its own heuristics. Both are specimen of what we could call 'Lisp-complete' programs: designs that require Lisp or its hypothetical, similarly metacircular equivalent to function. Their style was idiomatic to INTERLISP of 1970s, making heavy use of FEXPRs and self-modification of code. There's quite a lot of thorough analysis available in three-part The Nature of Heuristics:,.

Contains the most insights into the workings of EURISKO. Remarkable quote of when EURISKO discovered Lisp atoms, reflecting it was written before the two decade pause in nuclear annihilation threat: Next, EURISKO analyzed the differences between EQ and EQUAL. Specifically, it defined the set of structures which can be EQUAL but not EQ, and then defined the complement of that set. This turned out to be the concept we refer to as LISP atoms. In analogy to humankind, once EURISKO discovered atoms it was able to destroy its environment (by clobbering CDR of atoms), and once that capability existed it was hard to prevent it from happening. Lenat's from all this was that 'common sense' is necessary to drive autonomous heuristic search, and that a critical mass of knowledge is necessary.

That's where his current CYC project started off in early 1990s. Bonus material: The Elements of Artificial Intelligence Using Common Lisp by Steven L. Tanimoto describes a basic AM clone,. — 32 days ago. New projects:. — Implements - and - from Clojure, as well as several expansions on the idea. — CC0.

— Authenticated-Encryption functions — MIT. — Base64 encoding and decoding for Common Lisp. — Apache 2.0. — Noise library for Common Lisp. — BSD.

— clBLAS binding — Apache License, Version 2.0. — Utility library for loading.env files — MIT. — A Fuzz Testing Framework — BSD-2. — Library to manipulate LAS files — ISC. — CL-PROJ provides Proj.4 library bindings — BSD. — Common Interface to the ISO prolog implementations from Common Lisp — MIT.

— Code coverage utility for Common Lisp — MIT. — DESTRUCTURING-BIND with proper error signaling — MIT. — A stream that always blocks and never has data available. — Public domain.

— Binary Heap for Common Lisp. — Apache 2.0. — Huffman encoding and decoding for Common Lisp. — Apache 2.0. — Lazy forms for Common Lisp.

— Apache 2.0. — Lorem ipsum generator in portable Common Lisp — MIT. — Parsing package for Common Lisp. — Apache 2.0. — Simple html generator.

— MIT License. — Common Lisp PROtocol and TESTcase Manager — LLGPL. — Lua-style string pattern matching. — Apache 2.0. — This project contains several Common Lisp packages — MIT. — A variant of READ secure against internbombing, excessive input and macro characters.

— BSD 2-clause. — Filter parameters — BSD 2-Clause. — additional library collection for cl-collider — Public Domain / 0-clause MIT. — SHA1 Digest and HMAC for LispWorks. — Apache 2.0.

— A fast, purely functional data structure library — BSD-3. — Targa Image Loading for Common Lisp. — Apache 2.0.

— Compatibility package exporting CLtL2 functionality — LLGPL Updated projects:,. Removed projects: clot, clpmr, cobstor, html-sugar, ie3fp, manardb, metafs, mime4cl, net4cl, npg, ods4cl, plain-odbc, quid-pro-quo, sanitized-params, sclf, smtp4cl, tiff4cl. The removed projects no longer work on SBCL. To get this update, use (ql:update-dist 'quicklisp'). — 59 days ago. Interactivity is a principal requirement for a usable programming environment. Interactivity means that there should be a shell/console/REPL or other similar text-based command environment.

And a principal requirement for such an environment is keeping history. And not just keeping it, but doing it robustly:. recording history from concurrently running sessions. keeping unlimited history. identifying the time of the record and its context This allows to freely experiment and reproduce the results of successful experiments, as well as go back to an arbitrary point in time and take another direction of your work, as well as keeping DRY while performing common repetitive tasks in the REPL (e.g.

Initialization of an environment or context). Or frlog (when you need a distinct name) is a small tool that intends to support all these requirements. It grew out of a frustration with how history is kept in SLIME, so it was primarily built to support this environment, but it can be easily utilized for other shells that don't have good enough history facility.

It is possible due to its reliance on the most common and accessible data-interchange facility: text-based HTTP. Frlog is a backend service that supports any client that is able to send an HTTP request. The backend is a Common Lisp script that can be run in the following manner (probably, the best way to do it is inside screen): sbcl -noprint -load hunch.lisp - -port 7654 -script flight-recorder.lisp If will print a bunch of messages that should end with the following line (modulo timestamp): 2018-09-29 16:00:53 INFO Started hunch acceptor at port: 7654. The service appends each incoming request to the text file in markdown format: /.frlog.md. The API is just a single endpoint - /frlog that accepts GET and POST requests. The parameters are:. text is the content (url-encoded, for sure) of the record that can, alternatively, be sent in the POST request's body (more robust) Optional query parameters are:.

title - used to specify that this is a new record: for console-based interactions, usually, there's a command and zero or more results - a command starts the record (and thus should be accompanied with the title: for SLIME interactions it's the current Lisp package and a serial number). An entitled record is added in the following manner: ### cl-user (10) 2018-09-2915:49:17 (uiop:pathname-directory-pathname ) If there's no title, the text is added like this:;;; 2018-09-2915:49:29 #. tag - if provided it signals that the record should be made not to a standard.frlog.md file, but to.frlog.md. This allows to easily log a specific group of interactions separately If the response code is 200 everything's fine. Currently, 2 clients are available:. a SLIME client flight-recorder.el that monkey-patches a couple of basic SLIME functions (just load it from Emacs if you have SLIME initialized).

and a tiny Lisp client frlog.lisp P.S. To sum up, more and more I've grown to appreciate simple (sometimes even primitive - the primitive the better:) tools. Flight-recorder seems to me to be just like that: it was very easy to hack together, but it solves an important problem for me and, I guess, for many. And it's the modern 'Unix way': small independent daemons, text-based formats and HTTP instead of pipes. Frlog uses another tiny tool of mine - that I've already utilized in a number of projects but haven't described yet - it's a topic for another post. In short, it is a script to streamline running hunchentoot that does all the basic setup and reduces the developer's work to just defining the HTTP endpoints. I know, the name is, probably, taken and it's a rather obvious one.

But I think it just doesn't matter in this case.:) — 89 days ago. New projects:. — A generator for the i3 status bar. — Artistic.

— A script to evaluate expressions in multiple lisp implementations. — Artistic. — A SuperCollider client for CommonLisp — Public Domain. — Implements the CLTL2 environment access functionality for implementations which do not provide the functionality to the programmer. — MIT.

— Double-entry accounting system. — BSD-3. — Interface of MeCab that is a morpheme analyzer — LLGPL. — lisp code generator for swagger — 2-clause BSD. — A cmake script parser. — MIT. — Provides support for UUIDs as proper values — MIT.

— System to version the database in roughly the same way rails migrations work. Differences are that only one database is really supported (but hacking around that is trivial) and that migrations are not needed to be stored in separate files. — MIT. — A portability library for IEEE float features not covered by the CL standard.

— Artistic. — An iCalendar format lirbary. — Artistic. — Customize and manage Lisp parens reader — MIT. — Declare binary formats as structs and then read and write them. — GPLv3.

— Portable mmap (file memory mapping) utility library. — Artistic. — A small library to generate pango-style text markup. — Artistic. — Elegant High Performance Computing — AGPLv3. — A friendly interface for creating a Plump DOM.

— MIT. — Print the licenses used by the given project and its dependencies. — MIT. — Sylvester the Cat's Common Lisp IDE — Public Domain.

— Display the stars of a GitHub User — GPL 3. — A client library for the Studio image hosting service — Artistic. — Convenience functions and macros for testing Common Lisp applications via Prove and Quickcheck — MIT Expat. — A collection of useful functions and macros.

— MIT. — Module system for language embeddings. — MIT Updated projects:,. Removed projects: cl-clblas, cl-proj. There are no direct problems with. They are victims of a hard drive crash on my end, and an incomplete recovery.

I have not been able to set up the foreign libraries required to build those projects in time for this month's release. If you want to continue using cl-clblas and cl-proj, there are a few options:. Don't upgrade to the latest Quicklisp dist until they are back in.

If you already upgraded,. Clone their repos into /quicklisp/local-projects.

That’s not as nice as rewinding the PC to just before the syscall, with a fixed up state that will resume the operation, but is simpler to implement, and usually good enough. Classic worst is better (Unix semantics are also safer with concurrency, but that could have been opt-in.). That’s not a new observation, and SUN heads like to point to prior art like,. Linux sometimes has to reinvent everything with its special flavour.

For instance, but TSX is slow enough that SuperMalloc first tries to use a per-thread cache. Explored the use of hardware transactional lock elision solely to abort on context switches; they maintained high system throughput under contention by trying the transaction once before falling back to a regular lock. I did not expect systems programming to get near multi-agent epistemic logic;). Which is fixable with LOCKed instructions, but that defeats the purpose of per-CPU data. I actually found the logic bug before the Spectre/Meltdown fire drill and was worried the hole would be plugged. This one survived the purge.

Fingers crossed — 95 days ago. In my previous, I complained about a misfeature of the editor that prevented binding editor functions to the Ctrl-S and Ctrl-Q keys.

Image Result For Cute Aesthetic Suga Wallpaper For Mac

In the manual, it is stated that these keys cannot be bound due to 'system restrictions'. It appears, though, that it is a measure to prevent users from footing themselves in the foot because Ctrl-S and Ctrl-Q could be sent by terminals to implement.

Software flow control is optional, though; it can be switched on and off for each terminal line and it is not needed for virtual terminal connections (Telnet, DECNET) as flow control is implemented by the network layer and networked terminal sessions usually have enough buffer space. Thus, reserving Ctrl-S and Ctrl-Q really only makes sense for asynchronous terminal lines that require software flow control, and there is no reason to reserve these characters for all terminal sessions, regardless of technology. I am used to having Ctrl-S and Ctrl-Q be bound to certain functions from GNU Emacs, and I want to use the same bindings with VAX LISP as they've become part of my muscle memory. Thus, I wanted to remove the explicit checks for these keys in the EDITOR::BIND-COMMAND and BIND-KEYBOARD-FUNCTION functions. Lacking the source code to VAX LISP, I could not just remove the checks and recompile, so I needed a different way.

Image Result For Cute Aesthetic Suga Wallpaper For Macbook

This is where the VMS PATCH utility comes into play. It is a standard tool that is used to modify program executables, usually to remove bugs without requiring a full reinstallation of the software package that needs to be fixed. Finding what to patch In order to remove the checks for Ctrl-S/Q in EDITOR::BIND-COMMAND and BIND-KEYBOARD-FUNCTION, I disassembled the two function using the standard VAX LISP function DISASSEMBLE. VAX assembler code is easy to read, so it was rather straightforward to find out how the checks work. As I did not have the source code or the symbol table for LISP.EXE when I developed this patch, I needed to resort to patching in absolute mode which is kind of brittle. PATCH can also work in symbolic mode if a symbol table is available for the executable file, which allows patches to work even if the executable has been linked differently than the executable used to develop the patch (i.e.

You could write a patch for a library function that'd work for executables that were linked statically against the library). Also, PATCH allows patches to insert more instructions than were originally present in the executable.

It does this by adding additional disk space to the executable to hold the new, longer code, and then patch the required jump instructions to the patch area into the original location. Closing thoughts.