split-sequence is a small library to split sequences in to a list of
subsequences delimited by an object satisfying a test function. It is
a member of the Common Lisp Utilities family of programs, designed by
community consensus.
trivial-features ensures consistent *FEATURES* across multiple
Common Lisp implementations.
For example, on MacOS X platforms, while most Lisps push :DARWIN
to *FEATURES*, CLISP and Allegro push :MACOS and :MACOSX instead,
respectively. Some Lisps might not push any feature suggesting MacOS
X at all. trivial-features will make sure all Lisps will have :DARWIN
in the *FEATURES* list when running on MacOS X.
trivial-gray-streams is a trivial library which provides an extremely
thin compatibility layer for Gray streams.
From David N. Gray's STREAM-DEFINITION-BY-USER proposal:
"Common Lisp does not provide a standard way for users to define
their own streams for use by the standard I/O functions. This impedes
the development of window systems for Common Lisp because, while
there are standard Common Lisp I/O functions and there are beginning
to be standard window systems, there is no portable way to connect
them together to make a portable Common Lisp window system. There
are also many applications where users might want to define their
own filter streams for doing things like printer device control,
report formatting, character code translation, or encryption/decryption."
The dwarfdump tool prints the various elements of DWARF debugging
information found in ELF object files.
Fast CRC routines written in assembly language, callable using the C and Pascal
calling conventions, as well as directly from assembly language programs.
This Unix port contains routines for the calculation of traditional CRC-32
used by Zmodem, Opus, Ethernet, and many other protocols.
It also contains routines for the POSIX 1003.2 32-bit CRC calculation.
See ${PREFIX}/share/doc/fastcrc/index.html for reference.
This port requires ELF. It creates libfcrc.so.1, and includes <fastcrc.h> for
C programmers.
Dependencies: nasm
ebnf2yacc is a tool to help write yacc parsers/compilers. It takes as input a
grammar written in ebnf, and outputs a c++ abstract syntax tree that supports
the visitor pattern, along with a yacc file to build the tree.
Written in Scheme only, this adds input line editing feature to
Gauche. Assumes VT100 compatible terminal capability.
FSF binutils/gcc/gdb toolchain for ARM Cortex-M & Cortex-R
processors (Cortex-M0/M0+/M3/M4, Cortex-R4/R5/R7).
This port brings C and C++ compilers. Gloss and libc layer
are provided through newlib embedded C library.
This is complete package prepated by "GNU Tools for ARM Embedded
Processors" project (which is maintained by ARM company itself).
It includes:
binutils
gcc 5.3 with LTO and GRAPHITE support.
newlib optimized for speed
newlib-nano optimized for
two versions of libstdc++, optimized for speed and size.
gdb without sim.
All this is built with support for armv6-m, armv7-ar,
armv7-m and armv7e-m targets, armv7e-m with and without
FPU support and armv8-m too.
This port gives bit-to-bit compatibility with "official"
embedded ARM toolchain for MacOS X, Linux and Windows.
DrIFT is a type sensitive preprocessor for Haskell. It extracts type
declarations and directives from modules. The directives cause rules to
be fired on the parsed type declarations, generating new code which is
then appended to the bottom of the input file. The rules are expressed
as Haskell code, and it is intended that the user can add new rules as
required. DrIFT automates instance derivation for classes that aren't
supported by the standard compilers. In addition, instances can be
produced in separate modules to that containing the type declaration.
This allows instances to be derived for a type after the original module
has been compiled. As a bonus, simple utility functions can also be
produced from a type.
This library defines an Interpreter monad. It allows to load Haskell
modules, browse them, type-check and evaluate strings with Haskell
expressions and even coerce them into values. The library is
thread-safe and type-safe (even the coercion of expressions to values).
It is, essentially, a huge subset of the GHC API wrapped in a simpler
API.