Ports Search

php-memoize is a PHP extension which transparently caches PHP functions, much like Perl's Memoize module. It comes with the following storage modules which can be enabled at compile time: - memory: Simple per-request module with no dependencies. Since this is a per-request cache, neither TTLs specified in the `memoize()` call or `memoize.default_ttl` are used. - memcached: Uses libmemcached or the memcached PHP extension

libshbuf implements a new kind of IPC: the "shared buffer", a faster, more flexible replacement for standard Unix FIFOs. It offers the following advantages: - Normally better latency and throughput - Full access to the buffer at any time - Connecting processes need not to be children of each other - Arbitrary buffer lengths - Memory mapped - "Backlog" The implementation is based on SysV shared memory, semaphores and message queues. It makes use of POSIX pthreads.

The GNU Binutils are a collection of binary tools. The main ones are: * ld - the GNU linker. * as - the GNU assembler. Most of these programs use BFD, the Binary File Descriptor library, to do low-level manipulation. Many of them also use the opcodes library to assemble and disassemble machine instructions. This port may be used as a replacement for the system binutils and support features from the latest versions of GCC. For cross-compilation, see the devel/cross-binutils port.

php-memoize is a PHP extension which transparently caches PHP functions, much like Perl's Memoize module. It comes with the following storage modules which can be enabled at compile time: - memory: Simple per-request module with no dependencies. Since this is a per-request cache, neither TTLs specified in the `memoize()` call or `memoize.default_ttl` are used. - memcached: Uses libmemcached or the memcached PHP extension

Parmap is a minimalistic library allowing to exploit multicore architecture for OCaml programs with minimal modifications: if you want to use your many cores to accelerate an operation which happens to be a map, fold or map/fold (map-reduce), just use Parmap's parmap, parfold and parmapfold primitives in place of the standard List.map and friends, and specify the number of subprocesses to use by the optional parameter ~ncores.

diStorm is a binary stream disassembler of x86 instructions. It can operate in 16, 32, and 64 bit modes, and supports FPU, MMX, SSE, SSE2, SSE3, SSE4, 3DNow! (with extensions), x86-64, VMX, AMD SVM, and AVX instruction sets. diStorm was written to decode every instruction quickly and accurately, with robust handling of valid and unused prefixes. The output is a special structure that can describe any x86 instruction, and later be formatted into text for display.

This is an abstract base class for objects backed by a socket which provides the basic framework for event-driven asynchronous IO, designed to be fast. Danga::Socket is both a base class for objects, and an event loop. Callers subclass Danga::Socket. Danga::Socket's constructor registers itself with the Danga::Socket event loop, and invokes callbacks on the object for readability, writability, errors, and other conditions.

This module can be used to more easily spot the place where a program or a module generates errors. Its use is extremely simple, reduced to just'use'ing it. This is achieved by modifying the functions warn() and die() in order to replace the standard messages by complete stack traces that precisely indicates how and where the error or warning occurred. Other than this, their use should stay unchanged, even when using die() inside eval().

IPC::Shareable allows you to tie a variable to shared memory making it easy to share the contents of that variable with other Perl processes. Currently either scalars or hashes can be tied; tying of arrays remains a work in progress. However, the variable being tied may contain arbitrarily complex data structures - including references to arrays, hashes of hashes, etc. See the "REFERENCES" entry in this man page below for more information.

MooseX::Emulate::Class::Accessor::Fast attempts to emulate the behavior of Class::Accessor::Fast as accurately as possible using the Moose attribute system. The public API of Class::Accessor::Fast is wholly supported, but the private methods are not. If you are only using the public methods (as you should) migration should be a matter of switching your "use base" line to a "with" line.