- validate_pos used exists on an array element, which only works with
5.6.0. This releaes makes it work 5.00503 again.
- the validation parameters are checked first now
- performance improved on named parameters
- add BOOLEAN type (equivalent to UNDEF | SCALAR)
- fixed buges in test
- apply some of the same optimizations to positional parameters
- The 'NO_VALIDATION' mode was seriously broken in that it didn't
handle defaults at all.
- The 'NO_VALIDATION' env var was mis-documented as being
'NO_VALIDATE'.
- The 'NO_VALIDATION' env var is now 'PERL_NO_VALIDATION' and this
method of disabling validation is no longer considered alpha.
- The validation functions now check this environment variable every
time they are called.
- Fix problem with CPAN shell's 'r' command that
Attribute::Params::Validate was causing with older Perl's.
- Add ability to specify defaults for parameters and get a new
hash/array back from validate or validate_pos.
- Require Attribute::Handlers if using Perl 5.6.0+.
- fix doc nits.
- Added Attribute::Params::Validate - do validation via attributes
- Rename set_options to validation_options. This can now be exported
safely and is included in the :all export tag. set_options is
deprecated and will be removed in a future release.
Also fixes PR/15225 by Shell Hung.
The automatic truncation in gensolpkg doesn't work for packages which
have the same package name for the first 5-6 chars.
e.g. amanda-server and amanda-client would be named amanda and amanda.
Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for
amanda-server.
All svr4 packages also have a vendor tag, so we have to reserve some chars
for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6
or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the
vendor tag enough room.
All p5-* packages and a few other packages have now a SVR4_PKGNAME.
The Params::Validate module provides a flexible system for validation
method/function call parameters. The validation can be as simple as
checking for the presence of required parameters or as complex as
validating object classes (via isa) or capabilities (via can),
checking parameter types, and using customized callbacks to ensure
data integrity.
