For the theory of Memoization, please see the Memoize module
documentation. This module implements an expiry policy for Memoize
that follows LRU semantics, that is, the last n results, where n
is specified as the argument to the CACHESIZE parameter, will be
cached.
This module always exports a single function, Dumper, which can be
called with an array of values to dump those values.
It exists, fundamentally, as a convenient way to reproduce a set
of Dumper options that we've found ourselves using across large
numbers of applications, primarily for debugging output.
The principle guiding theme is "all the concision you can get while
still having a useful dump and not doing anything cleverer than
setting Data::Dumper options" - it's been pointed out to us that
Data::Dump::Streamer can produce shorter output with less lines of
code. We know. This is simpler and we've never seen it segfault.
But for complex/weird structures, it generally rocks. You should
use it as well, when Concise is underkill. We do.
Why is deparsing on when the aim is concision? Because you often
want to know what subroutine refs you have when debugging and because
if you were planning to eval this back in you probably wanted to
remove subrefs first and add them back in a custom way anyway. Note
that this -does- force using the pure perl Dumper rather than the
XS one, but I've never in my life seen Data::Dumper show up in a
profile so "who cares?".
These flags types were originally incorrectly handled in glib as being
enums. That bug was fixed, but they're still enums here, leading to
warnings about the mismatch.
Change them to flags.
just set CONFIGURE_ARGS on mips64el, don't provide a way to build with
--english-only on other arch (as the only reason for using this seems to
be to work around compiler/toolchain problems). Avoids oddity with
out-of-date reported by fgsch@.
Also make sure the arch check is done after including bsd.port.arch.mk;
ARCH was in my environment when I tested before, sigh... this problem
reported by kili@.
"it's shorter than the previous version, so it's automagically ok" kili@ ;)
This extension provides a fiber/coroutine implementation for nodejs. It
also ships with a futures implementation that wraps existing nodejs
async functions, allowing synchronous style code that handles exceptions
properly and doesn't block the nodejs event loop.
OK sthen@
building support for other languages). Use it on mips64el by default
as ld(1) has trouble without it. Information from Brian Callahan and
Bryan Irvine.
- while there, prefer http MASTER_SITES
ok landry@
