Allegro is a cross-platform library intended for use in computer games and
other types of multimedia programming.
A wide range of extension packages and add-on modules are also available, which
can be found in the "Library Extensions" section of the Allegro website.
Allegro is a cross-platform library intended for use in computer games and
other types of multimedia programming.
A wide range of extension packages and add-on modules are also available, which
can be found in the "Library Extensions" section of the Allegro website.
A C/C++ library for controlling Pololu AVR hardware, such as the 3pi robot
and Orangutan family of robot controllers.
The ResourcePool is a generic connection caching and pooling management
facility. It might be used in an Apache/mod_perl environment to support
connection caching like Apache::DBI for non-DBI resources
(e.g. Net::LDAP). It's also useful in a stand alone perl application
to handle connection pools.
The key benefit of ResourcePool is the generic design which makes it
easily extensible to new resource types.
The ResourcePool has a simple check mechanism to detect and close broken
connections (e.g. if the database server was restarted) and opens new
connections if possible.
If you are new to ResourcePool you should go to the ResourcePool::BigPicture
documentation which provides the best entry point to this module.
The ResourcePool itself handles always exactly equivalent connections
(e.g. connections to the same server with the same user-name and password)
and is therefore not able to do a load balancing. The
ResourcePool::LoadBalancer is able to do a advanced load balancing across
different servers and increases the overall availability by applying a
failover policy if there is a server breakdown.
GNU Pth - The GNU Portable Threads
Copyright (c) 1999-2005 Ralf S. Engelschall <rse@gnu.org>
Pth is a very portable POSIX/ANSI-C based library for Unix platforms
which provides non-preemptive priority-based scheduling for multiple
threads of execution (aka ``multithreading'') inside event-driven
applications. All threads run in the same address space of the server
application, but each thread has it's own individual program-counter,
run-time stack, signal mask and errno variable.
The thread scheduling itself is done in a cooperative way, i.e., the
threads are managed by a priority- and event-based non-preemptive
scheduler. The intention is that this way one can achieve better
portability and run-time performance than with preemptive scheduling.
The event facility allows threads to wait until various types of events
occur, including pending I/O on file descriptors, asynchronous signals,
elapsed timers, pending I/O on message ports, thread and process
termination, and even customized callback functions.
pty is a tool to help debug console programs which take the terminal out of
canonical mode, by allowing the program being debugged and the debugger to run
on separate terminal devices.
To use pty, the programmer changes to the terminal device where he or she
wishes to interact with the program to be debugged, and at the shell
prompt, runs pty with no arguments. Pty will print out the filename of the
slave side of the pseudo-terminal it has opened. Inside the debugger,
running in another terminal device, one then redirects the program to be
debugged's IO to the slave (tty command of gdb). When you are finished
using pty, you must manually kill it. When pty starts it prints out its
pid.
INTRODUCTION --- WHAT IS NOWEB, ANYWAY?
noweb is a literate-programming tool like FunnelWEB or nuweb, only
simpler. A noweb file contains program source code interleaved with
documentation. When noweb is invoked, it writes the program source
code to the output files mentioned in the noweb file, and it writes
a TeX file for typeset documentation.
noweb is designed to meet the needs of literate programmers while
remaining as simple as possible. Its primary advantages are
simplicity, extensibility, and language-independence. noweb works
``out of the box'' with any programming language, and supports TeX,
latex, and HTML (Mosaic) back ends. A back end to support full
hypertext or indexing takes about 250 lines; a simpler one can be
written in 40 lines of awk. The primary sacrifice relative to WEB
is that code is not prettyprinted.
If you're brand new to literate programming, check out the FAQ for
the USENET newsgroup comp.programming.literate. There are also some
resources available through the noweb home page:
PCCTS - The Purdue Compiler Construction Tool Set
PCCTS is a set of public domain software tools designed to
facilitate the implementation of compilers and other
translation systems. These tools currently include antlr,
and dlg.
In many ways, PCCTS is similar to a highly integrated
version of YACC [Joh78] and LEX [Les75]; where antlr (ANother
Tool for Language Recognition) corresponds to YACC and dlg
(DFA-based Lexical analyzer Generator) functions like LEX.
However, PCCTS has many additional features which
make it easier to use for a wider range of translation
problems.
The Revision Control System (RCS) manages multiple revisions of files. RCS
automates the storing, retrieval, logging, identification, and merging of
revisions. RCS is useful for text that is revised frequently, including source
code, programs, documentation, graphics, papers, and form letters.
This port is gnu rcs.
pmccabe calculates McCabe-style cyclomatic complexity for C and C++
source code. Per-function complexity may be used for spotting likely
trouble spots and for estimating testing effort.
pmccabe also includes a non-commented line counter, decomment which
only removes comments from source code; codechanges, a program to
calculate the amount of change which has occurred between two source
trees or files; and vifn, to invoke vi given a function name rather
than a file name.