The file is included via the do-FILE mechanism, which is essentially just a variety of eval with the caveat that lexical variables in the invoking script will be invisible to the included code. Otherwise, require demands that a library file be included if it hasn't already been included. Require 5.024_001 # ditto older syntax compatible Before perl 5.8.0 (released in 2002), the more verbose numeric form was the only supported syntax, which is why you might see it in older code. Specifying VERSION as a numeric argument of the form 5.024001 should generally be avoided as older less readable syntax compared to v5.24.1. Compare with use, which can do a similar check at compile time. An exception is raised if VERSION is greater than the version of the current Perl interpreter. I like the patch (except that Id prefer WARNOVERFLOW for the warning) > The other problem is that Perl is capable of storing much larger integers than > that (and indeed even larger numbers than PERLUINTMAX, through the use of > NVs), and the pure Perl version.pm code has to be carefully structured to > actually trigger the overflow (since. VERSION may be either a literal such as v5.24.1, which will be compared to $^V (or $PERL_VERSION in English), or a numeric argument of the form 5.024001, which will be compared to $]. When allow_ignored parameter is specified (with some non-empty value), the greatest version is always picked regardless of status.# require VERSION # require EXPR #requireĭemands a version of Perl specified by VERSION, or demands some semantics specified by EXPR or by $_ if EXPR is not supplied. īy default, when picking the version to show on badge, all rolling, noscheme, incorrect, untrusted, ignored versions are skipped (so, for instance, rolling 9999 versions in Gentoo do not hide real stable versions). Useful to mark unacceptable versions based on arbitrary criteria, for instance unsupported dependency versions. Specify "minimal acceptable version" - any versions lesser than it will be marked with crimson color. Specify empty header to remove it completely. Most badges may be tweaked by specifying additional parameters in the URL. May be tweaked with header, minversion, and allow_ignored parameters (see below). ![]() Pick as many as you want! You may add ?header= to the URL to leave only the version. These show version in specific repository. May be tweaked with header parameter (see below). These badges also support minversion= parameter. There may be multiple versions, for example devel and newest, or multiple variations of the same version encountered in some repositories (e.g. This shows latest version(s) known to repology. Tiny badge with latest packaged version(s) Debian Stable, Testing, Unstable and Experimental all belong to a single family and are thus only counted once. Repository family is an aggregation of related repositories, e.g. This shows total number of repository families featuring this package. Feel free to submit PRs with missing dates. Note however that this will only work for repositories which have end of life date ( valid_till) set in the configs. You may also exclude old and no longer supported repositories with exclude_unsupported=1 parameter. ![]() use exclude_sources=modules,site to exclude e.g. You may exclude specific kinds of sources ( repository, modules, site) with exclude_sources parameter. It's also possible to specify number of columns with columns= parameter. ![]() ![]() HTML code for right-aligned badge (most useful for README.md as it allows other content to flow around it not leading to space waste): This badge shows versions and up to date status of this project in all known repositories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |