Enter the query into the form above. You can look for specific version of a package by using @ symbol like this: gcc@10.
API method:
GET /api/packages?search=hello&page=1&limit=20
where search is your query, page is a page number and limit is a number of items on a single page. Pagination information (such as a number of pages and etc) is returned
in response headers.
If you'd like to join our channel webring send a patch to ~whereiseveryone/toys@lists.sr.ht adding your channel as an entry in channels.scm.
In Common Lisp, a special variable that is never dynamically bound typically serves as a stand-in for a global variable. The global-vars library provides true global variables that are implemented by some compilers. An attempt to rebind a global variable properly results in a compiler error. That is, a global variable cannot be dynamically bound.
Global variables therefore allow us to communicate an intended usage that differs from special variables. Global variables are also more efficient than special variables, especially in the presence of threads.
Clamp is an attempt to bring the powerful, but verbose, language of Common Lisp up to the terseness of Arc.
There are two parts to Clamp. There is the core of Clamp, which implements the utilities of Arc that are easily converted from Arc to Common Lisp. The other part is the "experimental" part. It contains features of Arc that are not so easy to copy (ssyntax, argument destructuring, etc.).
This package provides a PNG Common Lisp system to operate with Portable Network Graphics file format.
The Type-Templates library allows you to define types and “template functions” that can be expanded into various type-specialized versions to eliminate runtime dispatch overhead. It was specifically designed to implement low-level numerical data types and functionality.
This is a lightweight, non-consing, optimized queue implementation for Common Lisp.
This is a Common Lisp implementation of the Encoding for Robust Immutable Storage specification (ERIS).
This a Common Lisp library for reading and writing binary data. It is based on code from chapter 24 of the book Practical Common Lisp.
This is a backend for the linear-programming Common Lisp library using the GNU Linear Programming Kit (GLPK) library.
NDebug provides a small set of utilities to make graphical (or, rather non-REPL-resident) Common Lisp applications easier to integrate with the standard Lisp debugger (*debugger-hook*, namely) and implementation-specific debugger hooks (via trivial-custom-debugger), especially in a multi-threaded context.
This is a task scheduling framework for Common Lisp.
This is a library to abstract away the parsing of Unix-style command-line arguments. Use it in conjunction with asdf:program-op or cl-launch for portable processing of command-line arguments.
System-Load is a Common Lisp library for accessing the system's CPU and memory usage.
This package provides a standard interface to the various package lock implementations of Common Lisp.
Radiance is a web application environment, which is sort of like a web framework, but more general, more flexible. It should let you write personal websites and generally deployable applications easily and in such a way that they can be used on practically any setup without having to undergo special adaptations.
This library is a small interface to portable but nonstandard introspection of Common Lisp environments. It is intended to allow a bit more compile-time introspection of environments in Common Lisp.
Quite a bit of information is available at the time a macro or compiler-macro runs; inlining info, type declarations, that sort of thing. This information is all standard - any Common Lisp program can (declare (integer x)) and such.
This info ought to be accessible through the standard &environment parameters, but it is not. Several implementations keep the information for their own purposes but do not make it available to user programs, because there is no standard mechanism to do so.
This library uses implementation-specific hooks to make information available to users. This is currently supported on SBCL, CCL, and CMUCL. Other implementations have implementations of the functions that do as much as they can and/or provide reasonable defaults.
This Common Lisp library provides an implementation of in-memory input streams, output streams and io streams for any type of elements.
This package provides an extensible implementation of defclass that can accurately control the expansion according to the metaclass and automatically detect the suitable metaclass by analyzing the defclass form.
Common Lisp implementation of Graham Cormode and S. Muthukrishnan's Effective Computation of Biased Quantiles over Data Streams in ICDE’05.
CL-MOUNT-INFO is a Common Lisp wrapper around getmntent(3) and related C functions to get information about the mounted file system.
This is a string/octets parser library for Common Lisp with speed and readability in mind. Unlike other libraries, the code is not a pattern-matching-like, but a char-by-char procedural parser.
Croatoan provides high-level Common Lisp CLOS bindings for the ncurses terminal library.
This lisp library handles physical quantities which consist of
value / magnitude
uncertainty / error
unit
where the type of the value can be any subtype of real. For the uncertainty, both absolute and relative values are possible. Combinations of lisp symbols or strings are used to describe units. User defined units including abbreviations and prefixes are supported. Error propagation and unit checking is performed for all defined operations.
A miniature toolkit that contains some useful shifting/popping/pushing functions for arrays and vectors. Originally from Plump.
A hook, in the present context, is a certain kind of extension point in a program that allows interleaving the execution of arbitrary code with the execution of a the program without introducing any coupling between the two. Hooks are used extensively in the extensible editor Emacs.
In the Common LISP Object System (CLOS), a similar kind of extensibility is possible using the flexible multi-method dispatch mechanism. It may even seem that the concept of hooks does not provide any benefits over the possibilities of CLOS. However, there are some differences:
There can be only one method for each combination of specializers and qualifiers. As a result this kind of extension point cannot be used by multiple extensions independently.
Removing code previously attached via a
:before,:afteror:aroundmethod can be cumbersome.There could be other or even multiple extension points besides
:beforeand:afterin a single method.Attaching codes to individual objects using eql specializers can be cumbersome.
Introspection of code attached a particular extension point is cumbersome since this requires enumerating and inspecting the methods of a generic function.
This library tries to complement some of these weaknesses of method-based extension-points via the concept of hooks.