| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Upstream changes:
version 0.011; 2010-08-21
* bugfix: add a typemap entry for "const char *", to make XS version
of scalar_class() work correctly on Perl 5.6, having been broken by
the const fix in version 0.010
* in XS code, on Perls where it exists (prior to 5.9.5), treat SVt_PVBM
as a scalar referent type
version 0.010; 2010-08-20
* in XS, use PERL_NO_GET_CONTEXT for efficiency
* use full stricture in test suite
* also test POD coverage of pure Perl implementation
* in test suite, make all numeric comparisons against $] stringify it
first, to avoid architecture-dependent problems with floating point
rounding giving it an unexpected numeric value
* make XS code const clean for gcc -Wwrite-strings
* in Build.PL, explicitly set needs_compiler to avoid bogus
auto-dependency on ExtUtils::CBuilder
* in Build.PL, explicitly declare configure-time requirements
* add MYMETA.yml to .cvsignore
|
|
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.
The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.
sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
|
|
This module provides various type-testing functions. These are intended for
functions that, unlike most Perl code, care what type of data they are
operating on. For example, some functions wish to behave differently
depending on the type of their arguments (like overloaded functions in C++).
There are two flavours of function in this module. Functions of the first
flavour only provide type classification, to allow code to discriminate
between argument types. Functions of the second flavour package up the most
common type of type discrimination: checking that an argument is of an
expected type. The functions come in matched pairs, of the two flavours,
and so the type enforcement functions handle only the simplest requirements
for arguments of the types handled by the classification functions.
Enforcement of more complex types may, of course, be built using the
classification functions, or it may be more convenient to use a module
designed for the more complex job, such as Params::Validate.
|
