?????????? ????????? - ??????????????? - /home/agenciai/public_html/cd38d8/README.md.tar
???????
home/.cpan/build/Test-Requires-0.11-0/README.md 0000664 00000003325 15125143316 0014305 0 ustar 00 # NAME Test::Requires - Checks to see if the module can be loaded # SYNOPSIS # in your Makefile.PL use inc::Module::Install; test_requires 'Test::Requires'; # in your test use Test::More tests => 10; use Test::Requires { 'HTTP::MobileAttribute' => 0.01, # skip all if HTTP::MobileAttribute doesn't installed }; isa_ok HTTP::MobileAttribute->new, 'HTTP::MobileAttribute::NonMobile'; # or use Test::More tests => 10; use Test::Requires qw( HTTP::MobileAttribute ); isa_ok HTTP::MobileAttribute->new, 'HTTP::MobileAttribute::NonMobile'; # or use Test::More tests => 10; use Test::Requires; test_requires 'Some::Optional::Test::Required::Modules'; isa_ok HTTP::MobileAttribute->new, 'HTTP::MobileAttribute::NonMobile'; # DESCRIPTION Test::Requires checks to see if the module can be loaded. If this fails rather than failing tests this **skips all tests**. Test::Requires can also be used to require a minimum version of Perl: use Test::Requires "5.010"; # quoting is necessary!! # or use Test::Requires "v5.10"; # AUTHOR Tokuhiro Matsuno <tokuhirom @\*(#RJKLFHFSDLJF gmail.com> # THANKS TO kazuho++ # some tricky stuff miyagawa++ # original code from t/TestPlagger.pm tomyhero++ # reported issue related older test::builder tobyink++ # documented that Test::Requires "5.010" works # ENVIRONMENT If the `RELEASE_TESTING` environment variable is true, then instead of skipping tests, Test::Requires bails out. # SEE ALSO ["TestPlagger.pm" in t](https://metacpan.org/pod/t#TestPlagger.pm) # LICENSE This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. home/.cpan/build/Data-Validate-IP-0.31-0/README.md 0000644 00000023161 15125143316 0014477 0 ustar 00 # NAME Data::Validate::IP - IPv4 and IPv6 validation methods # VERSION version 0.31 # SYNOPSIS use Data::Validate::IP qw(is_ipv4 is_ipv6); my $suspect = '1.2.3.4'; if (is_ipv4($suspect)) { print "Looks like an IPv4 address"; } else { print "Not an IPv4 address\n"; } $suspect = '::1234'; if (is_ipv6($suspect)) { print "Looks like an IPv6 address"; } else { print "Not an IPv6 address\n"; } # DESCRIPTION This module provides a number IP address validation subs that both validate and untaint their input. This includes both basic validation (`is_ipv4()` and `is_ipv6()`) and special cases like checking whether an address belongs to a specific network or whether an address is public or private (reserved). # USAGE AND SECURITY RECOMMENDATIONS It's important to understand that if `is_ipv4($ip)`, `is_ipv6($ip)`, or `is_ip($ip)` return false, then all other validation functions for that IP address family will _also_ return false. So for example, if `is_ipv4($ip)` returns false, then `is_private_ipv4($ip)` _and_ `is_public_ipv4($ip)` will both also return false. This means that simply calling `is_private_ipv4($ip)` by itself is not sufficient if you are dealing with untrusted input. You should always check `is_ipv4($ip)` as well. This applies as well when using IPv6 functions or generic functions like `is_private_ip($ip)`. There are security implications to this around certain oddly formed addresses. Notably, an address like "010.0.0.1" is technically valid, but the operating system will treat "010" as an octal number. That means that "010.0.0.1" is equivalent to "8.0.0.1", _not_ "10.0.0.1". However, this module's `is_ipv4($ip)` and `is_ip($ip)` functions will return false for addresses like "010.0.0.1" which have octal components. And of course that means that it also returns false for `is_private_ipv4($ip)` _and_ `is_public_ipv4($ip)`. # FUNCTIONS All of the functions below are exported by default. All functions return an untainted value if the test passes and undef if it fails. In theory, this means that you should always check for a defined status explicitly but in practice there are no valid IP addresses where the string form evaluates to false in Perl. Note that none of these functions actually attempt to test whether the given IP address is routable from your device; they are purely semantic checks. ## is\_ipv4($ip), is\_ipv6($ip), is\_ip($ip) These functions simply check whether the address is a valid IPv4 or IPv6 address. ## is\_innet\_ipv4($ip, $network) This subroutine checks whether the address belongs to the given IPv4 network. The `$network` argument can either be a string in CIDR notation like "15.0.15.0/24" or a [NetAddr::IP](https://metacpan.org/pod/NetAddr%3A%3AIP) object. This subroutine used to accept many more forms of network specifications (anything [Net::Netmask](https://metacpan.org/pod/Net%3A%3ANetmask) accepts) but this has been deprecated. ## is\_unroutable\_ipv4($ip) This subroutine checks whether the address belongs to any of several special use IPv4 networks - `0.0.0.0/8`, `100.64.0.0/10`, `192.0.0.0/29`, `198.18.0.0/15`, `240.0.0.0/4` - as defined by [RFC 5735](http://tools.ietf.org/html/rfc5735), [RFC 6333](http://tools.ietf.org/html/rfc6333), and [RFC 6958](http://tools.ietf.org/html/rfc6598). Arguably, these should be broken down further but this subroutine will always exist for backwards compatibility. ## is\_private\_ipv4($ip) This subroutine checks whether the address belongs to any of the private IPv4 networks - `10.0.0.0/8`, `172.16.0.0/12`, `192.168.0.0/16` - as defined by [RFC 5735](http://tools.ietf.org/html/rfc5735). ## is\_loopback\_ipv4($ip) This subroutine checks whether the address belongs to the IPv4 loopback network \- `127.0.0.0/8` - as defined by [RFC 5735](http://tools.ietf.org/html/rfc5735). ## is\_linklocal\_ipv4($ip) This subroutine checks whether the address belongs to the IPv4 link local network - `169.254.0.0/16` - as defined by [RFC 5735](http://tools.ietf.org/html/rfc5735). ## is\_testnet\_ipv4($ip) This subroutine checks whether the address belongs to any of the IPv4 TEST-NET networks for use in documentation and example code - `192.0.2.0/24`, `198.51.100.0/24`, and `203.0.113.0/24` - as defined by [RFC 5735](http://tools.ietf.org/html/rfc5735). ## is\_anycast\_ipv4($ip) This subroutine checks whether the address belongs to the 6to4 relay anycast network - `192.88.99.0/24` - as defined by [RFC 5735](http://tools.ietf.org/html/rfc5735). ## is\_multicast\_ipv4($ip) This subroutine checks whether the address belongs to the IPv4 multicast network - `224.0.0.0/4` - as defined by [RFC 5735](http://tools.ietf.org/html/rfc5735). ## is\_loopback\_ipv6($ip) This subroutine checks whether the address is the IPv6 loopback address - `::1/128` - as defined by [RFC 4291](http://tools.ietf.org/html/rfc4291). ## is\_ipv4\_mapped\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 IPv4-mapped address network - `::ffff:0:0/96` - as defined by [RFC 4291](http://tools.ietf.org/html/rfc4291). ## is\_discard\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 discard prefix network - `100::/64` - as defined by [RFC 6666](http://tools.ietf.org/html/rfc6666). ## is\_special\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 special network \- `2001::/23` - as defined by [RFC 2928](http://tools.ietf.org/html/rfc2928). ## is\_teredo\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 TEREDO network - `2001::/32` - as defined by [RFC 4380](http://tools.ietf.org/html/rfc4380). Note that this network is a subnet of the larger special network at `2001::/23`. ## is\_orchid\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 ORCHID network - `2001::/32` - as defined by [RFC 4380](http://tools.ietf.org/html/rfc4380). Note that this network is a subnet of the larger special network at `2001::/23`. This network is currently scheduled to be returned to the special pool in March of 2014 unless the IETF extends its use. If that happens this subroutine will continue to exist but will always return false. ## is\_documentation\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 documentation network - `2001:DB8::/32` - as defined by [RFC 3849](http://tools.ietf.org/html/rfc3849). ## is\_unspecified\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 unspecified network - `::0/128` - as defined by [RFC 4291](http://tools.ietf.org/html/rfc4291).. Note that the address in this subnet is neither private nor public. ## is\_private\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 private network \- `FC00::/7` - as defined by [RFC 4193](http://tools.ietf.org/html/rfc4193). ## is\_linklocal\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 link-local unicast network - `FE80::/10` - as defined by [RFC 4291](http://tools.ietf.org/html/rfc4291). ## is\_multicast\_ipv6($ip) This subroutine checks whether the address belongs to the IPv6 multicast network - `FF00::/8` - as defined by [RFC 4291](http://tools.ietf.org/html/rfc4291). ## is\_public\_ipv4($ip), is\_public\_ipv6($ip), is\_public\_ip($ip) These subroutines check whether the given IP address belongs to any of the special case networks defined previously. Note that this is **not** simply the opposite of checking `is_private_ipv4()` or `is_private_ipv6()`. The private networks are a subset of all the special case networks. ## is\_linklocal\_ip($ip) This subroutine checks whether the address belongs to the IPv4 or IPv6 link-local unicast network. ## is\_loopback\_ip($ip) This subroutine checks whether the address is the IPv4 or IPv6 loopback address. ## is\_multicast\_ip($ip) This subroutine checks whether the address belongs to the IPv4 or IPv6 multicast network. ## is\_private\_ip($ip) This subroutine checks whether the address belongs to the IPv4 or IPv6 private network. # OBJECT-ORIENTED INTERFACE This module can also be used as a class. You can call `Data::Validate::IP->new()` to get an object and then call any of the validation subroutines as methods on that object. This is somewhat pointless since the object will never contain any state but this interface is kept for backwards compatibility. # SEE ALSO IPv4 **\[RFC 5735\] \[RFC 1918\]** IPv6 **\[RFC 2460\] \[RFC 4193\] \[RFC 4291\] \[RFC 6434\]** # ACKNOWLEDGEMENTS Thanks to Richard Sonnen <`sonnen@richardsonnen.com`> for writing the Data::Validate module. Thanks to Matt Dainty <`matt@bodgit-n-scarper.com`> for adding the `is_multicast_ipv4()` and `is_linklocal_ipv4()` code. # BUGS Please report any bugs or feature requests to `bug-data-validate-ip@rt.cpan.org`, or through the web interface at [http://rt.cpan.org](http://rt.cpan.org). I will be notified, and then you'll automatically be notified of progress on your bug as I make changes. Bugs may be submitted at [https://github.com/houseabsolute/Data-Validate-IP/issues](https://github.com/houseabsolute/Data-Validate-IP/issues). # SOURCE The source code repository for Data-Validate-IP can be found at [https://github.com/houseabsolute/Data-Validate-IP](https://github.com/houseabsolute/Data-Validate-IP). # AUTHORS - Neil Neely <neil@neely.cx> - Dave Rolsky <autarch@urth.org> # CONTRIBUTOR Gregory Oschwald <goschwald@maxmind.com> # COPYRIGHT AND LICENSE This software is copyright (c) 2022 by Neil Neely. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. The full text of the license can be found in the `LICENSE` file included with this distribution. home/.cpan/build/Template-Toolkit-3.102-0/README.md 0000644 00000031527 15125143332 0015054 0 ustar 00 [](https://github.com/abw/Template2/actions) [](https://github.com/abw/Template2/actions) # Template Toolkit Version 3.102, August 2022 Copyright (C) 1996-2022 Andy Wardley. All Rights Reserved This is free software; you can redistribute it and/or modify it under the same terms as Perl itself. # Installation If you have the CPAN module installed then you can install the Template Toolkit from the command line like so: $ cpan Template Please see the separate INSTALL file for further information on installing the Template Toolkit, including what to do if you don't have the CPAN module installed, and/or installation on MS Windows. # Description The Template Toolkit is a collection of modules which implement a fast, flexible, powerful and extensible template processing system. It was originally designed and remains primarily useful for generating dynamic web content, but it can be used equally well for processing any other kind of text based documents: HTML, XML, POD, PostScript, LaTeX, and so on. It can be used as a stand-alone Perl module or embedded within an Apache/mod_perl server for generating highly configurable dynamic web content. A number of Perl scripts are also provided which can greatly simplify the process of creating and managing static web content and other offline document systems. # What's New? Version 3.102 Various performance improvements. Update docs on complex keys. Remove unncessary imports for modern Perls. Version 3.101 Added meta() method to Template::Document and fixed incorrect line numbers when using outline tags Version 3.100 Maintenance release: several fixes, documentation improvements and ttree updates. Version 3.009 revert "Allow SET to have FILTER used in it" Version 3.008 fixes some testing issue with CGI and taint issues. Version 3.007 fixes a cpanm issue. Version 3.006 adds an encoding option to Datafile plugin and refresh the contributor list and copyrights for 2020. Version 3.004 enforced three-args open. Version 3.003 fixes some compatibility issues with several Plugins. Version 3.002 is a maintenance release fixing a warning during install. Version 3.001 officially drops Perl 5.6 support. Version 3.000 provides several performance improvements. Version 2.29 is a maintenance release fixing a cycling weaken issue. Version 2.28 is a maintenance release fixing some minor bugs and warnings. GitHub is now the official bug tacker tool for the project. Version 2.27 is a maintenance release fixing some minor bugs and warnings. Version 2.26 adds the new outline tag style and fixes various minor bugs. Version 2.25 fixes compatibility with Perl version 5.18 and fixes a numer of other minor bugs, typos, etc. Version 2.24 adds some new text virtual methods and fixes a silly bug in the Makefile.PL. Version 2.23 is a maintenance release which fixes a few bugs, including one in the XS Stash which caused problems when using third party modules (e.g. DateTime) which use the string-based form of eval. Version 2.22 is mostly a bug fixing release. The XS Stash now works with utf8 data. Tests that were failing on Win32 platforms have been fixed. Pod coverage and quality tests have been disabled except for release testing. The Autoformat plugin has been moved into a separate distribution. Version 2.21 featured a complete clean-out of all the old HTML documentation, examples, libraries and other cruft that was way out of date and badly unloved. A new version of the HTML documentation is available for download from http://tt2.org/download/index.html#html_docs. v2.21 also fixes a memory leak in the XS Stash. Version 2.21 also adds the STRICT option which reports the use of undefined variable values. The ANYCASE option has been improved so that you can write things like 'data.last' without the 'last' bit being interpreted as the LAST keyword. The xml filter is also new, providing a slightly more rigourous version of the html filter for use in XML documents. Version 2.20 fixed all known bugs. It also added the Scalar and Assert plugins. The HTML documentation, examples, libraries and other bits and pieces are still provided with the distribution, but are no longer installed by the Makefile.PL. If you want them (and very few people do, it seems), then you'll need to dig them out of the distribution by yourself (or uncomment the commented-out lines in Makefile.PL that handle the installation). This has been done in an effort to simplify the installation process. All of the HTML documentation is available online at http://tt2.org/ Version 2.19 fixed some minor bugs in both Perl and XS versions of the Template Stash, and fixed a problem with a test in the test suite failing under Win32. It also added the url filter as a version of what the uri filter used to do before we fixed it to do the right thing. Version 2.18 fixes a number of minor bugs. It also includes a modification to the parser grammar so that you can write expressions as arguments to subroutine, method or vmethod calls. Versions 2.17 and 2.16 were interim releases by Adam Kennedy who took care of some installation problems on Mac OSX while Andy was busy elsewhere. Version 2.15 is a major maintenance release. It applies all outstanding patches and closes all open bugs listed on http://rt.cpan.org/ It includes: * XS Stash: enhancements include support for tied hashes/arrays and "fallback" methods on objects (e.g. accessing hash and list items and calling virtual methods) * Virtual Methods: added the scalar.remove, scalar.substr, hash.delete, hash.items, hash.pairs, list.import and list.hash virtual methods. Added support for backreferences to scalar.replace and other improvements to list.push, list.unshift, list.hash, hash.list * Plugins: Added Math plugin, Bug fixes and enhancements to File, Image, URL and String plugins. Moved DBI, XML and GD plugins into separate distributions. * Numerous other bug fixes, enhancements, documentation updates, all described in detail in the Changes file. More significant is what's not in version 2.15. The DBI plugin has been moved into a separate Template-DBI distribution, the GD plugins into Template-GD, the XML plugins into Template-XML, and the Latex filters into Template-Latex. This has been done in an effort to make the Template Toolkit core distribution smaller, cleaner and easier to configure and install. Version 2.14 added Unicode support to TT, a full set of command line options for tpage, the 'caller' and 'callers' items to each template component, some enhancements to the XML::Simple plugin, and a number of minor bug fixes. See the Changes file for further details of the changes in these and earlier releases. # General Features Some of the key features of the Template Toolkit are listed below. See the documentation for further detail. * simple but powerful template language * promotes a clear separation between application functionality and presentation elements * variable substitution allows binding to any Perl data types (scalars, hashes, lists, subs, objects) * conditional blocks (IF/UNLESS/ELSIF/ELSE, SWITCH/CASE) * loops and iterators (FOREACH, WHILE) * file/template inclusion (INSERT, INCLUDE, PROCESS, WRAPPER) * definition of local template components (BLOCK) * post-processing filters (FILTER) * plugin module architecture for easy extensibility (USE) * embedded Perl can be optionally enabled (PERL/RAWPERL) * full exception handling (TRY/THROW/CATCH/FINAL) * user-defined macros (MACRO) * definition of template metadata (META) * virtual methods for complex data types (e.g. list.size, hash.keys, etc.) * numerous configuration options * modular OO architecture allows extensive customisation * fast LALR(1) parser modules compiles templates according to a YACC-like grammar. * templates compiled to Perl code for efficient runtime execution * in-memory and on-disk caching of compiled templates * simple front end module (Template.pm) for ease of use * numerous plugin modules: CGI, DBI, XML, URL, Date, Table, etc * standard filters for html, case folding, regex search and replace, etc. # Documentation The Template Toolkit is provided with enough documentation to keep all but the most voracious reader happy for quite some time. The 'Changes' file in the distribution directory documents all visible changes between versions of the Template Toolkit. See the section 'VERSION COMPATABILITY' below for further details. The 'TODO' file, also in the distribution directory, lists known bugs, planned enhancements and possible new features for future versions. The 'INSTALL' file covers the configuration and installation process. The rest of the documentation is distributed in Pod format. The Pod pages are installed when you 'make install' and can be viewed using 'perldoc', e.g. perldoc Template If you're using a Unix based system then the pages should also be converted to manpages during 'make install'. Thus, you can also: man Template (the man pages shouldn't have any problems relating to older versions) The documentation is also available in HTML format at the TT web site: http://tt2.org/docs/ The documentation is now split into several sections. The 'Template' page is now much shorter, containing information relating to the specifics of using the Template module, and a brief summary of everything else. Information relating more generally to the Template Toolkit, features, syntax of the template language, plugins and so forth, has been split up into a number of Template::Manual::* pages. Template::Manual provides the index for the manual. perldoc Template::Manual Individual sections can be viewed as, for example, perldoc Template::Manual::Syntax perldoc Template::Manual::Directives perldoc Template::Manual::Plugins The Template::Tutorial provides an index to the tutorial documents. There are currently 2 tutorials, on generating web content, and on creating and using data files. perldoc Template::Tutorial perldoc Template::Tutorial::Web perldoc Template::Tutorial::Datafile Each of the various modules that comprise the Template Toolkit has its own associated documention. The 'Template::Modules' manpage lists these modules along with a brief description of their functions. perldoc Template::Modules See the individual pages for further detail: perldoc Template::Context perldoc Template::Parser perldoc Template::Provider If you're interested in the internals of the Template Toolkit and want to know more about how it all works, then you might like to have a look at the following: perldoc Template::Manual::Internals This document also contains important information for people wishing to hack on the Template Toolkit. The final bit of good news is that there is now a FAQ for the Template Toolkit. perldoc Template::FAQ It's now got a few question in it, and better still, some answers! Further contributions welcome. Most of the documentation is stable and reliable. Where it's not then it's usually marked as such. In particular, the documentation for the internals (Template::Manual::Internals) and FAQ (Template::FAQ) are perpetually under construction. # Source Code The source code for the Template Toolkit is maintained in a public git repository at github: https://github.com/abw/Template2 If you want to hack on the source code, either to fix a bug or add a feature then you should fork the repository, make the changes, commit them, and then send me a pull request. See this guide for further information. http://help.github.com/send-pull-requests/ Any non-trivial new features should be discussed on the Template Toolkit mailing list first (see below). Don't forget to update the documentation and tests where relevant # Support The Template Toolkit mailing list provides a forum for discussing issues relating to the use and abuse of the Template Toolkit. There are a number of knowledgeable and helpful individuals who frequent the list (including the author) who can often offer help or suggestions. Please respect their time and patience by checking the documentation and/or mailing list archives before asking questions that may already have been answered. To subscribe to the mailing list, send an email to: template-toolkit+subscribe@groups.io You can also use the web interface: https://groups.io/g/template-toolkit For information about commercial support and consultancy for the Template Toolkit, please contact the author. # Author The Template Toolkit was written by Andy Wardley <abw@wardley.org> with the invaluable assistance and contributions from many other people. See Template::Manual::Credits for details. # Copyright Copyright (C) 1996-2022 Andy Wardley. All Rights Reserved. This is free software; you can redistribute it and/or modify it under the same terms as Perl itself. home/.cpan/build/DBD-mysql-5.009-0/README.md 0000644 00000002050 15125143507 0013413 0 ustar 00 [](https://github.com/perl5-dbi/DBD-mysql/actions/workflows/ci.yml) # DBD::mysql - database driver for Perl This is the Perl [DBI](https://metacpan.org/pod/DBI) driver for access to MySQL and MySQL Compatible databases. ## Usage Usage is described in [DBD::mysql](https://metacpan.org/pod/DBD::mysql). ## Building and Testing For building DBD::mysql you need a MySQL 8.x or newer client library. ``` perl Makefile.PL make make test ``` See the output of `perl Makefile.PL` for how to set database credentials. Testing is also done via GitHub action. ## Installation Installation is described in [DBD::mysql::INSTALL](https://metacpan.org/pod/DBD::mysql::INSTALL). ## Support This module is maintained and supported on a mailing list, dbi-users. To subscribe to this list, send an email to dbi-users-subscribe@perl.org Mailing list archives are at [http://groups.google.com/group/perl.dbi.users](http://groups.google.com/group/perl.dbi.users)
| ver. 1.6 |
Github
|
.
| PHP 8.2.30 | ??????????? ?????????: 0 |
proxy
|
phpinfo
|
???????????