There are a number of different situations (like testing caching code)
where you want to want to do a number of tests, and then verify that
some underlying subroutine deep within the code was called a specific
number of times.
ok ajacoutot@
From maintainer Abel Abraham Camarillo Ojeda
Dump in hexadecimal the content of a scalar. The result is returned
in a string. Each line of the result consists of the offset in the
source in the leftmost column of each line, followed by one or more
columns of data from the source in hexadecimal. The rightmost column
of each line shows the printable characters (all others are shown
as single dots).
Manipulating stashes (Perl's symbol tables) is occasionally necessary,
but incredibly messy, and easy to get wrong. This module hides all of
that behind a simple API.
ok ajacoutot@
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 seperate 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.
"go ahead, please" espie@
used by the Pugs project for handling data serialization; this can
be useful for optimization and caching purposes.
This is an interface to the syck C library for parsing and dumping
YAML data. It lets you transform textual YAML data into an object
of type 'YamlNode', and vice versa, fast.
"go ahead, please" espie@
allow the use of paths relative to it. FindBin supports invocation
of Haskell programs via "ghci", via "runhaskell/runghc", as well
as compiled as an executable.
"to ahead, please" espie@
GIO Reference Manual:
gio-querymodules creates a giomodule.cache listing the implemented
extension points for each module that has been found. It is used by GIO
at runtime to avoid opening all modules just to find out which extension
points they are implementing.
