{
    "mode": "man",
    "parameter": "perldiag",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/perldiag/1/json",
    "generated": "2026-06-15T13:39:36Z",
    "sections": {
        "NAME": {
            "content": "perldiag - various Perl diagnostics\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "These messages are classified as follows (listed in increasing order of desperation):\n\n(W) A warning (optional).\n(D) A deprecation (enabled by default).\n(S) A severe warning (enabled by default).\n(F) A fatal error (trappable).\n(P) An internal error you should never see (trappable).\n(X) A very fatal error (nontrappable).\n(A) An alien error message (not generated by Perl).\n\nThe majority of messages from the first three classifications above (W, D & S) can be\ncontrolled using the \"warnings\" pragma.\n\nIf a message can be controlled by the \"warnings\" pragma, its warning category is included\nwith the classification letter in the description below.  E.g. \"(W closed)\" means a warning\nin the \"closed\" category.\n\nOptional warnings are enabled by using the \"warnings\" pragma or the -w and -W switches.\nWarnings may be captured by setting $SIG{WARN} to a reference to a routine that will be\ncalled on each warning instead of printing it.  See perlvar.\n\nSevere warnings are always enabled, unless they are explicitly disabled with the \"warnings\"\npragma or the -X switch.\n\nTrappable errors may be trapped using the eval operator.  See \"eval\" in perlfunc.  In almost\nall cases, warnings may be selectively disabled or promoted to fatal errors using the\n\"warnings\" pragma.  See warnings.\n\nThe messages are in alphabetical order, without regard to upper or lower-case.  Some of these\nmessages are generic.  Spots that vary are denoted with a %s or other printf-style escape.\nThese escapes are ignored by the alphabetical order, as are all characters other than\nletters.  To look up your message, just ignore anything that is not a letter.\n\naccept() on closed socket %s\n(W closed) You tried to do an accept on a closed socket.  Did you forget to check the\nreturn value of your socket() call?  See \"accept\" in perlfunc.\n\nAliasing via reference is experimental\n(S experimental::refaliasing) This warning is emitted if you use a reference constructor\non the left-hand side of an assignment to alias one variable to another.  Simply suppress\nthe warning if you want to use the feature, but know that in doing so you are taking the\nrisk of using an experimental feature which may change or be removed in a future Perl\nversion:\n\nno warnings \"experimental::refaliasing\";\nuse feature \"refaliasing\";\n\\$x = \\$y;\n\nAllocation too large: %x\n(X) You can't allocate more than 64K on an MS-DOS machine.\n\n'%c' allowed only after types %s in %s\n(F) The modifiers '!', '<' and '>' are allowed in pack() or unpack() only after certain\ntypes.  See \"pack\" in perlfunc.\n\nalpha->numify() is lossy\n(W numeric) An alpha version can not be numified without losing information.\n\nAmbiguous call resolved as CORE::%s(), qualify as such or use &\n(W ambiguous) A subroutine you have declared has the same name as a Perl keyword, and you\nhave used the name without qualification for calling one or the other.  Perl decided to\ncall the builtin because the subroutine is not imported.\n\nTo force interpretation as a subroutine call, either put an ampersand before the\nsubroutine name, or qualify the name with its package.  Alternatively, you can import the\nsubroutine (or pretend that it's imported with the \"use subs\" pragma).\n\nTo silently interpret it as the Perl operator, use the \"CORE::\" prefix on the operator\n(e.g. \"CORE::log($x)\") or declare the subroutine to be an object method (see \"Subroutine\nAttributes\" in perlsub or attributes).\n\nAmbiguous range in transliteration operator\n(F) You wrote something like \"tr/a-z-0//\" which doesn't mean anything at all.  To include\na \"-\" character in a transliteration, put it either first or last.  (In the past,\n\"tr/a-z-0//\" was synonymous with \"tr/a-y//\", which was probably not what you would have\nexpected.)\n\nAmbiguous use of %s resolved as %s\n(S ambiguous) You said something that may not be interpreted the way you thought.\nNormally it's pretty easy to disambiguate it by supplying a missing quote, operator,\nparenthesis pair or declaration.\n\nAmbiguous use of -%s resolved as -&%s()\n(S ambiguous) You wrote something like \"-foo\", which might be the string \"-foo\", or a\ncall to the function \"foo\", negated.  If you meant the string, just write \"-foo\".  If you\nmeant the function call, write \"-foo()\".\n\nAmbiguous use of %c resolved as operator %c\n(S ambiguous) \"%\", \"&\", and \"*\" are both infix operators (modulus, bitwise and, and\nmultiplication) and initial special characters (denoting hashes, subroutines and\ntypeglobs), and you said something like \"*foo * foo\" that might be interpreted as either\nof them.  We assumed you meant the infix operator, but please try to make it more clear\n-- in the example given, you might write \"*foo * foo()\" if you really meant to multiply a\nglob by the result of calling a function.\n\nAmbiguous use of %c{%s} resolved to %c%s\n(W ambiguous) You wrote something like \"@{foo}\", which might be asking for the variable\n@foo, or it might be calling a function named foo, and dereferencing it as an array\nreference.  If you wanted the variable, you can just write @foo.  If you wanted to call\nthe function, write \"@{foo()}\" ... or you could just not have a variable and a function\nwith the same name, and save yourself a lot of trouble.\n\nAmbiguous use of %c{%s[...]} resolved to %c%s[...]\nAmbiguous use of %c{%s{...}} resolved to %c%s{...}\n(W ambiguous) You wrote something like \"${foo[2]}\" (where foo represents the name of a\nPerl keyword), which might be looking for element number 2 of the array named @foo, in\nwhich case please write $foo[2], or you might have meant to pass an anonymous arrayref to\nthe function named foo, and then do a scalar deref on the value it returns.  If you meant\nthat, write \"${foo([2])}\".\n\nIn regular expressions, the \"${foo[2]}\" syntax is sometimes necessary to disambiguate\nbetween array subscripts and character classes.  \"/$length[2345]/\", for instance, will be\ninterpreted as $length followed by the character class \"[2345]\".  If an array subscript\nis what you want, you can avoid the warning by changing \"/${length[2345]}/\" to the\nunsightly \"/${\\$length[2345]}/\", by renaming your array to something that does not\ncoincide with a built-in keyword, or by simply turning off warnings with \"no warnings\n'ambiguous';\".\n\n'|' and '<' may not both be specified on command line\n(F) An error peculiar to VMS.  Perl does its own command line redirection, and found that\nSTDIN was a pipe, and that you also tried to redirect STDIN using '<'.  Only one STDIN\nstream to a customer, please.\n\n'|' and '>' may not both be specified on command line\n(F) An error peculiar to VMS.  Perl does its own command line redirection, and thinks you\ntried to redirect stdout both to a file and into a pipe to another command.  You need to\nchoose one or the other, though nothing's stopping you from piping into a program or Perl\nscript which 'splits' output into two streams, such as\n\nopen(OUT,\">$ARGV[0]\") or die \"Can't write to $ARGV[0]: $!\";\nwhile (<STDIN>) {\nprint;\nprint OUT;\n}\nclose OUT;\n\nApplying %s to %s will act on scalar(%s)\n(W misc) The pattern match (\"//\"), substitution (\"s///\"), and transliteration (\"tr///\")\noperators work on scalar values.  If you apply one of them to an array or a hash, it will\nconvert the array or hash to a scalar value (the length of an array, or the population\ninfo of a hash) and then work on that scalar value.  This is probably not what you meant\nto do.  See \"grep\" in perlfunc and \"map\" in perlfunc for alternatives.\n\nArg too short for msgsnd\n(F) msgsnd() requires a string at least as long as sizeof(long).\n\nArgument \"%s\" isn't numeric%s\n(W numeric) The indicated string was fed as an argument to an operator that expected a\nnumeric value instead.  If you're fortunate the message will identify which operator was\nso unfortunate.\n\nNote that for the \"Inf\" and \"NaN\" (infinity and not-a-number) the definition of \"numeric\"\nis somewhat unusual: the strings themselves (like \"Inf\") are considered numeric, and\nanything following them is considered non-numeric.\n\nArgument list not closed for PerlIO layer \"%s\"\n(W layer) When pushing a layer with arguments onto the Perl I/O system you forgot the )\nthat closes the argument list.  (Layers take care of transforming data between external\nand internal representations.)  Perl stopped parsing the layer list at this point and did\nnot attempt to push this layer.  If your program didn't explicitly request the failing\noperation, it may be the result of the value of the environment variable PERLIO.\n\nArgument \"%s\" treated as 0 in increment (++)\n(W numeric) The indicated string was fed as an argument to the \"++\" operator which\nexpects either a number or a string matching \"/^[a-zA-Z]*[0-9]*\\z/\".  See \"Auto-increment\nand Auto-decrement\" in perlop for details.\n\nArray passed to stat will be coerced to a scalar%s\n(W syntax) You called stat() on an array, but the array will be coerced to a scalar - the\nnumber of elements in the array.\n\nA signature parameter must start with '$', '@' or '%'\n(F) Each subroutine signature parameter declaration must start with a valid sigil; for\nexample:\n\nsub foo ($a, $, $b = 1, @c) {}\n\nA slurpy parameter may not have a default value\n(F) Only scalar subroutine signature parameters may have a default value; for example:\n\nsub foo ($a = 1)        {} # legal\nsub foo (@a = (1))      {} # invalid\nsub foo (%a = (a => b)) {} # invalid\n\nassertion botched: %s\n(X) The malloc package that comes with Perl had an internal failure.\n\nAssertion %s failed: file \"%s\", line %d\n(X) A general assertion failed.  The file in question must be examined.\n\nAssigned value is not a reference\n(F) You tried to assign something that was not a reference to an lvalue reference (e.g.,\n\"\\$x = $y\").  If you meant to make $x an alias to $y, use \"\\$x = \\$y\".\n\nAssigned value is not %s reference\n(F) You tried to assign a reference to a reference constructor, but the two references\nwere not of the same type.  You cannot alias a scalar to an array, or an array to a hash;\nthe two types must match.\n\n\\$x = \\@y;  # error\n\\@x = \\%y;  # error\n$y = [];\n\\$x = $y;   # error; did you mean \\$y?\n\nAssigning non-zero to $[ is no longer possible\n(F) When the \"arraybase\" feature is disabled (e.g., and under \"use v5.16;\", and as of\nPerl 5.30) the special variable $[, which is deprecated, is now a fixed zero value.\n\nAssignment to both a list and a scalar\n(F) If you assign to a conditional operator, the 2nd and 3rd arguments must either both\nbe scalars or both be lists.  Otherwise Perl won't know which context to supply to the\nright side.\n\nAssuming NOT a POSIX class since %s in regex; marked by <-- HERE in m/%s/\n(W regexp) You had something like these:\n\n[[:alnum]]\n[[:digit:xyz]\n\nThey look like they might have been meant to be the POSIX classes \"[:alnum:]\" or\n\"[:digit:]\".  If so, they should be written:\n\n[[:alnum:]]\n[[:digit:]xyz]\n\nSince these aren't legal POSIX class specifications, but are legal bracketed character\nclasses, Perl treats them as the latter.  In the first example, it matches the characters\n\":\", \"[\", \"a\", \"l\", \"m\", \"n\", and \"u\".\n\nIf these weren't meant to be POSIX classes, this warning message is spurious, and can be\nsuppressed by reordering things, such as\n\n[[al:num]]\n\nor\n\n[[:munla]]\n\n<> at require-statement should be quotes\n(F) You wrote \"require <file>\" when you should have written \"require 'file'\".\n\nAttempt to access disallowed key '%s' in a restricted hash\n(F) The failing code has attempted to get or set a key which is not in the current set of\nallowed keys of a restricted hash.\n\nAttempt to bless into a freed package\n(F) You wrote \"bless $foo\" with one argument after somehow causing the current package to\nbe freed.  Perl cannot figure out what to do, so it throws up its hands in despair.\n\nAttempt to bless into a reference\n(F) The CLASSNAME argument to the bless() operator is expected to be the name of the\npackage to bless the resulting object into.  You've supplied instead a reference to\nsomething: perhaps you wrote\n\nbless $self, $proto;\n\nwhen you intended\n\nbless $self, ref($proto) || $proto;\n\nIf you actually want to bless into the stringified version of the reference supplied, you\nneed to stringify it yourself, for example by:\n\nbless $self, \"$proto\";\n\nAttempt to clear deleted array\n(S debugging) An array was assigned to when it was being freed.  Freed values are not\nsupposed to be visible to Perl code.  This can also happen if XS code calls \"avclear\"\nfrom a custom magic callback on the array.\n\nAttempt to delete disallowed key '%s' from a restricted hash\n(F) The failing code attempted to delete from a restricted hash a key which is not in its\nkey set.\n\nAttempt to delete readonly key '%s' from a restricted hash\n(F) The failing code attempted to delete a key whose value has been declared readonly\nfrom a restricted hash.\n\nAttempt to free non-arena SV: 0x%x\n(S internal) All SV objects are supposed to be allocated from arenas that will be garbage\ncollected on exit.  An SV was discovered to be outside any of those arenas.\n\nAttempt to free nonexistent shared string '%s'%s\n(S internal) Perl maintains a reference-counted internal table of strings to optimize the\nstorage and access of hash keys and other strings.  This indicates someone tried to\ndecrement the reference count of a string that can no longer be found in the table.\n\nAttempt to free temp prematurely: SV 0x%x\n(S debugging) Mortalized values are supposed to be freed by the freetmps() routine.\nThis indicates that something else is freeing the SV before the freetmps() routine gets\na chance, which means that the freetmps() routine will be freeing an unreferenced scalar\nwhen it does try to free it.\n\nAttempt to free unreferenced glob pointers\n(S internal) The reference counts got screwed up on symbol aliases.\n\nAttempt to free unreferenced scalar: SV 0x%x\n(S internal) Perl went to decrement the reference count of a scalar to see if it would go\nto 0, and discovered that it had already gone to 0 earlier, and should have been freed,\nand in fact, probably was freed.  This could indicate that SvREFCNTdec() was called too\nmany times, or that SvREFCNTinc() was called too few times, or that the SV was\nmortalized when it shouldn't have been, or that memory has been corrupted.\n\nAttempt to pack pointer to temporary value\n(W pack) You tried to pass a temporary value (like the result of a function, or a\ncomputed expression) to the \"p\" pack() template.  This means the result contains a\npointer to a location that could become invalid anytime, even before the end of the\ncurrent statement.  Use literals or global values as arguments to the \"p\" pack() template\nto avoid this warning.\n\nAttempt to reload %s aborted.\n(F) You tried to load a file with \"use\" or \"require\" that failed to compile once already.\nPerl will not try to compile this file again unless you delete its entry from %INC.  See\n\"require\" in perlfunc and \"%INC\" in perlvar.\n\nAttempt to set length of freed array\n(W misc) You tried to set the length of an array which has been freed.  You can do this\nby storing a reference to the scalar representing the last index of an array and later\nassigning through that reference.  For example\n\n$r = do {my @a; \\$#a};\n$$r = 503\n\nAttempt to use reference as lvalue in substr\n(W substr) You supplied a reference as the first argument to substr() used as an lvalue,\nwhich is pretty strange.  Perhaps you forgot to dereference it first.  See \"substr\" in\nperlfunc.\n\nAttribute prototype(%s) discards earlier prototype attribute in same sub\n(W misc) A sub was declared as sub foo : prototype(A) : prototype(B) {}, for example.\nSince each sub can only have one prototype, the earlier declaration(s) are discarded\nwhile the last one is applied.\n\navreify called on tied array\n(S debugging) This indicates that something went wrong and Perl got very confused about\n@ or @DB::args being tied.\n\nBad arg length for %s, is %u, should be %d\n(F) You passed a buffer of the wrong size to one of msgctl(), semctl() or shmctl().  In C\nparlance, the correct sizes are, respectively, sizeof(struct msqidds *),\nsizeof(struct semidds *), and sizeof(struct shmidds *).\n\nBad evalled substitution pattern\n(F) You've used the \"/e\" switch to evaluate the replacement for a substitution, but perl\nfound a syntax error in the code to evaluate, most likely an unexpected right brace '}'.\n\nBad filehandle: %s\n(F) A symbol was passed to something wanting a filehandle, but the symbol has no\nfilehandle associated with it.  Perhaps you didn't do an open(), or did it in another\npackage.\n\nBad free() ignored\n(S malloc) An internal routine called free() on something that had never been malloc()ed\nin the first place.  Mandatory, but can be disabled by setting environment variable\n\"PERLBADFREE\" to 0.\n\nThis message can be seen quite often with DBFile on systems with \"hard\" dynamic linking,\nlike \"AIX\" and \"OS/2\".  It is a bug of \"Berkeley DB\" which is left unnoticed if \"DB\" uses\nforgiving system malloc().\n\nBad hash\n(P) One of the internal hash routines was passed a null HV pointer.\n\nBadly placed ()'s\n(A) You've accidentally run your script through csh instead of Perl.  Check the #! line,\nor manually feed your script into Perl yourself.\n\nBad name after %s\n(F) You started to name a symbol by using a package prefix, and then didn't finish the\nsymbol.  In particular, you can't interpolate outside of quotes, so\n\n$var = 'myvar';\n$sym = mypack::$var;\n\nis not the same as\n\n$var = 'myvar';\n$sym = \"mypack::$var\";\n\nBad plugin affecting keyword '%s'\n(F) An extension using the keyword plugin mechanism violated the plugin API.\n\nBad realloc() ignored\n(S malloc) An internal routine called realloc() on something that had never been\nmalloc()ed in the first place.  Mandatory, but can be disabled by setting the environment\nvariable \"PERLBADFREE\" to 1.\n\nBad symbol for array\n(P) An internal request asked to add an array entry to something that wasn't a symbol\ntable entry.\n\nBad symbol for dirhandle\n(P) An internal request asked to add a dirhandle entry to something that wasn't a symbol\ntable entry.\n\nBad symbol for filehandle\n(P) An internal request asked to add a filehandle entry to something that wasn't a symbol\ntable entry.\n\nBad symbol for hash\n(P) An internal request asked to add a hash entry to something that wasn't a symbol table\nentry.\n\nBad symbol for scalar\n(P) An internal request asked to add a scalar entry to something that wasn't a symbol\ntable entry.\n\nBareword found in conditional\n(W bareword) The compiler found a bareword where it expected a conditional, which often\nindicates that an || or && was parsed as part of the last argument of the previous\nconstruct, for example:\n\nopen FOO || die;\n\nIt may also indicate a misspelled constant that has been interpreted as a bareword:\n\nuse constant TYPO => 1;\nif (TYOP) { print \"foo\" }\n\nThe \"strict\" pragma is useful in avoiding such errors.\n\nBareword in require contains \"%s\"\nBareword in require maps to disallowed filename \"%s\"\nBareword in require maps to empty filename\n(F) The bareword form of require has been invoked with a filename which could not have\nbeen generated by a valid bareword permitted by the parser.  You shouldn't be able to get\nthis error from Perl code, but XS code may throw it if it passes an invalid module name\nto \"Perlloadmodule\".\n\nBareword in require must not start with a double-colon: \"%s\"\n(F) In \"require Bare::Word\", the bareword is not allowed to start with a double-colon.\nWrite \"require ::Foo::Bar\" as  \"require Foo::Bar\" instead.\n\nBareword \"%s\" not allowed while \"strict subs\" in use\n(F) With \"strict subs\" in use, a bareword is only allowed as a subroutine identifier, in\ncurly brackets or to the left of the \"=>\" symbol.  Perhaps you need to predeclare a\nsubroutine?\n\nBareword \"%s\" refers to nonexistent package\n(W bareword) You used a qualified bareword of the form \"Foo::\", but the compiler saw no\nother uses of that namespace before that point.  Perhaps you need to predeclare a\npackage?\n\nBareword filehandle \"%s\" not allowed under 'no feature \"barewordfilehandles\"'\n(F) You attempted to use a bareword filehandle with the \"barewordfilehandles\" feature\ndisabled.\n\nOnly the built-in handles \"STDIN\", \"STDOUT\", \"STDERR\", \"ARGV\", \"ARGVOUT\" and \"DATA\" can\nbe used with the \"barewordfilehandles\" feature disabled.\n\nBEGIN failed--compilation aborted\n(F) An untrapped exception was raised while executing a BEGIN subroutine.  Compilation\nstops immediately and the interpreter is exited.\n\nBEGIN not safe after errors--compilation aborted\n(F) Perl found a \"BEGIN {}\" subroutine (or a \"use\" directive, which implies a \"BEGIN {}\")\nafter one or more compilation errors had already occurred.  Since the intended\nenvironment for the \"BEGIN {}\" could not be guaranteed (due to the errors), and since\nsubsequent code likely depends on its correct operation, Perl just gave up.\n\n\\%d better written as $%d\n(W syntax) Outside of patterns, backreferences live on as variables.  The use of\nbackslashes is grandfathered on the right-hand side of a substitution, but stylistically\nit's better to use the variable form because other Perl programmers will expect it, and\nit works better if there are more than 9 backreferences.\n\nBinary number > 0b11111111111111111111111111111111 non-portable\n(W portable) The binary number you specified is larger than 232-1 (4294967295) and\ntherefore non-portable between systems.  See perlport for more on portability concerns.\n\nbind() on closed socket %s\n(W closed) You tried to do a bind on a closed socket.  Did you forget to check the return\nvalue of your socket() call?  See \"bind\" in perlfunc.\n\nbinmode() on closed filehandle %s\n(W unopened) You tried binmode() on a filehandle that was never opened.  Check your\ncontrol flow and number of arguments.\n\nBit vector size > 32 non-portable\n(W portable) Using bit vector sizes larger than 32 is non-portable.\n\nBizarre copy of %s\n(P) Perl detected an attempt to copy an internal value that is not copiable.\n\nBizarre SvTYPE [%d]\n(P) When starting a new thread or returning values from a thread, Perl encountered an\ninvalid data type.\n\nBoth or neither range ends should be Unicode in regex; marked by <-- HERE in m/%s/\n(W regexp) (only under \"use re 'strict'\" or within \"(?[...])\")\n\nIn a bracketed character class in a regular expression pattern, you had a range which has\nexactly one end of it specified using \"\\N{}\", and the other end is specified using a non-\nportable mechanism.  Perl treats the range as a Unicode range, that is, all the\ncharacters in it are considered to be the Unicode characters, and which may be different\ncode points on some platforms Perl runs on.  For example, \"[\\N{U+06}-\\x08]\" is treated as\nif you had instead said \"[\\N{U+06}-\\N{U+08}]\", that is it matches the characters whose\ncode points in Unicode are 6, 7, and 8.  But that \"\\x08\" might indicate that you meant\nsomething different, so the warning gets raised.\n\nBuffer overflow in primeenviter: %s\n(W internal) A warning peculiar to VMS.  While Perl was preparing to iterate over %ENV,\nit encountered a logical name or symbol definition which was too long, so it was\ntruncated to the string shown.\n\nCallback called exit\n(F) A subroutine invoked from an external package via callsv() exited by calling exit.\n\n%s() called too early to check prototype\n(W prototype) You've called a function that has a prototype before the parser saw a\ndefinition or declaration for it, and Perl could not check that the call conforms to the\nprototype.  You need to either add an early prototype declaration for the subroutine in\nquestion, or move the subroutine definition ahead of the call to get proper prototype\nchecking.  Alternatively, if you are certain that you're calling the function correctly,\nyou may put an ampersand before the name to avoid the warning.  See perlsub.\n\nCannot chr %f\n(F) You passed an invalid number (like an infinity or not-a-number) to \"chr\".\n\nCannot complete in-place edit of %s: %s\n(F) Your perl script appears to have changed directory while performing an in-place edit\nof a file specified by a relative path, and your system doesn't include the directory\nrelative POSIX functions needed to handle that.\n\nCannot compress %f in pack\n(F) You tried compressing an infinity or not-a-number as an unsigned integer with BER,\nwhich makes no sense.\n\nCannot compress integer in pack\n(F) An argument to pack(\"w\",...) was too large to compress.  The BER compressed integer\nformat can only be used with positive integers, and you attempted to compress a very\nlarge number (> 1e308).  See \"pack\" in perlfunc.\n\nCannot compress negative numbers in pack\n(F) An argument to pack(\"w\",...) was negative.  The BER compressed integer format can\nonly be used with positive integers.  See \"pack\" in perlfunc.\n\nCannot convert a reference to %s to typeglob\n(F) You manipulated Perl's symbol table directly, stored a reference in it, then tried to\naccess that symbol via conventional Perl syntax.  The access triggers Perl to autovivify\nthat typeglob, but it there is no legal conversion from that type of reference to a\ntypeglob.\n\nCannot copy to %s\n(P) Perl detected an attempt to copy a value to an internal type that cannot be directly\nassigned to.\n\nCannot find encoding \"%s\"\n(S io) You tried to apply an encoding that did not exist to a filehandle, either with\nopen() or binmode().\n\nCannot open %s as a dirhandle: it is already open as a filehandle\n(F) You tried to use opendir() to associate a dirhandle to a symbol (glob or scalar) that\nalready holds a filehandle.  Since this idiom might render your code confusing, it was\ndeprecated in Perl 5.10.  As of Perl 5.28, it is a fatal error.\n\nCannot open %s as a filehandle: it is already open as a dirhandle\n(F) You tried to use open() to associate a filehandle to a symbol (glob or scalar) that\nalready holds a dirhandle.  Since this idiom might render your code confusing, it was\ndeprecated in Perl 5.10.  As of Perl 5.28, it is a fatal error.\n\nCannot pack %f with '%c'\n(F) You tried converting an infinity or not-a-number to an integer, which makes no sense.\n\nCannot printf %f with '%c'\n(F) You tried printing an infinity or not-a-number as a character (%c), which makes no\nsense.  Maybe you meant '%s', or just stringifying it?\n\nCannot set tied @DB::args\n(F) \"caller\" tried to set @DB::args, but found it tied.  Tying @DB::args is not\nsupported.  (Before this error was added, it used to crash.)\n\nCannot tie unreifiable array\n(P) You somehow managed to call \"tie\" on an array that does not keep a reference count on\nits arguments and cannot be made to do so.  Such arrays are not even supposed to be\naccessible to Perl code, but are only used internally.\n\nCannot yet reorder svvcatpvfn() arguments from valist\n(F) Some XS code tried to use \"svvcatpvfn()\" or a related function with a format string\nthat specifies explicit indexes for some of the elements, and using a C-style variable-\nargument list (a \"valist\").  This is not currently supported.  XS authors wanting to do\nthis must instead construct a C array of \"SV*\" scalars containing the arguments.\n\nCan only compress unsigned integers in pack\n(F) An argument to pack(\"w\",...) was not an integer.  The BER compressed integer format\ncan only be used with positive integers, and you attempted to compress something else.\nSee \"pack\" in perlfunc.\n\nCan't bless non-reference value\n(F) Only hard references may be blessed.  This is how Perl \"enforces\" encapsulation of\nobjects.  See perlobj.\n\nCan't \"break\" in a loop topicalizer\n(F) You called \"break\", but you're in a \"foreach\" block rather than a \"given\" block.  You\nprobably meant to use \"next\" or \"last\".\n\nCan't \"break\" outside a given block\n(F) You called \"break\", but you're not inside a \"given\" block.\n\nCan't call method \"%s\" on an undefined value\n(F) You used the syntax of a method call, but the slot filled by the object reference or\npackage name contains an undefined value.  Something like this will reproduce the error:\n\n$BADREF = undef;\nprocess $BADREF 1,2,3;\n$BADREF->process(1,2,3);\n\nCan't call method \"%s\" on unblessed reference\n(F) A method call must know in what package it's supposed to run.  It ordinarily finds\nthis out from the object reference you supply, but you didn't supply an object reference\nin this case.  A reference isn't an object reference until it has been blessed.  See\nperlobj.\n\nCan't call method \"%s\" without a package or object reference\n(F) You used the syntax of a method call, but the slot filled by the object reference or\npackage name contains an expression that returns a defined value which is neither an\nobject reference nor a package name.  Something like this will reproduce the error:\n\n$BADREF = 42;\nprocess $BADREF 1,2,3;\n$BADREF->process(1,2,3);\n\nCan't call mroisachangedin() on anonymous symbol table\n(P) Perl got confused as to whether a hash was a plain hash or a symbol table hash when\ntrying to update @ISA caches.\n\nCan't call mromethodchangedin() on anonymous symbol table\n(F) An XS module tried to call \"mromethodchangedin\" on a hash that was not attached to\nthe symbol table.\n\nCan't chdir to %s\n(F) You called \"perl -x/foo/bar\", but /foo/bar is not a directory that you can chdir to,\npossibly because it doesn't exist.\n\nCan't check filesystem of script \"%s\" for nosuid\n(P) For some reason you can't check the filesystem of the script for nosuid.\n\nCan't coerce %s to %s in %s\n(F) Certain types of SVs, in particular real symbol table entries (typeglobs), can't be\nforced to stop being what they are.  So you can't say things like:\n\n*foo += 1;\n\nYou CAN say\n\n$foo = *foo;\n$foo += 1;\n\nbut then $foo no longer contains a glob.\n\nCan't \"continue\" outside a when block\n(F) You called \"continue\", but you're not inside a \"when\" or \"default\" block.\n\nCan't create pipe mailbox\n(P) An error peculiar to VMS.  The process is suffering from exhausted quotas or other\nplumbing problems.\n\nCan't declare %s in \"%s\"\n(F) Only scalar, array, and hash variables may be declared as \"my\", \"our\" or \"state\"\nvariables.  They must have ordinary identifiers as names.\n\nCan't \"default\" outside a topicalizer\n(F) You have used a \"default\" block that is neither inside a \"foreach\" loop nor a \"given\"\nblock.  (Note that this error is issued on exit from the \"default\" block, so you won't\nget the error if you use an explicit \"continue\".)\n\nCan't determine class of operator %s, assuming BASEOP\n(S) This warning indicates something wrong in the internals of perl.  Perl was trying to\nfind the class (e.g. LISTOP) of a particular OP, and was unable to do so. This is likely\nto be due to a bug in the perl internals, or due to a bug in XS code which manipulates\nperl optrees.\n\nCan't do inplace edit: %s is not a regular file\n(S inplace) You tried to use the -i switch on a special file, such as a file in /dev, a\nFIFO or an uneditable directory.  The file was ignored.\n\nCan't do inplace edit on %s: %s\n(S inplace) The creation of the new file failed for the indicated reason.\n\nCan't do inplace edit: %s would not be unique\n(S inplace) Your filesystem does not support filenames longer than 14 characters and Perl\nwas unable to create a unique filename during inplace editing with the -i switch.  The\nfile was ignored.\n\nCan't do %s(\"%s\") on non-UTF-8 locale; resolved to \"%s\".\n(W locale) You are 1) running under \"\"use locale\"\"; 2) the current locale is not a UTF-8\none; 3) you tried to do the designated case-change operation on the specified Unicode\ncharacter; and 4) the result of this operation would mix Unicode and locale rules, which\nlikely conflict.  Mixing of different rule types is forbidden, so the operation was not\ndone; instead the result is the indicated value, which is the best available that uses\nentirely Unicode rules.  That turns out to almost always be the original character,\nunchanged.\n\nIt is generally a bad idea to mix non-UTF-8 locales and Unicode, and this issue is one of\nthe reasons why.  This warning is raised when Unicode rules would normally cause the\nresult of this operation to contain a character that is in the range specified by the\nlocale, 0..255, and hence is subject to the locale's rules, not Unicode's.\n\nIf you are using locale purely for its characteristics related to things like its numeric\nand time formatting (and not \"LCCTYPE\"), consider using a restricted form of the locale\npragma (see \"The \"use locale\" pragma\" in perllocale) like\n\"\"use locale ':notcharacters'\"\".\n\nNote that failed case-changing operations done as a result of case-insensitive \"/i\"\nregular expression matching will show up in this warning as having the \"fc\" operation (as\nthat is what the regular expression engine calls behind the scenes.)\n\nCan't do waitpid with flags\n(F) This machine doesn't have either waitpid() or wait4(), so only waitpid() without\nflags is emulated.\n\nCan't emulate -%s on #! line\n(F) The #! line specifies a switch that doesn't make sense at this point.  For example,\nit'd be kind of silly to put a -x on the #!  line.\n\nCan't %s %s-endian %ss on this platform\n(F) Your platform's byte-order is neither big-endian nor little-endian, or it has a very\nstrange pointer size.  Packing and unpacking big- or little-endian floating point values\nand pointers may not be possible.  See \"pack\" in perlfunc.\n\nCan't exec \"%s\": %s\n(W exec) A system(), exec(), or piped open call could not execute the named program for\nthe indicated reason.  Typical reasons include: the permissions were wrong on the file,\nthe file wasn't found in $ENV{PATH}, the executable in question was compiled for another\narchitecture, or the #! line in a script points to an interpreter that can't be run for\nsimilar reasons.  (Or maybe your system doesn't support #! at all.)\n\nCan't exec %s\n(F) Perl was trying to execute the indicated program for you because that's what the #!\nline said.  If that's not what you wanted, you may need to mention \"perl\" on the #! line\nsomewhere.\n\nCan't execute %s\n(F) You used the -S switch, but the copies of the script to execute found in the PATH did\nnot have correct permissions.\n\nCan't find an opnumber for \"%s\"\n(F) A string of a form \"CORE::word\" was given to prototype(), but there is no builtin\nwith the name \"word\".\n\nCan't find label %s\n(F) You said to goto a label that isn't mentioned anywhere that it's possible for us to\ngo to.  See \"goto\" in perlfunc.\n\nCan't find %s on PATH\n(F) You used the -S switch, but the script to execute could not be found in the PATH.\n\nCan't find %s on PATH, '.' not in PATH\n(F) You used the -S switch, but the script to execute could not be found in the PATH, or\nat least not with the correct permissions.  The script exists in the current directory,\nbut PATH prohibits running it.\n\nCan't find string terminator %s anywhere before EOF\n(F) Perl strings can stretch over multiple lines.  This message means that the closing\ndelimiter was omitted.  Because bracketed quotes count nesting levels, the following is\nmissing its final parenthesis:\n\nprint q(The character '(' starts a side comment.);\n\nIf you're getting this error from a here-document, you may have included unseen\nwhitespace before or after your closing tag or there may not be a linebreak after it.  A\ngood programmer's editor will have a way to help you find these characters (or lack of\ncharacters).  See perlop for the full details on here-documents.\n\nCan't find Unicode property definition \"%s\"\nCan't find Unicode property definition \"%s\" in regex; marked by <-- HERE in m/%s/\n(F) The named property which you specified via \"\\p\" or \"\\P\" is not one known to Perl.\nPerhaps you misspelled the name?  See \"Properties accessible through \\p{} and \\P{}\" in\nperluniprops for a complete list of available official properties.  If it is a user-\ndefined property it must have been defined by the time the regular expression is matched.\n\nIf you didn't mean to use a Unicode property, escape the \"\\p\", either by \"\\\\p\" (just the\n\"\\p\") or by \"\\Q\\p\" (the rest of the string, or until \"\\E\").\n\nCan't fork: %s\n(F) A fatal error occurred while trying to fork while opening a pipeline.\n\nCan't fork, trying again in 5 seconds\n(W pipe) A fork in a piped open failed with EAGAIN and will be retried after five\nseconds.\n\nCan't get filespec - stale stat buffer?\n(S) A warning peculiar to VMS.  This arises because of the difference between access\nchecks under VMS and under the Unix model Perl assumes.  Under VMS, access checks are\ndone by filename, rather than by bits in the stat buffer, so that ACLs and other\nprotections can be taken into account.  Unfortunately, Perl assumes that the stat buffer\ncontains all the necessary information, and passes it, instead of the filespec, to the\naccess-checking routine.  It will try to retrieve the filespec using the device name and\nFID present in the stat buffer, but this works only if you haven't made a subsequent call\nto the CRTL stat() routine, because the device name is overwritten with each call.  If\nthis warning appears, the name lookup failed, and the access-checking routine gave up and\nreturned FALSE, just to be conservative.  (Note: The access-checking routine knows about\nthe Perl \"stat\" operator and file tests, so you shouldn't ever see this warning in\nresponse to a Perl command; it arises only if some internal code takes stat buffers\nlightly.)\n\nCan't get pipe mailbox device name\n(P) An error peculiar to VMS.  After creating a mailbox to act as a pipe, Perl can't\nretrieve its name for later use.\n\nCan't get SYSGEN parameter value for MAXBUF\n(P) An error peculiar to VMS.  Perl asked $GETSYI how big you want your mailbox buffers\nto be, and didn't get an answer.\n\nCan't \"goto\" into a binary or list expression\n(F) A \"goto\" statement was executed to jump into the middle of a binary or list\nexpression.  You can't get there from here.  The reason for this restriction is that the\ninterpreter would get confused as to how many arguments there are, resulting in stack\ncorruption or crashes.  This error occurs in cases such as these:\n\ngoto F;\nprint do { F: }; # Can't jump into the arguments to print\n\ngoto G;\n$x + do { G: $y }; # How is + supposed to get its first operand?\n\nCan't \"goto\" into a \"given\" block\n(F) A \"goto\" statement was executed to jump into the middle of a \"given\" block.  You\ncan't get there from here.  See \"goto\" in perlfunc.\n\nCan't \"goto\" into the middle of a foreach loop\n(F) A \"goto\" statement was executed to jump into the middle of a foreach loop.  You can't\nget there from here.  See \"goto\" in perlfunc.\n\nCan't \"goto\" out of a pseudo block\n(F) A \"goto\" statement was executed to jump out of what might look like a block, except\nthat it isn't a proper block.  This usually occurs if you tried to jump out of a sort()\nblock or subroutine, which is a no-no.  See \"goto\" in perlfunc.\n\nCan't goto subroutine from an eval-%s\n(F) The \"goto subroutine\" call can't be used to jump out of an eval \"string\" or block.\n\nCan't goto subroutine from a sort sub (or similar callback)\n(F) The \"goto subroutine\" call can't be used to jump out of the comparison sub for a\nsort(), or from a similar callback (such as the reduce() function in List::Util).\n\nCan't goto subroutine outside a subroutine\n(F) The deeply magical \"goto subroutine\" call can only replace one subroutine call for\nanother.  It can't manufacture one out of whole cloth.  In general you should be calling\nit out of only an AUTOLOAD routine anyway.  See \"goto\" in perlfunc.\n\nCan't ignore signal CHLD, forcing to default\n(W signal) Perl has detected that it is being run with the SIGCHLD signal (sometimes\nknown as SIGCLD) disabled.  Since disabling this signal will interfere with proper\ndetermination of exit status of child processes, Perl has reset the signal to its default\nvalue.  This situation typically indicates that the parent program under which Perl may\nbe running (e.g. cron) is being very careless.\n\nCan't kill a non-numeric process ID\n(F) Process identifiers must be (signed) integers.  It is a fatal error to attempt to\nkill() an undefined, empty-string or otherwise non-numeric process identifier.\n\nCan't \"last\" outside a loop block\n(F) A \"last\" statement was executed to break out of the current block, except that\nthere's this itty bitty problem called there isn't a current block.  Note that an \"if\" or\n\"else\" block doesn't count as a \"loopish\" block, as doesn't a block given to sort(),\nmap() or grep().  You can usually double the curlies to get the same effect though,\nbecause the inner curlies will be considered a block that loops once.  See \"last\" in\nperlfunc.\n\nCan't linearize anonymous symbol table\n(F) Perl tried to calculate the method resolution order (MRO) of a package, but failed\nbecause the package stash has no name.\n\nCan't load '%s' for module %s\n(F) The module you tried to load failed to load a dynamic extension.  This may either\nmean that you upgraded your version of perl to one that is incompatible with your old\ndynamic extensions (which is known to happen between major versions of perl), or (more\nlikely) that your dynamic extension was built against an older version of the library\nthat is installed on your system.  You may need to rebuild your old dynamic extensions.\n\nCan't localize lexical variable %s\n(F) You used local on a variable name that was previously declared as a lexical variable\nusing \"my\" or \"state\".  This is not allowed.  If you want to localize a package variable\nof the same name, qualify it with the package name.\n\nCan't localize through a reference\n(F) You said something like \"local $$ref\", which Perl can't currently handle, because\nwhen it goes to restore the old value of whatever $ref pointed to after the scope of the\nlocal() is finished, it can't be sure that $ref will still be a reference.\n\nCan't locate %s\n(F) You said to \"do\" (or \"require\", or \"use\") a file that couldn't be found.  Perl looks\nfor the file in all the locations mentioned in @INC, unless the file name included the\nfull path to the file.  Perhaps you need to set the PERL5LIB or PERL5OPT environment\nvariable to say where the extra library is, or maybe the script needs to add the library\nname to @INC.  Or maybe you just misspelled the name of the file.  See \"require\" in\nperlfunc and lib.\n\nCan't locate auto/%s.al in @INC\n(F) A function (or method) was called in a package which allows autoload, but there is no\nfunction to autoload.  Most probable causes are a misprint in a function/method name or a\nfailure to \"AutoSplit\" the file, say, by doing \"make install\".\n\nCan't locate loadable object for module %s in @INC\n(F) The module you loaded is trying to load an external library, like for example, foo.so\nor bar.dll, but the DynaLoader module was unable to locate this library.  See DynaLoader.\n\nCan't locate object method \"%s\" via package \"%s\"\n(F) You called a method correctly, and it correctly indicated a package functioning as a\nclass, but that package doesn't define that particular method, nor does any of its base\nclasses.  See perlobj.\n\nCan't locate object method \"%s\" via package \"%s\" (perhaps you forgot to load \"%s\"?)\n(F) You called a method on a class that did not exist, and the method could not be found\nin UNIVERSAL.  This often means that a method requires a package that has not been\nloaded.\n\nCan't locate package %s for @%s::ISA\n(W syntax) The @ISA array contained the name of another package that doesn't seem to\nexist.\n\nCan't locate PerlIO%s\n(F) You tried to use in open() a PerlIO layer that does not exist, e.g. open(FH,\n\">:nosuchlayer\", \"somefile\").\n\nCan't make list assignment to %ENV on this system\n(F) List assignment to %ENV is not supported on some systems, notably VMS.\n\nCan't make loaded symbols global on this platform while loading %s\n(S) A module passed the flag 0x01 to DynaLoader::dlloadfile() to request that symbols\nfrom the stated file are made available globally within the process, but that\nfunctionality is not available on this platform.  Whilst the module likely will still\nwork, this may prevent the perl interpreter from loading other XS-based extensions which\nneed to link directly to functions defined in the C or XS code in the stated file.\n\nCan't modify %s in %s\n(F) You aren't allowed to assign to the item indicated, or otherwise try to change it,\nsuch as with an auto-increment.\n\nCan't modify nonexistent substring\n(P) The internal routine that does assignment to a substr() was handed a NULL.\n\nCan't modify non-lvalue subroutine call of &%s\nCan't modify non-lvalue subroutine call of &%s in %s\n(F) Subroutines meant to be used in lvalue context should be declared as such.  See\n\"Lvalue subroutines\" in perlsub.\n\nCan't modify reference to %s in %s assignment\n(F) Only a limited number of constructs can be used as the argument to a reference\nconstructor on the left-hand side of an assignment, and what you used was not one of\nthem.  See \"Assigning to References\" in perlref.\n\nCan't modify reference to localized parenthesized array in list assignment\n(F) Assigning to \"\\local(@array)\" or \"\\(local @array)\" is not supported, as it is not\nclear exactly what it should do.  If you meant to make @array refer to some other array,\nuse \"\\@array = \\@otherarray\".  If you want to make the elements of @array aliases of the\nscalars referenced on the right-hand side, use \"\\(@array) = @scalarrefs\".\n\nCan't modify reference to parenthesized hash in list assignment\n(F) Assigning to \"\\(%hash)\" is not supported.  If you meant to make %hash refer to some\nother hash, use \"\\%hash = \\%otherhash\".  If you want to make the elements of %hash into\naliases of the scalars referenced on the right-hand side, use a hash slice:\n\"\\@hash{@keys} = @thosescalarrefs\".\n\nCan't msgrcv to read-only var\n(F) The target of a msgrcv must be modifiable to be used as a receive buffer.\n\nCan't \"next\" outside a loop block\n(F) A \"next\" statement was executed to reiterate the current block, but there isn't a\ncurrent block.  Note that an \"if\" or \"else\" block doesn't count as a \"loopish\" block, as\ndoesn't a block given to sort(), map() or grep().  You can usually double the curlies to\nget the same effect though, because the inner curlies will be considered a block that\nloops once.  See \"next\" in perlfunc.\n\nCan't open %s: %s\n(S inplace) The implicit opening of a file through use of the \"<>\" filehandle, either\nimplicitly under the \"-n\" or \"-p\" command-line switches, or explicitly, failed for the\nindicated reason.  Usually this is because you don't have read permission for a file\nwhich you named on the command line.\n\n(F) You tried to call perl with the -e switch, but /dev/null (or your operating system's\nequivalent) could not be opened.\n\nCan't open a reference\n(W io) You tried to open a scalar reference for reading or writing, using the 3-arg\nopen() syntax:\n\nopen FH, '>', $ref;\n\nbut your version of perl is compiled without perlio, and this form of open is not\nsupported.\n\nCan't open bidirectional pipe\n(W pipe) You tried to say \"open(CMD, \"|cmd|\")\", which is not supported.  You can try any\nof several modules in the Perl library to do this, such as IPC::Open2.  Alternately,\ndirect the pipe's output to a file using \">\", and then read it in under a different file\nhandle.\n\nCan't open error file %s as stderr\n(F) An error peculiar to VMS.  Perl does its own command line redirection, and couldn't\nopen the file specified after '2>' or '2>>' on the command line for writing.\n\nCan't open input file %s as stdin\n(F) An error peculiar to VMS.  Perl does its own command line redirection, and couldn't\nopen the file specified after '<' on the command line for reading.\n\nCan't open output file %s as stdout\n(F) An error peculiar to VMS.  Perl does its own command line redirection, and couldn't\nopen the file specified after '>' or '>>' on the command line for writing.\n\nCan't open output pipe (name: %s)\n(P) An error peculiar to VMS.  Perl does its own command line redirection, and couldn't\nopen the pipe into which to send data destined for stdout.\n\nCan't open perl script \"%s\": %s\n(F) The script you specified can't be opened for the indicated reason.\n\nIf you're debugging a script that uses #!, and normally relies on the shell's $PATH\nsearch, the -S option causes perl to do that search, so you don't have to type the path\nor \"`which $scriptname`\".\n\nCan't read CRTL environ\n(S) A warning peculiar to VMS.  Perl tried to read an element of %ENV from the CRTL's\ninternal environment array and discovered the array was missing.  You need to figure out\nwhere your CRTL misplaced its environ or define PERLENVTABLES (see perlvms) so that\nenviron is not searched.\n\nCan't redeclare \"%s\" in \"%s\"\n(F) A \"my\", \"our\" or \"state\" declaration was found within another declaration, such as\n\"my ($x, my($y), $z)\" or \"our (my $x)\".\n\nCan't \"redo\" outside a loop block\n(F) A \"redo\" statement was executed to restart the current block, but there isn't a\ncurrent block.  Note that an \"if\" or \"else\" block doesn't count as a \"loopish\" block, as\ndoesn't a block given to sort(), map() or grep().  You can usually double the curlies to\nget the same effect though, because the inner curlies will be considered a block that\nloops once.  See \"redo\" in perlfunc.\n\nCan't remove %s: %s, skipping file\n(S inplace) You requested an inplace edit without creating a backup file.  Perl was\nunable to remove the original file to replace it with the modified file.  The file was\nleft unmodified.\n\nCan't rename in-place work file '%s' to '%s': %s\n(F) When closed implicitly, the temporary file for in-place editing couldn't be renamed\nto the original filename.\n\nCan't rename %s to %s: %s, skipping file\n(F) The rename done by the -i switch failed for some reason, probably because you don't\nhave write permission to the directory.\n\nCan't reopen input pipe (name: %s) in binary mode\n(P) An error peculiar to VMS.  Perl thought stdin was a pipe, and tried to reopen it to\naccept binary data.  Alas, it failed.\n\nCan't represent character for Ox%X on this platform\n(F) There is a hard limit to how big a character code point can be due to the fundamental\nproperties of UTF-8, especially on EBCDIC platforms.  The given code point exceeds that.\nThe only work-around is to not use such a large code point.\n\nCan't reset %ENV on this system\n(F) You called \"reset('E')\" or similar, which tried to reset all variables in the current\npackage beginning with \"E\".  In the main package, that includes %ENV.  Resetting %ENV is\nnot supported on some systems, notably VMS.\n\nCan't resolve method \"%s\" overloading \"%s\" in package \"%s\"\n(F)(P) Error resolving overloading specified by a method name (as opposed to a subroutine\nreference): no such method callable via the package.  If the method name is \"???\", this\nis an internal error.\n\nCan't return %s from lvalue subroutine\n(F) Perl detected an attempt to return illegal lvalues (such as temporary or readonly\nvalues) from a subroutine used as an lvalue.  This is not allowed.\n\nCan't return outside a subroutine\n(F) The return statement was executed in mainline code, that is, where there was no\nsubroutine call to return out of.  See perlsub.\n\nCan't return %s to lvalue scalar context\n(F) You tried to return a complete array or hash from an lvalue subroutine, but you\ncalled the subroutine in a way that made Perl think you meant to return only one value.\nYou probably meant to write parentheses around the call to the subroutine, which tell\nPerl that the call should be in list context.\n\nCan't stat script \"%s\"\n(P) For some reason you can't fstat() the script even though you have it open already.\nBizarre.\n\nCan't take log of %g\n(F) For ordinary real numbers, you can't take the logarithm of a negative number or zero.\nThere's a Math::Complex package that comes standard with Perl, though, if you really want\nto do that for the negative numbers.\n\nCan't take sqrt of %g\n(F) For ordinary real numbers, you can't take the square root of a negative number.\nThere's a Math::Complex package that comes standard with Perl, though, if you really want\nto do that.\n\nCan't undef active subroutine\n(F) You can't undefine a routine that's currently running.  You can, however, redefine it\nwhile it's running, and you can even undef the redefined subroutine while the old routine\nis running.  Go figure.\n\nCan't unweaken a nonreference\n(F) You attempted to unweaken something that was not a reference.  Only references can be\nunweakened.\n\nCan't upgrade %s (%d) to %d\n(P) The internal svupgrade routine adds \"members\" to an SV, making it into a more\nspecialized kind of SV.  The top several SV types are so specialized, however, that they\ncannot be interconverted.  This message indicates that such a conversion was attempted.\n\nCan't use '%c' after -mname\n(F) You tried to call perl with the -m switch, but you put something other than \"=\" after\nthe module name.\n\nCan't use a hash as a reference\n(F) You tried to use a hash as a reference, as in \"%foo->{\"bar\"}\" or \"%$ref->{\"hello\"}\".\nVersions of perl <= 5.22.0 used to allow this syntax, but shouldn't have.  This was\ndeprecated in perl 5.6.1.\n\nCan't use an array as a reference\n(F) You tried to use an array as a reference, as in \"@foo->[23]\" or \"@$ref->[99]\".\nVersions of perl <= 5.22.0 used to allow this syntax, but shouldn't have.  This was\ndeprecated in perl 5.6.1.\n\nCan't use anonymous symbol table for method lookup\n(F) The internal routine that does method lookup was handed a symbol table that doesn't\nhave a name.  Symbol tables can become anonymous for example by undefining stashes:\n\"undef %Some::Package::\".\n\nCan't use an undefined value as %s reference\n(F) A value used as either a hard reference or a symbolic reference must be a defined\nvalue.  This helps to delurk some insidious errors.\n\nCan't use bareword (\"%s\") as %s ref while \"strict refs\" in use\n(F) Only hard references are allowed by \"strict refs\".  Symbolic references are\ndisallowed.  See perlref.\n\nCan't use %! because Errno.pm is not available\n(F) The first time the \"%!\" hash is used, perl automatically loads the Errno.pm module.\nThe Errno module is expected to tie the %! hash to provide symbolic names for $! errno\nvalues.\n\nCan't use both '<' and '>' after type '%c' in %s\n(F) A type cannot be forced to have both big-endian and little-endian byte-order at the\nsame time, so this combination of modifiers is not allowed.  See \"pack\" in perlfunc.\n\nCan't use 'defined(@array)' (Maybe you should just omit the defined()?)\n(F) defined() is not useful on arrays because it checks for an undefined scalar value.\nIf you want to see if the array is empty, just use \"if (@array) { # not empty }\" for\nexample.\n\nCan't use 'defined(%hash)' (Maybe you should just omit the defined()?)\n(F) \"defined()\" is not usually right on hashes.\n\nAlthough \"defined %hash\" is false on a plain not-yet-used hash, it becomes true in\nseveral non-obvious circumstances, including iterators, weak references, stash names,\neven remaining true after \"undef %hash\".  These things make \"defined %hash\" fairly\nuseless in practice, so it now generates a fatal error.\n\nIf a check for non-empty is what you wanted then just put it in boolean context (see\n\"Scalar values\" in perldata):\n\nif (%hash) {\n# not empty\n}\n\nIf you had \"defined %Foo::Bar::QUUX\" to check whether such a package variable exists then\nthat's never really been reliable, and isn't a good way to enquire about the features of\na package, or whether it's loaded, etc.\n\nCan't use %s for loop variable\n(P) The parser got confused when trying to parse a \"foreach\" loop.\n\nCan't use global %s in %s\n(F) You tried to declare a magical variable as a lexical variable.  This is not allowed,\nbecause the magic can be tied to only one location (namely the global variable) and it\nwould be incredibly confusing to have variables in your program that looked like magical\nvariables but weren't.\n\nCan't use '%c' in a group with different byte-order in %s\n(F) You attempted to force a different byte-order on a type that is already inside a\ngroup with a byte-order modifier.  For example you cannot force little-endianness on a\ntype that is inside a big-endian group.\n\nCan't use \"my %s\" in sort comparison\n(F) The global variables $a and $b are reserved for sort comparisons.  You mentioned $a\nor $b in the same line as the <=> or cmp operator, and the variable had earlier been\ndeclared as a lexical variable.  Either qualify the sort variable with the package name,\nor rename the lexical variable.\n\nCan't use %s ref as %s ref\n(F) You've mixed up your reference types.  You have to dereference a reference of the\ntype needed.  You can use the ref() function to test the type of the reference, if need\nbe.\n\nCan't use string (\"%s\") as %s ref while \"strict refs\" in use\nCan't use string (\"%s\"...) as %s ref while \"strict refs\" in use\n(F) You've told Perl to dereference a string, something which \"use strict\" blocks to\nprevent it happening accidentally.  See \"Symbolic references\" in perlref.  This can be\ntriggered by an \"@\" or \"$\" in a double-quoted string immediately before interpolating a\nvariable, for example in \"user @$twitterid\", which says to treat the contents of\n$twitterid as an array reference; use a \"\\\" to have a literal \"@\" symbol followed by the\ncontents of $twitterid: \"user \\@$twitterid\".\n\nCan't use subscript on %s\n(F) The compiler tried to interpret a bracketed expression as a subscript.  But to the\nleft of the brackets was an expression that didn't look like a hash or array reference,\nor anything else subscriptable.\n\nCan't use \\%c to mean $%c in expression\n(W syntax) In an ordinary expression, backslash is a unary operator that creates a\nreference to its argument.  The use of backslash to indicate a backreference to a matched\nsubstring is valid only as part of a regular expression pattern.  Trying to do this in\nordinary Perl code produces a value that prints out looking like SCALAR(0xdecaf).  Use\nthe $1 form instead.\n\nCan't weaken a nonreference\n(F) You attempted to weaken something that was not a reference.  Only references can be\nweakened.\n\nCan't \"when\" outside a topicalizer\n(F) You have used a when() block that is neither inside a \"foreach\" loop nor a \"given\"\nblock.  (Note that this error is issued on exit from the \"when\" block, so you won't get\nthe error if the match fails, or if you use an explicit \"continue\".)\n\nCan't x= to read-only value\n(F) You tried to repeat a constant value (often the undefined value) with an assignment\noperator, which implies modifying the value itself.  Perhaps you need to copy the value\nto a temporary, and repeat that.\n\nCharacter following \"\\c\" must be printable ASCII\n(F) In \"\\cX\", X must be a printable (non-control) ASCII character.\n\nNote that ASCII characters that don't map to control characters are discouraged, and will\ngenerate the warning (when enabled) \"\"\\c%c\" is more clearly written simply as \"%s\"\".\n\nCharacter following \\%c must be '{' or a single-character Unicode property name in regex;\nmarked by <-- HERE in m/%s/\n(F) (In the above the %c is replaced by either \"p\" or \"P\".)  You specified something that\nisn't a legal Unicode property name.  Most Unicode properties are specified by \"\\p{...}\".\nBut if the name is a single character one, the braces may be omitted.\n\nCharacter in 'C' format wrapped in pack\n(W pack) You said\n\npack(\"C\", $x)\n\nwhere $x is either less than 0 or more than 255; the \"C\" format is only for encoding\nnative operating system characters (ASCII, EBCDIC, and so on) and not for Unicode\ncharacters, so Perl behaved as if you meant\n\npack(\"C\", $x & 255)\n\nIf you actually want to pack Unicode codepoints, use the \"U\" format instead.\n\nCharacter in 'c' format wrapped in pack\n(W pack) You said\n\npack(\"c\", $x)\n\nwhere $x is either less than -128 or more than 127; the \"c\" format is only for encoding\nnative operating system characters (ASCII, EBCDIC, and so on) and not for Unicode\ncharacters, so Perl behaved as if you meant\n\npack(\"c\", $x & 255);\n\nIf you actually want to pack Unicode codepoints, use the \"U\" format instead.\n\nCharacter in '%c' format wrapped in unpack\n(W unpack) You tried something like\n\nunpack(\"H\", \"\\x{2a1}\")\n\nwhere the format expects to process a byte (a character with a value below 256), but a\nhigher value was provided instead.  Perl uses the value modulus 256 instead, as if you\nhad provided:\n\nunpack(\"H\", \"\\x{a1}\")\n\nCharacter in 'W' format wrapped in pack\n(W pack) You said\n\npack(\"U0W\", $x)\n\nwhere $x is either less than 0 or more than 255.  However, \"U0\"-mode expects all values\nto fall in the interval [0, 255], so Perl behaved as if you meant:\n\npack(\"U0W\", $x & 255)\n\nCharacter(s) in '%c' format wrapped in pack\n(W pack) You tried something like\n\npack(\"u\", \"\\x{1f3}b\")\n\nwhere the format expects to process a sequence of bytes (character with a value below\n256), but some of the characters had a higher value.  Perl uses the character values\nmodulus 256 instead, as if you had provided:\n\npack(\"u\", \"\\x{f3}b\")\n\nCharacter(s) in '%c' format wrapped in unpack\n(W unpack) You tried something like\n\nunpack(\"s\", \"\\x{1f3}b\")\n\nwhere the format expects to process a sequence of bytes (character with a value below\n256), but some of the characters had a higher value.  Perl uses the character values\nmodulus 256 instead, as if you had provided:\n\nunpack(\"s\", \"\\x{f3}b\")\n\ncharnames alias definitions may not contain a sequence of multiple spaces; marked by <-- HERE\nin %s\n(F) You defined a character name which had multiple space characters in a row.  Change\nthem to single spaces.  Usually these names are defined in the \":alias\" import argument\nto \"use charnames\", but they could be defined by a translator installed into\n$^H{charnames}.  See \"CUSTOM ALIASES\" in charnames.\n\nchdir() on unopened filehandle %s\n(W unopened) You tried chdir() on a filehandle that was never opened.\n\n\"\\c%c\" is more clearly written simply as \"%s\"\n(W syntax) The \"\\cX\" construct is intended to be a way to specify non-printable\ncharacters.  You used it for a printable one, which is better written as simply itself,\nperhaps preceded by a backslash for non-word characters.  Doing it the way you did is not\nportable between ASCII and EBCDIC platforms.\n\nCloning substitution context is unimplemented\n(F) Creating a new thread inside the \"s///\" operator is not supported.\n\nclosedir() attempted on invalid dirhandle %s\n(W io) The dirhandle you tried to close is either closed or not really a dirhandle.\nCheck your control flow.\n\nclose() on unopened filehandle %s\n(W unopened) You tried to close a filehandle that was never opened.\n\nClosure prototype called\n(F) If a closure has attributes, the subroutine passed to an attribute handler is the\nprototype that is cloned when a new closure is created.  This subroutine cannot be\ncalled.\n\n\\C no longer supported in regex; marked by <-- HERE in m/%s/\n(F) The \\C character class used to allow a match of single byte within a multi-byte utf-8\ncharacter, but was removed in v5.24 as it broke encapsulation and its implementation was\nextremely buggy.  If you really need to process the individual bytes, you probably want\nto convert your string to one where each underlying byte is stored as a character, with\nutf8::encode().\n\nCode missing after '/'\n(F) You had a (sub-)template that ends with a '/'.  There must be another template code\nfollowing the slash.  See \"pack\" in perlfunc.\n\nCode point 0x%X is not Unicode, and not portable\n(S nonunicode portable) You had a code point that has never been in any standard, so it\nis likely that languages other than Perl will NOT understand it.  This code point also\nwill not fit in a 32-bit word on ASCII platforms and therefore is non-portable between\nsystems.\n\nAt one time, it was legal in some standards to have code points up to 0x7FFFFFFF, but\nnot higher, and this code point is higher.\n\nAcceptance of these code points is a Perl extension, and you should expect that nothing\nother than Perl can handle them; Perl itself on EBCDIC platforms before v5.24 does not\nhandle them.\n\nPerl also makes no guarantees that the representation of these code points won't change\nat some point in the future, say when machines become available that have larger than a\n64-bit word.  At that time, files containing any of these, written by an older Perl might\nrequire conversion before being readable by a newer Perl.\n\nCode point 0x%X is not Unicode, may not be portable\n(S nonunicode) You had a code point above the Unicode maximum of U+10FFFF.\n\nPerl allows strings to contain a superset of Unicode code points, but these may not be\naccepted by other languages/systems.  Further, even if these languages/systems accept\nthese large code points, they may have chosen a different representation for them than\nthe UTF-8-like one that Perl has, which would mean files are not exchangeable between\nthem and Perl.\n\nOn EBCDIC platforms, code points above 0x3FFFFFFF have a different representation in\nPerl v5.24 than before, so any file containing these that was written before that version\nwill require conversion before being readable by a later Perl.\n\n%s: Command not found\n(A) You've accidentally run your script through csh or another shell instead of Perl.\nCheck the #! line, or manually feed your script into Perl yourself.  The #! line at the\ntop of your file could look like\n\n#!/usr/bin/perl\n\n%s: command not found\n(A) You've accidentally run your script through bash or another shell instead of Perl.\nCheck the #! line, or manually feed your script into Perl yourself.  The #! line at the\ntop of your file could look like\n\n#!/usr/bin/perl\n\n%s: command not found: %s\n(A) You've accidentally run your script through zsh or another shell instead of Perl.\nCheck the #! line, or manually feed your script into Perl yourself.  The #! line at the\ntop of your file could look like\n\n#!/usr/bin/perl\n\nCompilation failed in require\n(F) Perl could not compile a file specified in a \"require\" statement.  Perl uses this\ngeneric message when none of the errors that it encountered were severe enough to halt\ncompilation immediately.\n\nComplex regular subexpression recursion limit (%d) exceeded\n(W regexp) The regular expression engine uses recursion in complex situations where back-\ntracking is required.  Recursion depth is limited to 32766, or perhaps less in\narchitectures where the stack cannot grow arbitrarily.  (\"Simple\" and \"medium\" situations\nare handled without recursion and are not subject to a limit.)  Try shortening the string\nunder examination; looping in Perl code (e.g. with \"while\") rather than in the regular\nexpression engine; or rewriting the regular expression so that it is simpler or\nbacktracks less.  (See perlfaq2 for information on Mastering Regular Expressions.)\n\nconnect() on closed socket %s\n(W closed) You tried to do a connect on a closed socket.  Did you forget to check the\nreturn value of your socket() call?  See \"connect\" in perlfunc.\n\nConstant(%s): Call to &{$^H{%s}} did not return a defined value\n(F) The subroutine registered to handle constant overloading (see overload) or a custom\ncharnames handler (see \"CUSTOM TRANSLATORS\" in charnames) returned an undefined value.\n\nConstant(%s): $^H{%s} is not defined\n(F) The parser found inconsistencies while attempting to define an overloaded constant.\nPerhaps you forgot to load the corresponding overload pragma?\n\nConstant is not %s reference\n(F) A constant value (perhaps declared using the \"use constant\" pragma) is being\ndereferenced, but it amounts to the wrong type of reference.  The message indicates the\ntype of reference that was expected.  This usually indicates a syntax error in\ndereferencing the constant value.  See \"Constant Functions\" in perlsub and constant.\n\nConstants from lexical variables potentially modified elsewhere are no longer permitted\n(F) You wrote something like\n\nmy $var;\n$sub = sub () { $var };\n\nbut $var is referenced elsewhere and could be modified after the \"sub\" expression is\nevaluated.  Either it is explicitly modified elsewhere (\"$var = 3\") or it is passed to a\nsubroutine or to an operator like \"printf\" or \"map\", which may or may not modify the\nvariable.\n\nTraditionally, Perl has captured the value of the variable at that point and turned the\nsubroutine into a constant eligible for inlining.  In those cases where the variable can\nbe modified elsewhere, this breaks the behavior of closures, in which the subroutine\ncaptures the variable itself, rather than its value, so future changes to the variable\nare reflected in the subroutine's return value.\n\nThis usage was deprecated, and as of Perl 5.32 is no longer allowed, making it possible\nto change the behavior in the future.\n\nIf you intended for the subroutine to be eligible for inlining, then make sure the\nvariable is not referenced elsewhere, possibly by copying it:\n\nmy $var2 = $var;\n$sub = sub () { $var2 };\n\nIf you do want this subroutine to be a closure that reflects future changes to the\nvariable that it closes over, add an explicit \"return\":\n\nmy $var;\n$sub = sub () { return $var };\n\nConstant subroutine %s redefined\n(W redefine)(S) You redefined a subroutine which had previously been eligible for\ninlining.  See \"Constant Functions\" in perlsub for commentary and workarounds.\n\nConstant subroutine %s undefined\n(W misc) You undefined a subroutine which had previously been eligible for inlining.  See\n\"Constant Functions\" in perlsub for commentary and workarounds.\n\nConstant(%s) unknown\n(F) The parser found inconsistencies either while attempting to define an overloaded\nconstant, or when trying to find the character name specified in the \"\\N{...}\" escape.\nPerhaps you forgot to load the corresponding overload pragma?\n\n:const is experimental\n(S experimental::constattr) The \"const\" attribute is experimental.  If you want to use\nthe feature, disable the warning with \"no warnings 'experimental::constattr'\", but know\nthat in doing so you are taking the risk that your code may break in a future Perl\nversion.\n\n:const is not permitted on named subroutines\n(F) The \"const\" attribute causes an anonymous subroutine to be run and its value captured\nat the time that it is cloned.  Named subroutines are not cloned like this, so the\nattribute does not make sense on them.\n\nCopy method did not return a reference\n(F) The method which overloads \"=\" is buggy.  See \"Copy Constructor\" in overload.\n\n&CORE::%s cannot be called directly\n(F) You tried to call a subroutine in the \"CORE::\" namespace with &foo syntax or through\na reference.  Some subroutines in this package cannot yet be called that way, but must be\ncalled as barewords.  Something like this will work:\n\nBEGIN { *shove = \\&CORE::push; }\nshove @array, 1,2,3; # pushes on to @array\n\nCORE::%s is not a keyword\n(F) The CORE:: namespace is reserved for Perl keywords.\n\nCorrupted regexp opcode %d > %d\n(P) This is either an error in Perl, or, if you're using one, your custom regular\nexpression engine.  If not the latter, report the problem to\n<https://github.com/Perl/perl5/issues>.\n\ncorrupted regexp pointers\n(P) The regular expression engine got confused by what the regular expression compiler\ngave it.\n\ncorrupted regexp program\n(P) The regular expression engine got passed a regexp program without a valid magic\nnumber.\n\nCorrupt malloc ptr 0x%x at 0x%x\n(P) The malloc package that comes with Perl had an internal failure.\n\nCount after length/code in unpack\n(F) You had an unpack template indicating a counted-length string, but you have also\nspecified an explicit size for the string.  See \"pack\" in perlfunc.\n\nDeclaring references is experimental\n(S experimental::declaredrefs) This warning is emitted if you use a reference\nconstructor on the right-hand side of \"my\", \"state\", \"our\", or \"local\".  Simply suppress\nthe warning if you want to use the feature, but know that in doing so you are taking the\nrisk of using an experimental feature which may change or be removed in a future Perl\nversion:\n\nno warnings \"experimental::declaredrefs\";\nuse feature \"declaredrefs\";\n$fooref = my \\$foo;\n\nDeep recursion on anonymous subroutine\nDeep recursion on subroutine \"%s\"\n(W recursion) This subroutine has called itself (directly or indirectly) 100 times more\nthan it has returned.  This probably indicates an infinite recursion, unless you're\nwriting strange benchmark programs, in which case it indicates something else.\n\nThis threshold can be changed from 100, by recompiling the perl binary, setting the C\npre-processor macro \"PERLSUBDEPTHWARN\" to the desired value.\n\n(?(DEFINE)....) does not allow branches in regex; marked by <-- HERE in m/%s/\n(F) You used something like \"(?(DEFINE)...|..)\" which is illegal.  The most likely cause\nof this error is that you left out a parenthesis inside of the \"....\" part.\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.\n\n%s defines neither package nor VERSION--version check failed\n(F) You said something like \"use Module 42\" but in the Module file there are neither\npackage declarations nor a $VERSION.\n\ndelete argument is not a HASH or ARRAY element or slice\n(F) The argument to \"delete\" must be either a hash or array element, such as:\n\n$foo{$bar}\n$ref->{\"susie\"}[12]\n\nor a hash or array slice, such as:\n\n@foo[$bar, $baz, $xyzzy]\n$ref->[12]->@{\"susie\", \"queue\"}\n\nor a hash key/value or array index/value slice, such as:\n\n%foo[$bar, $baz, $xyzzy]\n$ref->[12]->%{\"susie\", \"queue\"}\n\nDelimiter for here document is too long\n(F) In a here document construct like \"<<FOO\", the label \"FOO\" is too long for Perl to\nhandle.  You have to be seriously twisted to write code that triggers this error.\n\nDeprecated use of my() in false conditional. This will be a fatal error in Perl 5.30\n(D deprecated) You used a declaration similar to \"my $x if 0\".  There has been a long-\nstanding bug in Perl that causes a lexical variable not to be cleared at scope exit when\nits declaration includes a false conditional.  Some people have exploited this bug to\nachieve a kind of static variable.  Since we intend to fix this bug, we don't want people\nrelying on this behavior.  You can achieve a similar static effect by declaring the\nvariable in a separate block outside the function, eg\n\nsub f { my $x if 0; return $x++ }\n\nbecomes\n\n{ my $x; sub f { return $x++ } }\n\nBeginning with perl 5.10.0, you can also use \"state\" variables to have lexicals that are\ninitialized only once (see feature):\n\nsub f { state $x; return $x++ }\n\nThis use of \"my()\" in a false conditional has been deprecated since Perl 5.10, and it\nwill become a fatal error in Perl 5.30.\n\nDESTROY created new reference to dead object '%s'\n(F) A DESTROY() method created a new reference to the object which is just being\nDESTROYed.  Perl is confused, and prefers to abort rather than to create a dangling\nreference.\n\nDid not produce a valid header\nSee \"500 Server error\".\n\n%s did not return a true value\n(F) A required (or used) file must return a true value to indicate that it compiled\ncorrectly and ran its initialization code correctly.  It's traditional to end such a file\nwith a \"1;\", though any true value would do.  See \"require\" in perlfunc.\n\n(Did you mean &%s instead?)\n(W misc) You probably referred to an imported subroutine &FOO as $FOO or some such.\n\n(Did you mean \"local\" instead of \"our\"?)\n(W shadow) Remember that \"our\" does not localize the declared global variable.  You have\ndeclared it again in the same lexical scope, which seems superfluous.\n\n(Did you mean $ or @ instead of %?)\n(W) You probably said %hash{$key} when you meant $hash{$key} or @hash{@keys}.  On the\nother hand, maybe you just meant %hash and got carried away.\n\nDied\n(F) You passed die() an empty string (the equivalent of \"die \"\"\") or you called it with\nno args and $@ was empty.\n\nDocument contains no data\nSee \"500 Server error\".\n\n%s does not define %s::VERSION--version check failed\n(F) You said something like \"use Module 42\" but the Module did not define a $VERSION.\n\n'/' does not take a repeat count\n(F) You cannot put a repeat count of any kind right after the '/' code.  See \"pack\" in\nperlfunc.\n\ndo \"%s\" failed, '.' is no longer in @INC; did you mean do \"./%s\"?\n(D deprecated) Previously \" do \"somefile\"; \" would search the current directory for the\nspecified file.  Since perl v5.26.0, . has been removed from @INC by default, so this is\nno longer true.  To search the current directory (and only the current directory) you can\nwrite \" do \"./somefile\"; \".\n\nDon't know how to get file name\n(P) \"PerlIOgetname\", a perl internal I/O function specific to VMS, was somehow called on\nanother platform.  This should not happen.\n\nDon't know how to handle magic of type \\%o\n(P) The internal handling of magical variables has been cursed.\n\ndostudy: out of memory\n(P) This should have been caught by safemalloc() instead.\n\n(Do you need to predeclare %s?)\n(S syntax) This is an educated guess made in conjunction with the message \"%s found where\noperator expected\".  It often means a subroutine or module name is being referenced that\nhasn't been declared yet.  This may be because of ordering problems in your file, or\nbecause of a missing \"sub\", \"package\", \"require\", or \"use\" statement.  If you're\nreferencing something that isn't defined yet, you don't actually have to define the\nsubroutine or package before the current location.  You can use an empty \"sub foo;\" or\n\"package FOO;\" to enter a \"forward\" declaration.\n\ndump() must be written as CORE::dump() as of Perl 5.30\n(F) You used the obsolete \"dump()\" built-in function.  That was deprecated in Perl 5.8.0.\nAs of Perl 5.30 it must be written in fully qualified format: \"CORE::dump()\".\n\nSee \"dump\" in perlfunc.\n\ndump is not supported\n(F) Your machine doesn't support dump/undump.\n\nDuplicate free() ignored\n(S malloc) An internal routine called free() on something that had already been freed.\n\nDuplicate modifier '%c' after '%c' in %s\n(W unpack) You have applied the same modifier more than once after a type in a pack\ntemplate.  See \"pack\" in perlfunc.\n\nelseif should be elsif\n(S syntax) There is no keyword \"elseif\" in Perl because Larry thinks it's ugly.  Your\ncode will be interpreted as an attempt to call a method named \"elseif\" for the class\nreturned by the following block.  This is unlikely to be what you want.\n\nEmpty \\%c in regex; marked by <-- HERE in m/%s/\nEmpty \\%c{}\nEmpty \\%c{} in regex; marked by <-- HERE in m/%s/\n(F) You used something like \"\\b{}\", \"\\B{}\", \"\\o{}\", \"\\p\", \"\\P\", or \"\\x\" without\nspecifying anything for it to operate on.\n\nUnfortunately, for backwards compatibility reasons, an empty \"\\x\" is legal outside\n\"use re 'strict'\" and expands to a NUL character.\n\nEmpty (?) without any modifiers in regex; marked by <-- HERE in m/%s/\n(W regexp) (only under \"use re 'strict'\") \"(?)\" does nothing, so perhaps this is a typo.\n\n${^ENCODING} is no longer supported\n(F) The special variable \"${^ENCODING}\", formerly used to implement the \"encoding\"\npragma, is no longer supported as of Perl 5.26.0.\n\nSetting it to anything other than \"undef\" is a fatal error as of Perl 5.28.\n\nentering effective %s failed\n(F) While under the \"use filetest\" pragma, switching the real and effective uids or gids\nfailed.\n\n%ENV is aliased to %s\n(F) You're running under taint mode, and the %ENV variable has been aliased to another\nhash, so it doesn't reflect anymore the state of the program's environment.  This is\npotentially insecure.\n\nError converting file specification %s\n(F) An error peculiar to VMS.  Because Perl may have to deal with file specifications in\neither VMS or Unix syntax, it converts them to a single form when it must operate on them\ndirectly.  Either you've passed an invalid file specification to Perl, or you've found a\ncase the conversion routines don't handle.  Drat.\n\nError %s in expansion of %s\n(F) An error was encountered in handling a user-defined property (\"User-Defined Character\nProperties\" in perlunicode).  These are programmer written subroutines, hence subject to\nerrors that may prevent them from compiling or running.  The calls to these subs are\n\"eval\"'d, and if there is a failure, this message is raised, using the contents of $@\nfrom the failed \"eval\".\n\nAnother possibility is that tainted data was encountered somewhere in the chain of\nexpanding the property.  If so, the message wording will indicate that this is the\nproblem.  See \"Insecure user-defined property %s\".\n\nEval-group in insecure regular expression\n(F) Perl detected tainted data when trying to compile a regular expression that contains\nthe \"(?{ ... })\" zero-width assertion, which is unsafe.  See \"(?{ code })\" in perlre, and\nperlsec.\n\nEval-group not allowed at runtime, use re 'eval' in regex m/%s/\n(F) Perl tried to compile a regular expression containing the \"(?{ ... })\" zero-width\nassertion at run time, as it would when the pattern contains interpolated values.  Since\nthat is a security risk, it is not allowed.  If you insist, you may still do this by\nusing the \"re 'eval'\" pragma or by explicitly building the pattern from an interpolated\nstring at run time and using that in an eval().  See \"(?{ code })\" in perlre.\n\nEval-group not allowed, use re 'eval' in regex m/%s/\n(F) A regular expression contained the \"(?{ ... })\" zero-width assertion, but that\nconstruct is only allowed when the \"use re 'eval'\" pragma is in effect.  See \"(?{ code\n})\" in perlre.\n\nEVAL without pos change exceeded limit in regex; marked by <-- HERE in m/%s/\n(F) You used a pattern that nested too many EVAL calls without consuming any text.\nRestructure the pattern so that text is consumed.\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.\n\nExcessively long <> operator\n(F) The contents of a <> operator may not exceed the maximum size of a Perl identifier.\nIf you're just trying to glob a long list of filenames, try using the glob() operator, or\nput the filenames into a variable and glob that.\n\nexec? I'm not *that* kind of operating system\n(F) The \"exec\" function is not implemented on some systems, e.g.  Catamount. See\nperlport.\n\n%sExecution of %s aborted due to compilation errors.\n(F) The final summary message when a Perl compilation fails.\n\nexists argument is not a HASH or ARRAY element or a subroutine\n(F) The argument to \"exists\" must be a hash or array element or a subroutine with an\nampersand, such as:\n\n$foo{$bar}\n$ref->{\"susie\"}[12]\n&dosomething\n\nexists argument is not a subroutine name\n(F) The argument to \"exists\" for \"exists &sub\" must be a subroutine name, and not a\nsubroutine call.  \"exists &sub()\" will generate this error.\n\nExiting eval via %s\n(W exiting) You are exiting an eval by unconventional means, such as a goto, or a loop\ncontrol statement.\n\nExiting format via %s\n(W exiting) You are exiting a format by unconventional means, such as a goto, or a loop\ncontrol statement.\n\nExiting pseudo-block via %s\n(W exiting) You are exiting a rather special block construct (like a sort block or\nsubroutine) by unconventional means, such as a goto, or a loop control statement.  See\n\"sort\" in perlfunc.\n\nExiting subroutine via %s\n(W exiting) You are exiting a subroutine by unconventional means, such as a goto, or a\nloop control statement.\n\nExiting substitution via %s\n(W exiting) You are exiting a substitution by unconventional means, such as a return, a\ngoto, or a loop control statement.\n\nExpecting close bracket in regex; marked by <-- HERE in m/%s/\n(F) You wrote something like\n\n(?13\n\nto denote a capturing group of the form \"(?PARNO)\", but omitted the \")\".\n\nExpecting interpolated extended charclass in regex; marked by <-- HERE in m/%s/\n(F) It looked like you were attempting to interpolate an already-compiled extended\ncharacter class, like so:\n\nmy $thaiorlao = qr/(?[ \\p{Thai} + \\p{Lao} ])/;\n...\nqr/(?[ \\p{Digit} & $thaiorlao ])/;\n\nBut the marked code isn't syntactically correct to be such an interpolated class.\n\nExperimental aliasing via reference not enabled\n(F) To do aliasing via references, you must first enable the feature:\n\nno warnings \"experimental::refaliasing\";\nuse feature \"refaliasing\";\n\\$x = \\$y;\n\nExperimental %s on scalar is now forbidden\n(F) An experimental feature added in Perl 5.14 allowed \"each\", \"keys\", \"push\", \"pop\",\n\"shift\", \"splice\", \"unshift\", and \"values\" to be called with a scalar argument.  This\nexperiment is considered unsuccessful, and has been removed.  The \"postderef\" feature may\nmeet your needs better.\n\nExperimental subroutine signatures not enabled\n(F) To use subroutine signatures, you must first enable them:\n\nno warnings \"experimental::signatures\";\nuse feature \"signatures\";\nsub foo ($left, $right) { ... }\n\nExplicit blessing to '' (assuming package main)\n(W misc) You are blessing a reference to a zero length string.  This has the effect of\nblessing the reference into the package main.  This is usually not what you want.\nConsider providing a default target package, e.g. bless($ref, $p || 'MyPackage');\n\n%s: Expression syntax\n(A) You've accidentally run your script through csh instead of Perl.  Check the #! line,\nor manually feed your script into Perl yourself.\n\n%s failed--call queue aborted\n(F) An untrapped exception was raised while executing a UNITCHECK, CHECK, INIT, or END\nsubroutine.  Processing of the remainder of the queue of such routines has been\nprematurely ended.\n\nFailed to close in-place work file %s: %s\n(F) Closing an output file from in-place editing, as with the \"-i\" command-line switch,\nfailed.\n\nFalse [] range \"%s\" in regex; marked by <-- HERE in m/%s/\n(W regexp)(F) A character class range must start and end at a literal character, not\nanother character class like \"\\d\" or \"[:alpha:]\".  The \"-\" in your false range is\ninterpreted as a literal \"-\".  In a \"(?[...])\"  construct, this is an error, rather than\na warning.  Consider quoting the \"-\", \"\\-\".  The <-- HERE shows whereabouts in the\nregular expression the problem was discovered.  See perlre.\n\nFatal VMS error (status=%d) at %s, line %d\n(P) An error peculiar to VMS.  Something untoward happened in a VMS system service or RTL\nroutine; Perl's exit status should provide more details.  The filename in \"at %s\" and the\nline number in \"line %d\" tell you which section of the Perl source code is distressed.\n\nfcntl is not implemented\n(F) Your machine apparently doesn't implement fcntl().  What is this, a PDP-11 or\nsomething?\n\nFETCHSIZE returned a negative value\n(F) A tied array claimed to have a negative number of elements, which is not possible.\n\nField too wide in 'u' format in pack\n(W pack) Each line in an uuencoded string starts with a length indicator which can't\nencode values above 63.  So there is no point in asking for a line length bigger than\nthat.  Perl will behave as if you specified \"u63\" as the format.\n\nFile::Glob::glob() will disappear in perl 5.30. Use File::Glob::bsdglob() instead.\n(D deprecated) \"File::Glob\" has a function called \"glob\", which just calls \"bsdglob\".\nHowever, its prototype is different from the prototype of \"CORE::glob\", and hence,\n\"File::Glob::glob\" should not be used.\n\n\"File::Glob::glob()\" was deprecated in perl 5.8.0. A deprecation message was issued from\nperl 5.26.0 onwards, and the function will disappear in perl 5.30.0.\n\nCode using \"File::Glob::glob()\" should call \"File::Glob::bsdglob()\" instead.\n\nFilehandle %s opened only for input\n(W io) You tried to write on a read-only filehandle.  If you intended it to be a read-\nwrite filehandle, you needed to open it with \"+<\" or \"+>\" or \"+>>\" instead of with \"<\" or\nnothing.  If you intended only to write the file, use \">\" or \">>\".  See \"open\" in\nperlfunc.\n\nFilehandle %s opened only for output\n(W io) You tried to read from a filehandle opened only for writing, If you intended it to\nbe a read/write filehandle, you needed to open it with \"+<\" or \"+>\" or \"+>>\" instead of\nwith \">\".  If you intended only to read from the file, use \"<\".  See \"open\" in perlfunc.\nAnother possibility is that you attempted to open filedescriptor 0 (also known as STDIN)\nfor output (maybe you closed STDIN earlier?).\n\nFilehandle %s reopened as %s only for input\n(W io) You opened for reading a filehandle that got the same filehandle id as STDOUT or\nSTDERR.  This occurred because you closed STDOUT or STDERR previously.\n\nFilehandle STDIN reopened as %s only for output\n(W io) You opened for writing a filehandle that got the same filehandle id as STDIN.\nThis occurred because you closed STDIN previously.\n\nFinal $ should be \\$ or $name\n(F) You must now decide whether the final $ in a string was meant to be a literal dollar\nsign, or was meant to introduce a variable name that happens to be missing.  So you have\nto put either the backslash or the name.\n\nflock() on closed filehandle %s\n(W closed) The filehandle you're attempting to flock() got itself closed some time before\nnow.  Check your control flow.  flock() operates on filehandles.  Are you attempting to\ncall flock() on a dirhandle by the same name?\n\nFormat not terminated\n(F) A format must be terminated by a line with a solitary dot.  Perl got to the end of\nyour file without finding such a line.\n\nFormat %s redefined\n(W redefine) You redefined a format.  To suppress this warning, say\n\n{\nno warnings 'redefine';\neval \"format NAME =...\";\n}\n\nFound = in conditional, should be ==\n(W syntax) You said\n\nif ($foo = 123)\n\nwhen you meant\n\nif ($foo == 123)\n\n(or something like that).\n\n%s found where operator expected\n(S syntax) The Perl lexer knows whether to expect a term or an operator.  If it sees what\nit knows to be a term when it was expecting to see an operator, it gives you this\nwarning.  Usually it indicates that an operator or delimiter was omitted, such as a\nsemicolon.\n\ngdbm store returned %d, errno %d, key \"%s\"\n(S) A warning from the GDBMFile extension that a store failed.\n\ngethostent not implemented\n(F) Your C library apparently doesn't implement gethostent(), probably because if it did,\nit'd feel morally obligated to return every hostname on the Internet.\n\nget%sname() on closed socket %s\n(W closed) You tried to get a socket or peer socket name on a closed socket.  Did you\nforget to check the return value of your socket() call?\n\ngetpwnam returned invalid UIC %#o for user \"%s\"\n(S) A warning peculiar to VMS.  The call to \"sys$getuai\" underlying the \"getpwnam\"\noperator returned an invalid UIC.\n\ngetsockopt() on closed socket %s\n(W closed) You tried to get a socket option on a closed socket.  Did you forget to check\nthe return value of your socket() call?  See \"getsockopt\" in perlfunc.\n\ngiven is experimental\n(S experimental::smartmatch) \"given\" depends on smartmatch, which is experimental, so its\nbehavior may change or even be removed in any future release of perl.  See the\nexplanation under \"Experimental Details on given and when\" in perlsyn.\n\nGlobal symbol \"%s\" requires explicit package name (did you forget to declare \"my %s\"?)\n(F) You've said \"use strict\" or \"use strict vars\", which indicates that all variables\nmust either be lexically scoped (using \"my\" or \"state\"), declared beforehand using \"our\",\nor explicitly qualified to say which package the global variable is in (using \"::\").\n\nglob failed (%s)\n(S glob) Something went wrong with the external program(s) used for \"glob\" and \"<*.c>\".\nUsually, this means that you supplied a \"glob\" pattern that caused the external program\nto fail and exit with a nonzero status.  If the message indicates that the abnormal exit\nresulted in a coredump, this may also mean that your csh (C shell) is broken.  If so, you\nshould change all of the csh-related variables in config.sh:  If you have tcsh, make the\nvariables refer to it as if it were csh (e.g. \"fullcsh='/usr/bin/tcsh'\"); otherwise,\nmake them all empty (except that \"dcsh\" should be 'undef') so that Perl will think csh\nis missing.  In either case, after editing config.sh, run \"./Configure -S\" and rebuild\nPerl.\n\nGlob not terminated\n(F) The lexer saw a left angle bracket in a place where it was expecting a term, so it's\nlooking for the corresponding right angle bracket, and not finding it.  Chances are you\nleft some needed parentheses out earlier in the line, and you really meant a \"less than\".\n\ngmtime(%f) failed\n(W overflow) You called \"gmtime\" with a number that it could not handle: too large, too\nsmall, or NaN.  The returned value is \"undef\".\n\ngmtime(%f) too large\n(W overflow) You called \"gmtime\" with a number that was larger than it can reliably\nhandle and \"gmtime\" probably returned the wrong date.  This warning is also triggered\nwith NaN (the special not-a-number value).\n\ngmtime(%f) too small\n(W overflow) You called \"gmtime\" with a number that was smaller than it can reliably\nhandle and \"gmtime\" probably returned the wrong date.\n\nGot an error from DosAllocMem\n(P) An error peculiar to OS/2.  Most probably you're using an obsolete version of Perl,\nand this should not happen anyway.\n\ngoto must have label\n(F) Unlike with \"next\" or \"last\", you're not allowed to goto an unspecified destination.\nSee \"goto\" in perlfunc.\n\nGoto undefined subroutine%s\n(F) You tried to call a subroutine with \"goto &sub\" syntax, but the indicated subroutine\nhasn't been defined, or if it was, it has since been undefined.\n\nGroup name must start with a non-digit word character in regex; marked by <-- HERE in m/%s/\n(F) Group names must follow the rules for perl identifiers, meaning they must start with\na non-digit word character.  A common cause of this error is using (?&0) instead of (?0).\nSee perlre.\n\n()-group starts with a count\n(F) A ()-group started with a count.  A count is supposed to follow something: a template\ncharacter or a ()-group.  See \"pack\" in perlfunc.\n\n%s had compilation errors.\n(F) The final summary message when a \"perl -c\" fails.\n\nHad to create %s unexpectedly\n(S internal) A routine asked for a symbol from a symbol table that ought to have existed\nalready, but for some reason it didn't, and had to be created on an emergency basis to\nprevent a core dump.\n\n%s has too many errors\n(F) The parser has given up trying to parse the program after 10 errors.  Further error\nmessages would likely be uninformative.\n\nHexadecimal float: exponent overflow\n(W overflow) The hexadecimal floating point has a larger exponent than the floating point\nsupports.\n\nHexadecimal float: exponent underflow\n(W overflow) The hexadecimal floating point has a smaller exponent than the floating\npoint supports.  With the IEEE 754 floating point, this may also mean that the subnormals\n(formerly known as denormals) are being used, which may or may not be an error.\n\nHexadecimal float: internal error (%s)\n(F) Something went horribly bad in hexadecimal float handling.\n\nHexadecimal float: mantissa overflow\n(W overflow) The hexadecimal floating point literal had more bits in the mantissa (the\npart between the 0x and the exponent, also known as the fraction or the significand) than\nthe floating point supports.\n\nHexadecimal float: precision loss\n(W overflow) The hexadecimal floating point had internally more digits than could be\noutput.  This can be caused by unsupported long double formats, or by 64-bit integers not\nbeing available (needed to retrieve the digits under some configurations).\n\nHexadecimal float: unsupported long double format\n(F) You have configured Perl to use long doubles but the internals of the long double\nformat are unknown; therefore the hexadecimal float output is impossible.\n\nHexadecimal number > 0xffffffff non-portable\n(W portable) The hexadecimal number you specified is larger than 232-1 (4294967295) and\ntherefore non-portable between systems.  See perlport for more on portability concerns.\n\nIdentifier too long\n(F) Perl limits identifiers (names for variables, functions, etc.) to about 250\ncharacters for simple names, and somewhat more for compound names (like $A::B).  You've\nexceeded Perl's limits.  Future versions of Perl are likely to eliminate these arbitrary\nlimitations.\n\nIgnoring zero length \\N{} in character class in regex; marked by <-- HERE in m/%s/\n(W regexp) Named Unicode character escapes (\"\\N{...}\") may return a zero-length sequence.\nWhen such an escape is used in a character class its behavior is not well defined.  Check\nthat the correct escape has been used, and the correct charname handler is in scope.\n\nIllegal %s digit '%c' ignored\n(W digit) Here %s is one of \"binary\", \"octal\", or \"hex\".  You may have tried to use a\ndigit other than one that is legal for the given type, such as only 0 and 1 for binary.\nFor octals, this is raised only if the illegal character is an '8' or '9'.  For hex, 'A'\n- 'F' and 'a' - 'f' are legal.  Interpretation of the number stopped just before the\noffending digit or character.\n\nIllegal binary digit '%c'\n(F) You used a digit other than 0 or 1 in a binary number.\n\nIllegal character after '' in prototype for %s : %s\n(W illegalproto) An illegal character was found in a prototype declaration.  The '' in a\nprototype must be followed by a ';', indicating the rest of the parameters are optional,\nor one of '@' or '%', since those two will accept 0 or more final parameters.\n\nIllegal character \\%o (carriage return)\n(F) Perl normally treats carriage returns in the program text as it would any other\nwhitespace, which means you should never see this error when Perl was built using\nstandard options.  For some reason, your version of Perl appears to have been built\nwithout this support.  Talk to your Perl administrator.\n\nIllegal character following sigil in a subroutine signature\n(F) A parameter in a subroutine signature contained an unexpected character following the\n\"$\", \"@\" or \"%\" sigil character.  Normally the sigil should be followed by the variable\nname or \"=\" etc.  Perhaps you are trying use a prototype while in the scope of \"use\nfeature 'signatures'\"?  For example:\n\nsub foo ($$) {}            # legal - a prototype\n\nuse feature 'signatures;\nsub foo ($$) {}            # illegal - was expecting a signature\nsub foo ($a, $b)\n:prototype($$) {}  # legal\n\nIllegal character in prototype for %s : %s\n(W illegalproto) An illegal character was found in a prototype declaration.  Legal\ncharacters in prototypes are $, @, %, *, ;, [, ], &, \\, and +.  Perhaps you were trying\nto write a subroutine signature but didn't enable that feature first (\"use feature\n'signatures'\"), so your signature was instead interpreted as a bad prototype.\n\nIllegal declaration of anonymous subroutine\n(F) When using the \"sub\" keyword to construct an anonymous subroutine, you must always\nspecify a block of code.  See perlsub.\n\nIllegal declaration of subroutine %s\n(F) A subroutine was not declared correctly.  See perlsub.\n\nIllegal division by zero\n(F) You tried to divide a number by 0.  Either something was wrong in your logic, or you\nneed to put a conditional in to guard against meaningless input.\n\nIllegal modulus zero\n(F) You tried to divide a number by 0 to get the remainder.  Most numbers don't take to\nthis kindly.\n\nIllegal number of bits in vec\n(F) The number of bits in vec() (the third argument) must be a power of two from 1 to 32\n(or 64, if your platform supports that).\n\nIllegal octal digit '%c'\n(F) You used an 8 or 9 in an octal number.\n\nIllegal operator following parameter in a subroutine signature\n(F) A parameter in a subroutine signature, was followed by something other than \"=\"\nintroducing a default, \",\" or \")\".\n\nuse feature 'signatures';\nsub foo ($=1) {}           # legal\nsub foo ($a = 1) {}        # legal\nsub foo ($a += 1) {}       # illegal\nsub foo ($a == 1) {}       # illegal\n\nIllegal pattern in regex; marked by <-- HERE in m/%s/\n(F) You wrote something like\n\n(?+foo)\n\nThe \"+\" is valid only when followed by digits, indicating a capturing group.  See\n\"(?PARNO)\".\n\nIllegal suidscript\n(F) The script run under suidperl was somehow illegal.\n\nIllegal switch in PERL5OPT: -%c\n(X) The PERL5OPT environment variable may only be used to set the following switches:\n-[CDIMUdmtw].\n\nIllegal user-defined property name\n(F) You specified a Unicode-like property name in a regular expression pattern (using\n\"\\p{}\" or \"\\P{}\") that Perl knows isn't an official Unicode property, and was likely\nmeant to be a user-defined property name, but it can't be one of those, as they must\nbegin with either \"In\" or \"Is\".  Check the spelling.  See also \"Can't find Unicode\nproperty definition \"%s\"\".\n\nIll-formed CRTL environ value \"%s\"\n(W internal) A warning peculiar to VMS.  Perl tried to read the CRTL's internal environ\narray, and encountered an element without the \"=\" delimiter used to separate keys from\nvalues.  The element is ignored.\n\nIll-formed message in primeenviter: |%s|\n(W internal) A warning peculiar to VMS.  Perl tried to read a logical name or CLI symbol\ndefinition when preparing to iterate over %ENV, and didn't see the expected delimiter\nbetween key and value, so the line was ignored.\n\n(in cleanup) %s\n(W misc) This prefix usually indicates that a DESTROY() method raised the indicated\nexception.  Since destructors are usually called by the system at arbitrary points during\nexecution, and often a vast number of times, the warning is issued only once for any\nnumber of failures that would otherwise result in the same message being repeated.\n\nFailure of user callbacks dispatched using the \"GKEEPERR\" flag could also result in this\nwarning.  See \"GKEEPERR\" in perlcall.\n\nIncomplete expression within '(?[ ])' in regex; marked by <-- HERE in m/%s/\n(F) There was a syntax error within the \"(?[ ])\".  This can happen if the expression\ninside the construct was completely empty, or if there are too many or few operands for\nthe number of operators.  Perl is not smart enough to give you a more precise indication\nas to what is wrong.\n\nInconsistent hierarchy during C3 merge of class '%s': merging failed on parent '%s'\n(F) The method resolution order (MRO) of the given class is not C3-consistent, and you\nhave enabled the C3 MRO for this class.  See the C3 documentation in mro for more\ninformation.\n\nIndentation on line %d of here-doc doesn't match delimiter\n(F) You have an indented here-document where one or more of its lines have whitespace at\nthe beginning that does not match the closing delimiter.\n\nFor example, line 2 below is wrong because it does not have at least 2 spaces, but lines\n1 and 3 are fine because they have at least 2:\n\nif ($something) {\nprint <<~EOF;\nLine 1\nLine 2 not\nLine 3\nEOF\n}\n\nNote that tabs and spaces are compared strictly, meaning 1 tab will not match 8 spaces.\n\nInfinite recursion in regex\n(F) You used a pattern that references itself without consuming any input text.  You\nshould check the pattern to ensure that recursive patterns either consume text or fail.\n\nInfinite recursion in user-defined property\n(F) A user-defined property (\"User-Defined Character Properties\" in perlunicode) can\ndepend on the definitions of other user-defined properties.  If the chain of dependencies\nleads back to this property, infinite recursion would occur, were it not for the check\nthat raised this error.\n\nRestructure your property definitions to avoid this.\n\nInfinite recursion via empty pattern\n(F) You tried to use the empty pattern inside of a regex code block, for instance \"/(?{\ns!!! })/\", which resulted in re-executing the same pattern, which is an infinite loop\nwhich is broken by throwing an exception.\n\nInitialization of state variables in list currently forbidden\n(F) \"state\" only permits initializing a single variable, specified without parentheses.\nSo \"state $a = 42\" and \"state @a = qw(a b c)\" are allowed, but not \"state ($a) = 42\" or\n\"(state $a) = 42\".  To initialize more than one \"state\" variable, initialize them one at\na time.\n\n%%s[%s] in scalar context better written as $%s[%s]\n(W syntax) In scalar context, you've used an array index/value slice (indicated by %) to\nselect a single element of an array.  Generally it's better to ask for a scalar value\n(indicated by $).  The difference is that $foo[&bar] always behaves like a scalar, both\nin the value it returns and when evaluating its argument, while %foo[&bar] provides a\nlist context to its subscript, which can do weird things if you're expecting only one\nsubscript.  When called in list context, it also returns the index (what &bar returns) in\naddition to the value.\n\n%%s{%s} in scalar context better written as $%s{%s}\n(W syntax) In scalar context, you've used a hash key/value slice (indicated by %) to\nselect a single element of a hash.  Generally it's better to ask for a scalar value\n(indicated by $).  The difference is that $foo{&bar} always behaves like a scalar, both\nin the value it returns and when evaluating its argument, while @foo{&bar} and provides a\nlist context to its subscript, which can do weird things if you're expecting only one\nsubscript.  When called in list context, it also returns the key in addition to the\nvalue.\n\nInsecure dependency in %s\n(F) You tried to do something that the tainting mechanism didn't like.  The tainting\nmechanism is turned on when you're running setuid or setgid, or when you specify -T to\nturn it on explicitly.  The tainting mechanism labels all data that's derived directly or\nindirectly from the user, who is considered to be unworthy of your trust.  If any such\ndata is used in a \"dangerous\" operation, you get this error.  See perlsec for more\ninformation.\n\nInsecure directory in %s\n(F) You can't use system(), exec(), or a piped open in a setuid or setgid script if\n$ENV{PATH} contains a directory that is writable by the world.  Also, the PATH must not\ncontain any relative directory.  See perlsec.\n\nInsecure $ENV{%s} while running %s\n(F) You can't use system(), exec(), or a piped open in a setuid or setgid script if any\nof $ENV{PATH}, $ENV{IFS}, $ENV{CDPATH}, $ENV{ENV}, $ENV{BASHENV} or $ENV{TERM} are\nderived from data supplied (or potentially supplied) by the user.  The script must set\nthe path to a known value, using trustworthy data.  See perlsec.\n\nInsecure user-defined property %s\n(F) Perl detected tainted data when trying to compile a regular expression that contains\na call to a user-defined character property function, i.e. \"\\p{IsFoo}\" or \"\\p{InFoo}\".\nSee \"User-Defined Character Properties\" in perlunicode and perlsec.\n\nInteger overflow in format string for %s\n(F) The indexes and widths specified in the format string of \"printf()\" or \"sprintf()\"\nare too large.  The numbers must not overflow the size of integers for your architecture.\n\nInteger overflow in %s number\n(S overflow) The hexadecimal, octal or binary number you have specified either as a\nliteral or as an argument to hex() or oct() is too big for your architecture, and has\nbeen converted to a floating point number.  On a 32-bit architecture the largest\nhexadecimal, octal or binary number representable without overflow is 0xFFFFFFFF,\n037777777777, or 0b11111111111111111111111111111111 respectively.  Note that Perl\ntransparently promotes all numbers to a floating point representation internally--subject\nto loss of precision errors in subsequent operations.\n\nInteger overflow in srand\n(S overflow) The number you have passed to srand is too big to fit in your architecture's\ninteger representation.  The number has been replaced with the largest integer supported\n(0xFFFFFFFF on 32-bit architectures).  This means you may be getting less randomness than\nyou expect, because different random seeds above the maximum will return the same\nsequence of random numbers.\n\nInteger overflow in version\nInteger overflow in version %d\n(W overflow) Some portion of a version initialization is too large for the size of\nintegers for your architecture.  This is not a warning because there is no rational\nreason for a version to try and use an element larger than typically 232.  This is\nusually caused by trying to use some odd mathematical operation as a version, like 100/9.\n\nInternal disaster in regex; marked by <-- HERE in m/%s/\n(P) Something went badly wrong in the regular expression parser.  The <-- HERE shows\nwhereabouts in the regular expression the problem was discovered.\n\nInternal inconsistency in tracking vforks\n(S) A warning peculiar to VMS.  Perl keeps track of the number of times you've called\n\"fork\" and \"exec\", to determine whether the current call to \"exec\" should affect the\ncurrent script or a subprocess (see \"exec LIST\" in perlvms).  Somehow, this count has\nbecome scrambled, so Perl is making a guess and treating this \"exec\" as a request to\nterminate the Perl script and execute the specified command.\n\ninternal %<num>p might conflict with future printf extensions\n(S internal) Perl's internal routine that handles \"printf\" and \"sprintf\" formatting\nfollows a slightly different set of rules when called from C or XS code.  Specifically,\nformats consisting of digits followed by \"p\" (e.g., \"%7p\") are reserved for future use.\nIf you see this message, then an XS module tried to call that routine with one such\nreserved format.\n\nInternal urp in regex; marked by <-- HERE in m/%s/\n(P) Something went badly awry in the regular expression parser.  The <-- HERE shows\nwhereabouts in the regular expression the problem was discovered.\n\n%s (...) interpreted as function\n(W syntax) You've run afoul of the rule that says that any list operator followed by\nparentheses turns into a function, with all the list operators arguments found inside the\nparentheses.  See \"Terms and List Operators (Leftward)\" in perlop.\n\nIn '(?...)', the '(' and '?' must be adjacent in regex; marked by <-- HERE in m/%s/\n(F) The two-character sequence \"(?\" in this context in a regular expression pattern\nshould be an indivisible token, with nothing intervening between the \"(\" and the \"?\", but\nyou separated them with whitespace.\n\nIn '(*...)', the '(' and '*' must be adjacent in regex; marked by <-- HERE in m/%s/\n(F) The two-character sequence \"(*\" in this context in a regular expression pattern\nshould be an indivisible token, with nothing intervening between the \"(\" and the \"*\", but\nyou separated them.  Fix the pattern and retry.\n\nInvalid %s attribute: %s\n(F) The indicated attribute for a subroutine or variable was not recognized by Perl or by\na user-supplied handler.  See attributes.\n\nInvalid %s attributes: %s\n(F) The indicated attributes for a subroutine or variable were not recognized by Perl or\nby a user-supplied handler.  See attributes.\n\nInvalid character in charnames alias definition; marked by <-- HERE in '%s\n(F) You tried to create a custom alias for a character name, with the \":alias\" option to\n\"use charnames\" and the specified character in the indicated name isn't valid.  See\n\"CUSTOM ALIASES\" in charnames.\n\nInvalid \\0 character in %s for %s: %s\\0%s\n(W syscalls) Embedded \\0 characters in pathnames or other system call arguments produce a\nwarning as of 5.20.  The parts after the \\0 were formerly ignored by system calls.\n\nInvalid character in \\N{...}; marked by <-- HERE in \\N{%s}\n(F) Only certain characters are valid for character names.  The indicated one isn't.  See\n\"CUSTOM ALIASES\" in charnames.\n\nInvalid conversion in %s: \"%s\"\n(W printf) Perl does not understand the given format conversion.  See \"sprintf\" in\nperlfunc.\n\nInvalid escape in the specified encoding in regex; marked by <-- HERE in m/%s/\n(W regexp)(F) The numeric escape (for example \"\\xHH\") of value < 256 didn't correspond to\na single character through the conversion from the encoding specified by the encoding\npragma.  The escape was replaced with REPLACEMENT CHARACTER (U+FFFD) instead, except\nwithin \"(?[   ])\", where it is a fatal error.  The <-- HERE shows whereabouts in the\nregular expression the escape was discovered.\n\nInvalid hexadecimal number in \\N{U+...}\nInvalid hexadecimal number in \\N{U+...} in regex; marked by <-- HERE in m/%s/\n(F) The character constant represented by \"...\" is not a valid hexadecimal number.\nEither it is empty, or you tried to use a character other than 0 - 9 or A - F, a - f in a\nhexadecimal number.\n\nInvalid module name %s with -%c option: contains single ':'\n(F) The module argument to perl's -m and -M command-line options cannot contain single\ncolons in the module name, but only in the arguments after \"=\".  In other words,\n-MFoo::Bar=:baz is ok, but -MFoo:Bar=baz is not.\n\nInvalid mro name: '%s'\n(F) You tried to \"mro::setmro(\"classname\", \"foo\")\" or \"use mro 'foo'\", where \"foo\" is\nnot a valid method resolution order (MRO).  Currently, the only valid ones supported are\n\"dfs\" and \"c3\", unless you have loaded a module that is a MRO plugin.  See mro and\nperlmroapi.\n\nInvalid negative number (%s) in chr\n(W utf8) You passed a negative number to \"chr\".  Negative numbers are not valid character\nnumbers, so it returns the Unicode replacement character (U+FFFD).\n\nInvalid number '%s' for -C option.\n(F) You supplied a number to the -C option that either has extra leading zeroes or\noverflows perl's unsigned integer representation.\n\ninvalid option -D%c, use -D'' to see choices\n(S debugging) Perl was called with invalid debugger flags.  Call perl with the -D option\nwith no flags to see the list of acceptable values.  See also \"-Dletters\" in perlrun.\n\nInvalid quantifier in {,} in regex; marked by <-- HERE in m/%s/\n(F) The pattern looks like a {min,max} quantifier, but the min or max could not be parsed\nas a valid number - either it has leading zeroes, or it represents too big a number to\ncope with.  The <-- HERE shows where in the regular expression the problem was\ndiscovered.  See perlre.\n\nInvalid [] range \"%s\" in regex; marked by <-- HERE in m/%s/\n(F) The range specified in a character class had a minimum character greater than the\nmaximum character.  One possibility is that you forgot the \"{}\" from your ending \"\\x{}\" -\n\"\\x\" without the curly braces can go only up to \"ff\".  The <-- HERE shows whereabouts in\nthe regular expression the problem was discovered.  See perlre.\n\nInvalid range \"%s\" in transliteration operator\n(F) The range specified in the tr/// or y/// operator had a minimum character greater\nthan the maximum character.  See perlop.\n\nInvalid reference to group in regex; marked by <-- HERE in m/%s/\n(F) The capture group you specified can't possibly exist because the number you used is\nnot within the legal range of possible values for this machine.\n\nInvalid separator character %s in attribute list\n(F) Something other than a colon or whitespace was seen between the elements of an\nattribute list.  If the previous attribute had a parenthesised parameter list, perhaps\nthat list was terminated too soon.  See attributes.\n\nInvalid separator character %s in PerlIO layer specification %s\n(W layer) When pushing layers onto the Perl I/O system, something other than a colon or\nwhitespace was seen between the elements of a layer list.  If the previous attribute had\na parenthesised parameter list, perhaps that list was terminated too soon.\n\nInvalid strict version format (%s)\n(F) A version number did not meet the \"strict\" criteria for versions.  A \"strict\" version\nnumber is a positive decimal number (integer or decimal-fraction) without exponentiation\nor else a dotted-decimal v-string with a leading 'v' character and at least three\ncomponents.  The parenthesized text indicates which criteria were not met.  See the\nversion module for more details on allowed version formats.\n\nInvalid type '%s' in %s\n(F) The given character is not a valid pack or unpack type.  See \"pack\" in perlfunc.\n\n(W) The given character is not a valid pack or unpack type but used to be silently\nignored.\n\nInvalid version format (%s)\n(F) A version number did not meet the \"lax\" criteria for versions.  A \"lax\" version\nnumber is a positive decimal number (integer or decimal-fraction) without exponentiation\nor else a dotted-decimal v-string.  If the v-string has fewer than three components, it\nmust have a leading 'v' character.  Otherwise, the leading 'v' is optional.  Both decimal\nand dotted-decimal versions may have a trailing \"alpha\" component separated by an\nunderscore character after a fractional or dotted-decimal component.  The parenthesized\ntext indicates which criteria were not met.  See the version module for more details on\nallowed version formats.\n\nInvalid version object\n(F) The internal structure of the version object was invalid.  Perhaps the internals were\nmodified directly in some way or an arbitrary reference was blessed into the \"version\"\nclass.\n\nIn '(*VERB...)', the '(' and '*' must be adjacent in regex; marked by <-- HERE in m/%s/\nInverting a character class which contains a multi-character sequence is illegal in regex;\nmarked by <-- HERE in m/%s/\n(F) You wrote something like\n\nqr/\\P{name=KATAKANA LETTER AINU P}/\nqr/[^\\p{name=KATAKANA LETTER AINU P}]/\n\nThis name actually evaluates to a sequence of two Katakana characters, not just a single\none, and it is illegal to try to take the complement of a sequence.  (Mathematically it\nwould mean any sequence of characters from 0 to infinity in length that weren't these two\nin a row, and that is likely not of any real use.)\n\n(F) The two-character sequence \"(*\" in this context in a regular expression pattern\nshould be an indivisible token, with nothing intervening between the \"(\" and the \"*\", but\nyou separated them.\n\nioctl is not implemented\n(F) Your machine apparently doesn't implement ioctl(), which is pretty strange for a\nmachine that supports C.\n\nioctl() on unopened %s\n(W unopened) You tried ioctl() on a filehandle that was never opened.  Check your control\nflow and number of arguments.\n\nIO layers (like '%s') unavailable\n(F) Your Perl has not been configured to have PerlIO, and therefore you cannot use IO\nlayers.  To have PerlIO, Perl must be configured with 'useperlio'.\n\nIO::Socket::atmark not implemented on this architecture\n(F) Your machine doesn't implement the sockatmark() functionality, neither as a system\ncall nor an ioctl call (SIOCATMARK).\n\n'%s' is an unknown bound type in regex; marked by <-- HERE in m/%s/\n(F) You used \"\\b{...}\" or \"\\B{...}\" and the \"...\" is not known to Perl.  The current\nvalid ones are given in \"\\b{}, \\b, \\B{}, \\B\" in perlrebackslash.\n\n%s is forbidden - matches null string many times in regex; marked by <-- HERE in m/%s/\n(F) The pattern you've specified might cause the regular expression to infinite loop so\nit is forbidden.  The <-- HERE shows whereabouts in the regular expression the problem\nwas discovered.  See perlre.\n\n%s() isn't allowed on :utf8 handles\n(F) The sysread(), recv(), syswrite() and send() operators are not allowed on handles\nthat have the \":utf8\" layer, either explicitly, or implicitly, eg., with the\n\":encoding(UTF-16LE)\" layer.\n\nPreviously sysread() and recv() currently use only the \":utf8\" flag for the stream,\nignoring the actual layers.  Since sysread() and recv() did no UTF-8 validation they can\nend up creating invalidly encoded scalars.\n\nSimilarly, syswrite() and send() used only the \":utf8\" flag, otherwise ignoring any\nlayers.  If the flag is set, both wrote the value UTF-8 encoded, even if the layer is\nsome different encoding, such as the example above.\n\nIdeally, all of these operators would completely ignore the \":utf8\" state, working only\nwith bytes, but this would result in silently breaking existing code.\n\n\"%s\" is more clearly written simply as \"%s\" in regex; marked by <-- HERE in m/%s/\n(W regexp) (only under \"use re 'strict'\" or within \"(?[...])\")\n\nYou specified a character that has the given plainer way of writing it, and which is also\nportable to platforms running with different character sets.\n\n$* is no longer supported as of Perl 5.30\n(F) The special variable $*, deprecated in older perls, was removed in 5.10.0, is no\nlonger supported and is a fatal error as of Perl 5.30.  In previous versions of perl the\nuse of $* enabled or disabled multi-line matching within a string.\n\nInstead of using $* you should use the \"/m\" (and maybe \"/s\") regexp modifiers.  You can\nenable \"/m\" for a lexical scope (even a whole file) with \"use re '/m'\".  (In older\nversions: when $* was set to a true value then all regular expressions behaved as if they\nwere written using \"/m\".)\n\nUse of this variable will be a fatal error in Perl 5.30.\n\n$# is no longer supported as of Perl 5.30\n(F) The special variable $#, deprecated in older perls, was removed as of 5.10.0, is no\nlonger supported and is a fatal error as of Perl 5.30.  You should use the printf/sprintf\nfunctions instead.\n\n'%s' is not a code reference\n(W overload) The second (fourth, sixth, ...) argument of overload::constant needs to be a\ncode reference.  Either an anonymous subroutine, or a reference to a subroutine.\n\n'%s' is not an overloadable type\n(W overload) You tried to overload a constant type the overload package is unaware of.\n\nisa is experimental\n(S experimental::isa) This warning is emitted if you use the (\"isa\") operator. This\noperator is currently experimental and its behaviour may change in future releases of\nPerl.\n\n-i used with no filenames on the command line, reading from STDIN\n(S inplace) The \"-i\" option was passed on the command line, indicating that the script is\nintended to edit files in place, but no files were given.  This is usually a mistake,\nsince editing STDIN in place doesn't make sense, and can be confusing because it can make\nperl look like it is hanging when it is really just trying to read from STDIN.  You\nshould either pass a filename to edit, or remove \"-i\" from the command line.  See perlrun\nfor more details.\n\nJunk on end of regexp in regex m/%s/\n(P) The regular expression parser is confused.\n\n\\K not permitted in lookahead/lookbehind in regex; marked by <-- HERE in m/%s/\n(F) Your regular expression used \"\\K\" in a lookahead or lookbehind assertion, which\ncurrently isn't permitted.\n\nThis may change in the future, see Support \\K in lookarounds\n<https://github.com/Perl/perl5/issues/18134>.\n\nLabel not found for \"last %s\"\n(F) You named a loop to break out of, but you're not currently in a loop of that name,\nnot even if you count where you were called from.  See \"last\" in perlfunc.\n\nLabel not found for \"next %s\"\n(F) You named a loop to continue, but you're not currently in a loop of that name, not\neven if you count where you were called from.  See \"last\" in perlfunc.\n\nLabel not found for \"redo %s\"\n(F) You named a loop to restart, but you're not currently in a loop of that name, not\neven if you count where you were called from.  See \"last\" in perlfunc.\n\nleaving effective %s failed\n(F) While under the \"use filetest\" pragma, switching the real and effective uids or gids\nfailed.\n\nlength/code after end of string in unpack\n(F) While unpacking, the string buffer was already used up when an unpack length/code\ncombination tried to obtain more data.  This results in an undefined value for the\nlength.  See \"pack\" in perlfunc.\n\nlength() used on %s (did you mean \"scalar(%s)\"?)\n(W syntax) You used length() on either an array or a hash when you probably wanted a\ncount of the items.\n\nArray size can be obtained by doing:\n\nscalar(@array);\n\nThe number of items in a hash can be obtained by doing:\n\nscalar(keys %hash);\n\nLexing code attempted to stuff non-Latin-1 character into Latin-1 input\n(F) An extension is attempting to insert text into the current parse (using lexstuffpvn\nor similar), but tried to insert a character that couldn't be part of the current input.\nThis is an inherent pitfall of the stuffing mechanism, and one of the reasons to avoid\nit.  Where it is necessary to stuff, stuffing only plain ASCII is recommended.\n\nLexing code internal error (%s)\n(F) Lexing code supplied by an extension violated the lexer's API in a detectable way.\n\nlisten() on closed socket %s\n(W closed) You tried to do a listen on a closed socket.  Did you forget to check the\nreturn value of your socket() call?  See \"listen\" in perlfunc.\n\nList form of piped open not implemented\n(F) On some platforms, notably Windows, the three-or-more-arguments form of \"open\" does\nnot support pipes, such as \"open($pipe, '|-', @args)\".  Use the two-argument \"open($pipe,\n'|prog arg1 arg2...')\" form instead.\n\nLiteral vertical space in [] is illegal except under /x in regex; marked by <-- HERE in m/%s/\n(F) (only under \"use re 'strict'\" or within \"(?[...])\")\n\nLikely you forgot the \"/x\" modifier or there was a typo in the pattern.  For example, did\nyou really mean to match a form-feed?  If so, all the ASCII vertical space control\ncharacters are representable by escape sequences which won't present such a jarring\nappearance as your pattern does when displayed.\n\n\\r    carriage return\n\\f    form feed\n\\n    line feed\n\\cK   vertical tab\n\n%s: loadable library and perl binaries are mismatched (got handshake key %p, needed %p)\n(P) A dynamic loading library \".so\" or \".dll\" was being loaded into the process that was\nbuilt against a different build of perl than the said library was compiled against.\nReinstalling the XS module will likely fix this error.\n\nLocale '%s' contains (at least) the following characters which have unexpected meanings: %s\nThe Perl program will use the expected meanings\n(W locale) You are using the named UTF-8 locale.  UTF-8 locales are expected to have very\nparticular behavior, which most do.  This message arises when perl found some departures\nfrom the expectations, and is notifying you that the expected behavior overrides these\ndifferences.  In some cases the differences are caused by the locale definition being\ndefective, but the most common causes of this warning are when there are ambiguities and\nconflicts in following the Standard, and the locale has chosen an approach that differs\nfrom Perl's.\n\nOne of these is because that, contrary to the claims, Unicode is not completely locale\ninsensitive.  Turkish and some related languages have two types of \"I\" characters.  One\nis dotted in both upper- and lowercase, and the other is dotless in both cases.  Unicode\nallows a locale to use either the Turkish rules, or the rules used in all other\ninstances, where there is only one type of \"I\", which is dotless in the uppercase, and\ndotted in the lower.  The perl core does not (yet) handle the Turkish case, and this\nmessage warns you of that.  Instead, the Unicode::Casing module allows you to mostly\nimplement the Turkish casing rules.\n\nThe other common cause is for the characters\n\n$ + < = > ^ ` | ~\n\nThese are problematic.  The C standard says that these should be considered punctuation\nin the C locale (and the POSIX standard defers to the C standard), and Unicode is\ngenerally considered a superset of the C locale.  But Unicode has added an extra\ncategory, \"Symbol\", and classifies these particular characters as being symbols.  Most\nUTF-8 locales have them treated as punctuation, so that ispunct(2) returns non-zero for\nthem.  But a few locales have it return 0.   Perl takes the first approach, not using\n\"ispunct()\" at all (see Note [5] in perlrecharclass), and this message is raised to\nnotify you that you are getting Perl's approach, not the locale's.\n\nLocale '%s' may not work well.%s\n(W locale) You are using the named locale, which is a non-UTF-8 one, and which perl has\ndetermined is not fully compatible with what it can handle.  The second %s gives a\nreason.\n\nBy far the most common reason is that the locale has characters in it that are\nrepresented by more than one byte.  The only such locales that Perl can handle are the\nUTF-8 locales.  Most likely the specified locale is a non-UTF-8 one for an East Asian\nlanguage such as Chinese or Japanese.  If the locale is a superset of ASCII, the ASCII\nportion of it may work in Perl.\n\nSome essentially obsolete locales that aren't supersets of ASCII, mainly those in ISO 646\nor other 7-bit locales, such as ASMO 449, can also have problems, depending on what\nportions of the ASCII character set get changed by the locale and are also used by the\nprogram.  The warning message lists the determinable conflicting characters.\n\nNote that not all incompatibilities are found.\n\nIf this happens to you, there's not much you can do except switch to use a different\nlocale or use Encode to translate from the locale into UTF-8; if that's impracticable,\nyou have been warned that some things may break.\n\nThis message is output once each time a bad locale is switched into within the scope of\n\"use locale\", or on the first possibly-affected operation if the \"use locale\" inherits a\nbad one.  It is not raised for any operations from the POSIX module.\n\nlocaltime(%f) failed\n(W overflow) You called \"localtime\" with a number that it could not handle: too large,\ntoo small, or NaN.  The returned value is \"undef\".\n\nlocaltime(%f) too large\n(W overflow) You called \"localtime\" with a number that was larger than it can reliably\nhandle and \"localtime\" probably returned the wrong date.  This warning is also triggered\nwith NaN (the special not-a-number value).\n\nlocaltime(%f) too small\n(W overflow) You called \"localtime\" with a number that was smaller than it can reliably\nhandle and \"localtime\" probably returned the wrong date.\n\nLookbehind longer than %d not implemented in regex m/%s/\n(F) There is currently a limit on the length of string which lookbehind can handle.  This\nrestriction may be eased in a future release.\n\nLost precision when %s %f by 1\n(W imprecision) You attempted to increment or decrement a value by one, but the result is\ntoo large for the underlying floating point representation to store accurately. Hence,\nthe target of \"++\" or \"--\" is increased or decreased by quite different value than one,\nsuch as zero (i.e. the target is unchanged) or two, due to rounding.  Perl issues this\nwarning because it has already switched from integers to floating point when values are\ntoo large for integers, and now even floating point is insufficient.  You may wish to\nswitch to using Math::BigInt explicitly.\n\nlstat() on filehandle%s\n(W io) You tried to do an lstat on a filehandle.  What did you mean by that?  lstat()\nmakes sense only on filenames.  (Perl did a fstat() instead on the filehandle.)\n\nlvalue attribute %s already-defined subroutine\n(W misc) Although attributes.pm allows this, turning the lvalue attribute on or off on a\nPerl subroutine that is already defined does not always work properly.  It may or may not\ndo what you want, depending on what code is inside the subroutine, with exact details\nsubject to change between Perl versions.  Only do this if you really know what you are\ndoing.\n\nlvalue attribute ignored after the subroutine has been defined\n(W misc) Using the \":lvalue\" declarative syntax to make a Perl subroutine an lvalue\nsubroutine after it has been defined is not permitted.  To make the subroutine an lvalue\nsubroutine, add the lvalue attribute to the definition, or put the \"sub foo :lvalue;\"\ndeclaration before the definition.\n\nSee also attributes.pm.\n\nMagical list constants are not supported\n(F) You assigned a magical array to a stash element, and then tried to use the subroutine\nfrom the same slot.  You are asking Perl to do something it cannot do, details subject to\nchange between Perl versions.\n\nMalformed integer in [] in pack\n(F) Between the brackets enclosing a numeric repeat count only digits are permitted.  See\n\"pack\" in perlfunc.\n\nMalformed integer in [] in unpack\n(F) Between the brackets enclosing a numeric repeat count only digits are permitted.  See\n\"pack\" in perlfunc.\n\nMalformed PERLLIBPREFIX\n(F) An error peculiar to OS/2.  PERLLIBPREFIX should be of the form\n\nprefix1;prefix2\n\nor\nprefix1 prefix2\n\nwith nonempty prefix1 and prefix2.  If \"prefix1\" is indeed a prefix of a builtin library\nsearch path, prefix2 is substituted.  The error may appear if components are not found,\nor are too long.  See \"PERLLIBPREFIX\" in perlos2.\n\nMalformed prototype for %s: %s\n(F) You tried to use a function with a malformed prototype.  The syntax of function\nprototypes is given a brief compile-time check for obvious errors like invalid\ncharacters.  A more rigorous check is run when the function is called.  Perhaps the\nfunction's author was trying to write a subroutine signature but didn't enable that\nfeature first (\"use feature 'signatures'\"), so the signature was instead interpreted as a\nbad prototype.\n\nMalformed UTF-8 character%s\n(S utf8)(F) Perl detected a string that should be UTF-8, but didn't comply with UTF-8\nencoding rules, or represents a code point whose ordinal integer value doesn't fit into\nthe word size of the current platform (overflows).  Details as to the exact malformation\nare given in the variable, %s, part of the message.\n\nOne possible cause is that you set the UTF8 flag yourself for data that you thought to be\nin UTF-8 but it wasn't (it was for example legacy 8-bit data).  To guard against this,\nyou can use \"Encode::decode('UTF-8', ...)\".\n\nIf you use the \":encoding(UTF-8)\" PerlIO layer for input, invalid byte sequences are\nhandled gracefully, but if you use \":utf8\", the flag is set without validating the data,\npossibly resulting in this error message.\n\nSee also \"Handling Malformed Data\" in Encode.\n\nMalformed UTF-8 returned by \\N{%s} immediately after '%s'\n(F) The charnames handler returned malformed UTF-8.\n\nMalformed UTF-8 string in \"%s\"\n(F) This message indicates a bug either in the Perl core or in XS code. Such code was\ntrying to find out if a character, allegedly stored internally encoded as UTF-8, was of a\ngiven type, such as being punctuation or a digit.  But the character was not encoded in\nlegal UTF-8.  The %s is replaced by a string that can be used by knowledgeable people to\ndetermine what the type being checked against was.\n\nPassing malformed strings was deprecated in Perl 5.18, and became fatal in Perl 5.26.\n\nMalformed UTF-8 string in '%c' format in unpack\n(F) You tried to unpack something that didn't comply with UTF-8 encoding rules and perl\nwas unable to guess how to make more progress.\n\nMalformed UTF-8 string in pack\n(F) You tried to pack something that didn't comply with UTF-8 encoding rules and perl was\nunable to guess how to make more progress.\n\nMalformed UTF-8 string in unpack\n(F) You tried to unpack something that didn't comply with UTF-8 encoding rules and perl\nwas unable to guess how to make more progress.\n\nMalformed UTF-16 surrogate\n(F) Perl thought it was reading UTF-16 encoded character data but while doing it Perl met\na malformed Unicode surrogate.\n\nMandatory parameter follows optional parameter\n(F) In a subroutine signature, you wrote something like \"$a = undef, $b\", making an\nearlier parameter optional and a later one mandatory.  Parameters are filled from left to\nright, so it's impossible for the caller to omit an earlier one and pass a later one.  If\nyou want to act as if the parameters are filled from right to left, declare the rightmost\noptional and then shuffle the parameters around in the subroutine's body.\n\nMatched non-Unicode code point 0x%X against Unicode property; may not be portable\n(S nonunicode) Perl allows strings to contain a superset of Unicode code points; each\ncode point may be as large as what is storable in a signed integer on your system, but\nthese may not be accepted by other languages/systems.  This message occurs when you\nmatched a string containing such a code point against a regular expression pattern, and\nthe code point was matched against a Unicode property, \"\\p{...}\" or \"\\P{...}\".  Unicode\nproperties are only defined on Unicode code points, so the result of this match is\nundefined by Unicode, but Perl (starting in v5.20) treats non-Unicode code points as if\nthey were typical unassigned Unicode ones, and matched this one accordingly.  Whether a\ngiven property matches these code points or not is specified in \"Properties accessible\nthrough \\p{} and \\P{}\" in perluniprops.\n\nThis message is suppressed (unless it has been made fatal) if it is immaterial to the\nresults of the match if the code point is Unicode or not.  For example, the property\n\"\\p{ASCIIHexDigit}\" only can match the 22 characters \"[0-9A-Fa-f]\", so obviously all\nother code points, Unicode or not, won't match it.  (And \"\\P{ASCIIHexDigit}\" will match\nevery code point except these 22.)\n\nGetting this message indicates that the outcome of the match arguably should have been\nthe opposite of what actually happened.  If you think that is the case, you may wish to\nmake the \"nonunicode\" warnings category fatal; if you agree with Perl's decision, you\nmay wish to turn off this category.\n\nSee \"Beyond Unicode code points\" in perlunicode for more information.\n\n%s matches null string many times in regex; marked by <-- HERE in m/%s/\n(W regexp) The pattern you've specified would be an infinite loop if the regular\nexpression engine didn't specifically check for that.  The <-- HERE shows whereabouts in\nthe regular expression the problem was discovered.  See perlre.\n\nMaximal count of pending signals (%u) exceeded\n(F) Perl aborted due to too high a number of signals pending.  This usually indicates\nthat your operating system tried to deliver signals too fast (with a very high priority),\nstarving the perl process from resources it would need to reach a point where it can\nprocess signals safely.  (See \"Deferred Signals (Safe Signals)\" in perlipc.)\n\n\"%s\" may clash with future reserved word\n(W) This warning may be due to running a perl5 script through a perl4 interpreter,\nespecially if the word that is being warned about is \"use\" or \"my\".\n\n'%' may not be used in pack\n(F) You can't pack a string by supplying a checksum, because the checksumming process\nloses information, and you can't go the other way.  See \"unpack\" in perlfunc.\n\nMethod for operation %s not found in package %s during blessing\n(F) An attempt was made to specify an entry in an overloading table that doesn't resolve\nto a valid subroutine.  See overload.\n\nMethod %s not permitted\nSee \"500 Server error\".\n\nMight be a runaway multi-line %s string starting on line %d\n(S) An advisory indicating that the previous error may have been caused by a missing\ndelimiter on a string or pattern, because it eventually ended earlier on the current\nline.\n\nMisplaced  in number\n(W syntax) An underscore (underbar) in a numeric constant did not separate two digits.\n\nMissing argument for %n in %s\n(F) A %n was used in a format string with no corresponding argument for perl to write the\ncurrent string length to.\n\nMissing argument in %s\n(W missing) You called a function with fewer arguments than other arguments you supplied\nindicated would be needed.\n\nCurrently only emitted when a printf-type format required more arguments than were\nsupplied, but might be used in the future for other cases where we can statically\ndetermine that arguments to functions are missing, e.g. for the \"pack\" in perlfunc\nfunction.\n\nMissing argument to -%c\n(F) The argument to the indicated command line switch must follow immediately after the\nswitch, without intervening spaces.\n\nMissing braces on \\N{}\nMissing braces on \\N{} in regex; marked by <-- HERE in m/%s/\n(F) Wrong syntax of character name literal \"\\N{charname}\" within double-quotish context.\nThis can also happen when there is a space (or comment) between the \"\\N\" and the \"{\" in a\nregex with the \"/x\" modifier.  This modifier does not change the requirement that the\nbrace immediately follow the \"\\N\".\n\nMissing braces on \\o{}\n(F) A \"\\o\" must be followed immediately by a \"{\" in double-quotish context.\n\nMissing comma after first argument to %s function\n(F) While certain functions allow you to specify a filehandle or an \"indirect object\"\nbefore the argument list, this ain't one of them.\n\nMissing command in piped open\n(W pipe) You used the \"open(FH, \"| command\")\" or \"open(FH, \"command |\")\" construction,\nbut the command was missing or blank.\n\nMissing control char name in \\c\n(F) A double-quoted string ended with \"\\c\", without the required control character name.\n\nMissing ']' in prototype for %s : %s\n(W illegalproto) A grouping was started with \"[\" but never closed with \"]\".\n\nMissing name in \"%s sub\"\n(F) The syntax for lexically scoped subroutines requires that they have a name with which\nthey can be found.\n\nMissing $ on loop variable\n(F) Apparently you've been programming in csh too much.  Variables are always mentioned\nwith the $ in Perl, unlike in the shells, where it can vary from one line to the next.\n\n(Missing operator before %s?)\n(S syntax) This is an educated guess made in conjunction with the message \"%s found where\noperator expected\".  Often the missing operator is a comma.\n\nMissing or undefined argument to %s\n(F) You tried to call require or do with no argument or with an undefined value as an\nargument.  Require expects either a package name or a file-specification as an argument;\ndo expects a filename.  See \"require EXPR\" in perlfunc and \"do EXPR\" in perlfunc.\n\nMissing right brace on \\%c{} in regex; marked by <-- HERE in m/%s/\n(F) Missing right brace in \"\\x{...}\", \"\\p{...}\", \"\\P{...}\", or \"\\N{...}\".\n\nMissing right brace on \\N{}\nMissing right brace on \\N{} or unescaped left brace after \\N\n(F) \"\\N\" has two meanings.\n\nThe traditional one has it followed by a name enclosed in braces, meaning the character\n(or sequence of characters) given by that name.  Thus \"\\N{ASTERISK}\" is another way of\nwriting \"*\", valid in both double-quoted strings and regular expression patterns.  In\npatterns, it doesn't have the meaning an unescaped \"*\" does.\n\nStarting in Perl 5.12.0, \"\\N\" also can have an additional meaning (only) in patterns,\nnamely to match a non-newline character.  (This is short for \"[^\\n]\", and like \".\" but is\nnot affected by the \"/s\" regex modifier.)\n\nThis can lead to some ambiguities.  When \"\\N\" is not followed immediately by a left\nbrace, Perl assumes the \"[^\\n]\" meaning.  Also, if the braces form a valid quantifier\nsuch as \"\\N{3}\" or \"\\N{5,}\", Perl assumes that this means to match the given quantity of\nnon-newlines (in these examples, 3; and 5 or more, respectively).  In all other case,\nwhere there is a \"\\N{\" and a matching \"}\", Perl assumes that a character name is desired.\n\nHowever, if there is no matching \"}\", Perl doesn't know if it was mistakenly omitted, or\nif \"[^\\n]{\" was desired, and raises this error.  If you meant the former, add the right\nbrace; if you meant the latter, escape the brace with a backslash, like so: \"\\N\\{\"\n\nMissing right curly or square bracket\n(F) The lexer counted more opening curly or square brackets than closing ones.  As a\ngeneral rule, you'll find it's missing near the place you were last editing.\n\n(Missing semicolon on previous line?)\n(S syntax) This is an educated guess made in conjunction with the message \"%s found where\noperator expected\".  Don't automatically put a semicolon on the previous line just\nbecause you saw this message.\n\nModification of a read-only value attempted\n(F) You tried, directly or indirectly, to change the value of a constant.  You didn't, of\ncourse, try \"2 = 1\", because the compiler catches that.  But an easy way to do the same\nthing is:\n\nsub mod { $[0] = 1 }\nmod(2);\n\nAnother way is to assign to a substr() that's off the end of the string.\n\nYet another way is to assign to a \"foreach\" loop VAR when VAR is aliased to a constant in\nthe look LIST:\n\n$x = 1;\nforeach my $n ($x, 2) {\n$n *= 2; # modifies the $x, but fails on attempt to\n}            # modify the 2\n\nPerlIO::scalar will also produce this message as a warning if you attempt to open a read-\nonly scalar for writing.\n\nModification of non-creatable array value attempted, %s\n(F) You tried to make an array value spring into existence, and the subscript was\nprobably negative, even counting from end of the array backwards.\n\nModification of non-creatable hash value attempted, %s\n(P) You tried to make a hash value spring into existence, and it couldn't be created for\nsome peculiar reason.\n\nModule name must be constant\n(F) Only a bare module name is allowed as the first argument to a \"use\".\n\nModule name required with -%c option\n(F) The \"-M\" or \"-m\" options say that Perl should load some module, but you omitted the\nname of the module.  Consult perlrun for full details about \"-M\" and \"-m\".\n\nMore than one argument to '%s' open\n(F) The \"open\" function has been asked to open multiple files.  This can happen if you\nare trying to open a pipe to a command that takes a list of arguments, but have forgotten\nto specify a piped open mode.  See \"open\" in perlfunc for details.\n\nmprotect for COW string %p %u failed with %d\n(S) You compiled perl with -DPERLDEBUGREADONLYCOW (see \"Copy on Write\" in perlguts),\nbut a shared string buffer could not be made read-only.\n\nmprotect for %p %u failed with %d\n(S) You compiled perl with -DPERLDEBUGREADONLYOPS (see perlhacktips), but an op tree\ncould not be made read-only.\n\nmprotect RW for COW string %p %u failed with %d\n(S) You compiled perl with -DPERLDEBUGREADONLYCOW (see \"Copy on Write\" in perlguts),\nbut a read-only shared string buffer could not be made mutable.\n\nmprotect RW for %p %u failed with %d\n(S) You compiled perl with -DPERLDEBUGREADONLYOPS (see perlhacktips), but a read-only\nop tree could not be made mutable before freeing the ops.\n\nmsg%s not implemented\n(F) You don't have System V message IPC on your system.\n\nMultidimensional hash lookup is disabled\n(F) You supplied a list of subscripts to a hash lookup under \"no feature\n\"multidimensional\";\", eg:\n\n$z = $foo{$x, $y};\n\nwhich by default acts like:\n\n$z = $foo{join($;, $x, $y)};\n\nMultidimensional syntax %s not supported\n(W syntax) Multidimensional arrays aren't written like $foo[1,2,3].  They're written like\n$foo[1][2][3], as in C.\n\nMultiple slurpy parameters not allowed\n(F) In subroutine signatures, a slurpy parameter (\"@\" or \"%\") must be the last parameter,\nand there must not be more than one of them; for example:\n\nsub foo ($a, @b)    {} # legal\nsub foo ($a, @b, %) {} # invalid\n\n'/' must follow a numeric type in unpack\n(F) You had an unpack template that contained a '/', but this did not follow some unpack\nspecification producing a numeric value.  See \"pack\" in perlfunc.\n\n%s must not be a named sequence in transliteration operator\n(F) Transliteration (\"tr///\" and \"y///\") transliterates individual characters.  But a\nnamed sequence by definition is more than an individual character, and hence doing this\noperation on it doesn't make sense.\n\n\"my sub\" not yet implemented\n(F) Lexically scoped subroutines are not yet implemented.  Don't try that yet.\n\n\"my\" subroutine %s can't be in a package\n(F) Lexically scoped subroutines aren't in a package, so it doesn't make sense to try to\ndeclare one with a package qualifier on the front.\n\n\"my %s\" used in sort comparison\n(W syntax) The package variables $a and $b are used for sort comparisons.  You used $a or\n$b in as an operand to the \"<=>\" or \"cmp\" operator inside a sort comparison block, and\nthe variable had earlier been declared as a lexical variable.  Either qualify the sort\nvariable with the package name, or rename the lexical variable.\n\n\"my\" variable %s can't be in a package\n(F) Lexically scoped variables aren't in a package, so it doesn't make sense to try to\ndeclare one with a package qualifier on the front.  Use local() if you want to localize a\npackage variable.\n\nName \"%s::%s\" used only once: possible typo\n(W once) Typographical errors often show up as unique variable names.  If you had a good\nreason for having a unique name, then just mention it again somehow to suppress the\nmessage.  The \"our\" declaration is also provided for this purpose.\n\nNOTE: This warning detects package symbols that have been used only once.  This means\nlexical variables will never trigger this warning.  It also means that all of the package\nvariables $c, @c, %c, as well as *c, &c, sub c{}, c(), and c (the filehandle or format)\nare considered the same; if a program uses $c only once but also uses any of the others\nit will not trigger this warning.  Symbols beginning with an underscore and symbols using\nspecial identifiers (q.v. perldata) are exempt from this warning.\n\nNeed exactly 3 octal digits in regex; marked by <-- HERE in m/%s/\n(F) Within \"(?[   ])\", all constants interpreted as octal need to be exactly 3 digits\nlong.  This helps catch some ambiguities.  If your constant is too short, add leading\nzeros, like\n\n(?[ [ \\078 ] ])     # Syntax error!\n(?[ [ \\0078 ] ])    # Works\n(?[ [ \\007 8 ] ])   # Clearer\n\nThe maximum number this construct can express is \"\\777\".  If you need a larger one, you\nneed to use \\o{} instead.  If you meant two separate things, you need to separate them:\n\n(?[ [ \\7776 ] ])        # Syntax error!\n(?[ [ \\o{7776} ] ])     # One meaning\n(?[ [ \\777 6 ] ])       # Another meaning\n(?[ [ \\777 \\006 ] ])    # Still another\n\nNegative '/' count in unpack\n(F) The length count obtained from a length/code unpack operation was negative.  See\n\"pack\" in perlfunc.\n\nNegative length\n(F) You tried to do a read/write/send/recv operation with a buffer length that is less\nthan 0.  This is difficult to imagine.\n\nNegative offset to vec in lvalue context\n(F) When \"vec\" is called in an lvalue context, the second argument must be greater than\nor equal to zero.\n\nNegative repeat count does nothing\n(W numeric) You tried to execute the \"x\" repetition operator fewer than 0 times, which\ndoesn't make sense.\n\nNested quantifiers in regex; marked by <-- HERE in m/%s/\n(F) You can't quantify a quantifier without intervening parentheses.  So things like\nor +* or ?* are illegal.  The <-- HERE shows whereabouts in the regular expression the\nproblem was discovered.\n\nNote that the minimal matching quantifiers, \"*?\", \"+?\", and \"??\" appear to be nested\nquantifiers, but aren't.  See perlre.\n\n%s never introduced\n(S internal) The symbol in question was declared but somehow went out of scope before it\ncould possibly have been used.\n\nnext::method/next::can/maybe::next::method cannot find enclosing method\n(F) \"next::method\" needs to be called within the context of a real method in a real\npackage, and it could not find such a context.  See mro.\n\n\\N in a character class must be a named character: \\N{...} in regex; marked by <-- HERE in\nm/%s/\n(F) The new (as of Perl 5.12) meaning of \"\\N\" as \"[^\\n]\" is not valid in a bracketed\ncharacter class, for the same reason that \".\" in a character class loses its specialness:\nit matches almost everything, which is probably not what you want.\n\n\\N{} here is restricted to one character in regex; marked by <-- HERE in m/%s/\n(F) Named Unicode character escapes (\"\\N{...}\") may return a multi-character sequence.\nEven though a character class is supposed to match just one character of input, perl will\nmatch the whole thing correctly, except under certain conditions.  These currently are\n\nWhen the class is inverted (\"[^...]\")\nThe mathematically logical behavior for what matches when inverting is very different\nfrom what people expect, so we have decided to forbid it.\n\nThe escape is the beginning or final end point of a range\nSimilarly unclear is what should be generated when the \"\\N{...}\" is used as one of\nthe end points of the range, such as in\n\n[\\x{41}-\\N{ARABIC SEQUENCE YEH WITH HAMZA ABOVE WITH AE}]\n\nWhat is meant here is unclear, as the \"\\N{...}\" escape is a sequence of code points,\nso this is made an error.\n\nIn a regex set\nThe syntax \"(?[   ])\" in a regular expression yields a list of single code points,\nnone can be a sequence.\n\nNo %s allowed while running setuid\n(F) Certain operations are deemed to be too insecure for a setuid or setgid script to\neven be allowed to attempt.  Generally speaking there will be another way to do what you\nwant that is, if not secure, at least securable.  See perlsec.\n\nNo code specified for -%c\n(F) Perl's -e and -E command-line options require an argument.  If you want to run an\nempty program, pass the empty string as a separate argument or run a program consisting\nof a single 0 or 1:\n\nperl -e \"\"\nperl -e0\nperl -e1\n\nNo comma allowed after %s\n(F) A list operator that has a filehandle or \"indirect object\" is not allowed to have a\ncomma between that and the following arguments.  Otherwise it'd be just another one of\nthe arguments.\n\nOne possible cause for this is that you expected to have imported a constant to your name\nspace with use or import while no such importing took place, it may for example be that\nyour operating system does not support that particular constant.  Hopefully you did use\nan explicit import list for the constants you expect to see; please see \"use\" in perlfunc\nand \"import\" in perlfunc.  While an explicit import list would probably have caught this\nerror earlier it naturally does not remedy the fact that your operating system still does\nnot support that constant.  Maybe you have a typo in the constants of the symbol import\nlist of use or import or in the constant name at the line where this error was triggered?\n\nNo command into which to pipe on command line\n(F) An error peculiar to VMS.  Perl handles its own command line redirection, and found a\n'|' at the end of the command line, so it doesn't know where you want to pipe the output\nfrom this command.\n\nNo DB::DB routine defined\n(F) The currently executing code was compiled with the -d switch, but for some reason the\ncurrent debugger (e.g. perl5db.pl or a \"Devel::\" module) didn't define a routine to be\ncalled at the beginning of each statement.\n\nNo dbm on this machine\n(P) This is counted as an internal error, because every machine should supply dbm\nnowadays, because Perl comes with SDBM.  See SDBMFile.\n\nNo DB::sub routine defined\n(F) The currently executing code was compiled with the -d switch, but for some reason the\ncurrent debugger (e.g. perl5db.pl or a \"Devel::\" module) didn't define a \"DB::sub\"\nroutine to be called at the beginning of each ordinary subroutine call.\n\nNo digits found for %s literal\n(F) No hexadecimal digits were found following \"0x\" or no binary digits were found\nfollowing \"0b\".\n\nNo directory specified for -I\n(F) The -I command-line switch requires a directory name as part of the same argument.\nUse -Ilib, for instance.  -I lib won't work.\n\nNo error file after 2> or 2>> on command line\n(F) An error peculiar to VMS.  Perl handles its own command line redirection, and found a\n'2>' or a '2>>' on the command line, but can't find the name of the file to which to\nwrite data destined for stderr.\n\nNo group ending character '%c' found in template\n(F) A pack or unpack template has an opening '(' or '[' without its matching counterpart.\nSee \"pack\" in perlfunc.\n\nNo input file after < on command line\n(F) An error peculiar to VMS.  Perl handles its own command line redirection, and found a\n'<' on the command line, but can't find the name of the file from which to read data for\nstdin.\n\nNo next::method '%s' found for %s\n(F) \"next::method\" found no further instances of this method name in the remaining\npackages of the MRO of this class.  If you don't want it throwing an exception, use\n\"maybe::next::method\" or \"next::can\".  See mro.\n\nNon-finite repeat count does nothing\n(W numeric) You tried to execute the \"x\" repetition operator \"Inf\" (or \"-Inf\") or \"NaN\"\ntimes, which doesn't make sense.\n\nNon-hex character in regex; marked by <-- HERE in m/%s/\n(F) In a regular expression, there was a non-hexadecimal character where a hex one was\nexpected, like\n\n(?[ [ \\xDG ] ])\n(?[ [ \\x{DEKA} ] ])\n\nNon-hex character '%c' terminates \\x early.  Resolved as \"%s\"\n(W digit) In parsing a hexadecimal numeric constant, a character was unexpectedly\nencountered that isn't hexadecimal.  The resulting value is as indicated.\n\nNote that, within braces, every character starting with the first non-hexadecimal up to\nthe ending brace is ignored.\n\nNon-octal character in regex; marked by <-- HERE in m/%s/\n(F) In a regular expression, there was a non-octal character where an octal one was\nexpected, like\n\n(?[ [ \\o{1278} ] ])\n\nNon-octal character '%c' terminates \\o early.  Resolved as \"%s\"\n(W digit) In parsing an octal numeric constant, a character was unexpectedly encountered\nthat isn't octal.  The resulting value is as indicated.\n\nWhen not using \"\\o{...}\", you wrote something like \"\\08\", or \"\\179\" in a double-quotish\nstring.  The resolution is as indicated, with all but the last digit treated as a single\ncharacter, specified in octal.  The last digit is the next character in the string.  To\ntell Perl that this is indeed what you want, you can use the \"\\o{ }\" syntax, or use\nexactly three digits to specify the octal for the character.\n\nNote that, within braces, every character starting with the first non-octal up to the\nending brace is ignored.\n\n\"no\" not allowed in expression\n(F) The \"no\" keyword is recognized and executed at compile time, and returns no useful\nvalue.  See perlmod.\n\nNon-string passed as bitmask\n(W misc) A number has been passed as a bitmask argument to select().  Use the vec()\nfunction to construct the file descriptor bitmasks for select.  See \"select\" in perlfunc.\n\nNo output file after > on command line\n(F) An error peculiar to VMS.  Perl handles its own command line redirection, and found a\nlone '>' at the end of the command line, so it doesn't know where you wanted to redirect\nstdout.\n\nNo output file after > or >> on command line\n(F) An error peculiar to VMS.  Perl handles its own command line redirection, and found a\n'>' or a '>>' on the command line, but can't find the name of the file to which to write\ndata destined for stdout.\n\nNo package name allowed for subroutine %s in \"our\"\nNo package name allowed for variable %s in \"our\"\n(F) Fully qualified subroutine and variable names are not allowed in \"our\" declarations,\nbecause that doesn't make much sense under existing rules.  Such syntax is reserved for\nfuture extensions.\n\nNo Perl script found in input\n(F) You called \"perl -x\", but no line was found in the file beginning with #! and\ncontaining the word \"perl\".\n\nNo setregid available\n(F) Configure didn't find anything resembling the setregid() call for your system.\n\nNo setreuid available\n(F) Configure didn't find anything resembling the setreuid() call for your system.\n\nNo such class %s\n(F) You provided a class qualifier in a \"my\", \"our\" or \"state\" declaration, but this\nclass doesn't exist at this point in your program.\n\nNo such class field \"%s\" in variable %s of type %s\n(F) You tried to access a key from a hash through the indicated typed variable but that\nkey is not allowed by the package of the same type.  The indicated package has restricted\nthe set of allowed keys using the fields pragma.\n\nNo such hook: %s\n(F) You specified a signal hook that was not recognized by Perl.  Currently, Perl accepts\n\"DIE\" and \"WARN\" as valid signal hooks.\n\nNo such pipe open\n(P) An error peculiar to VMS.  The internal routine mypclose() tried to close a pipe\nwhich hadn't been opened.  This should have been caught earlier as an attempt to close an\nunopened filehandle.\n\nNo such signal: SIG%s\n(W signal) You specified a signal name as a subscript to %SIG that was not recognized.\nSay \"kill -l\" in your shell to see the valid signal names on your system.\n\nNo Unicode property value wildcard matches:\n(W regexp) You specified a wildcard for a Unicode property value, but there is no\nproperty value in the current Unicode release that matches it.  Check your spelling.\n\nNot a CODE reference\n(F) Perl was trying to evaluate a reference to a code value (that is, a subroutine), but\nfound a reference to something else instead.  You can use the ref() function to find out\nwhat kind of ref it really was.  See also perlref.\n\nNot a GLOB reference\n(F) Perl was trying to evaluate a reference to a \"typeglob\" (that is, a symbol table\nentry that looks like *foo), but found a reference to something else instead.  You can\nuse the ref() function to find out what kind of ref it really was.  See perlref.\n\nNot a HASH reference\n(F) Perl was trying to evaluate a reference to a hash value, but found a reference to\nsomething else instead.  You can use the ref() function to find out what kind of ref it\nreally was.  See perlref.\n\n'#' not allowed immediately following a sigil in a subroutine signature\n(F) In a subroutine signature definition, a comment following a sigil (\"$\", \"@\" or \"%\"),\nneeds to be separated by whitespace or a comma etc., in particular to avoid confusion\nwith the $# variable.  For example:\n\n# bad\nsub f ($# ignore first arg\n, $b) {}\n# good\nsub f ($, # ignore first arg\n$b) {}\n\nNot an ARRAY reference\n(F) Perl was trying to evaluate a reference to an array value, but found a reference to\nsomething else instead.  You can use the ref() function to find out what kind of ref it\nreally was.  See perlref.\n\nNot a SCALAR reference\n(F) Perl was trying to evaluate a reference to a scalar value, but found a reference to\nsomething else instead.  You can use the ref() function to find out what kind of ref it\nreally was.  See perlref.\n\nNot a subroutine reference\n(F) Perl was trying to evaluate a reference to a code value (that is, a subroutine), but\nfound a reference to something else instead.  You can use the ref() function to find out\nwhat kind of ref it really was.  See also perlref.\n\nNot a subroutine reference in overload table\n(F) An attempt was made to specify an entry in an overloading table that doesn't somehow\npoint to a valid subroutine.  See overload.\n\nNot enough arguments for %s\n(F) The function requires more arguments than you specified.\n\nNot enough format arguments\n(W syntax) A format specified more picture fields than the next line supplied.  See\nperlform.\n\n%s: not found\n(A) You've accidentally run your script through the Bourne shell instead of Perl.  Check\nthe #! line, or manually feed your script into Perl yourself.\n\nno UTC offset information; assuming local time is UTC\n(S) A warning peculiar to VMS.  Perl was unable to find the local timezone offset, so\nit's assuming that local system time is equivalent to UTC.  If it's not, define the\nlogical name SYS$TIMEZONEDIFFERENTIAL to translate to the number of seconds which need\nto be added to UTC to get local time.\n\nNULL OP IN RUN\n(S debugging) Some internal routine called run() with a null opcode pointer.\n\nNull picture in formline\n(F) The first argument to formline must be a valid format picture specification.  It was\nfound to be empty, which probably means you supplied it an uninitialized value.  See\nperlform.\n\nNull realloc\n(P) An attempt was made to realloc NULL.\n\nNULL regexp argument\n(P) The internal pattern matching routines blew it big time.\n\nNULL regexp parameter\n(P) The internal pattern matching routines are out of their gourd.\n\nNumber too long\n(F) Perl limits the representation of decimal numbers in programs to about 250\ncharacters.  You've exceeded that length.  Future versions of Perl are likely to\neliminate this arbitrary limitation.  In the meantime, try using scientific notation\n(e.g. \"1e6\" instead of \"1000000\").\n\nNumber with no digits\n(F) Perl was looking for a number but found nothing that looked like a number.  This\nhappens, for example with \"\\o{}\", with no number between the braces.\n\nNumeric format result too large\n(F) The length of the result of a numeric format supplied to sprintf() or printf() would\nhave been too large for the underlying C function to report.  This limit is typically\n2GB.\n\nNumeric variables with more than one digit may not start with '0'\n(F) The only numeric variable which is allowed to start with a 0 is $0, and you mentioned\na variable that starts with 0 that has more than one digit. You probably want to remove\nthe leading 0, or if the intent was to express a variable name in octal you should\nconvert to decimal.\n\nOctal number > 037777777777 non-portable\n(W portable) The octal number you specified is larger than 232-1 (4294967295) and\ntherefore non-portable between systems.  See perlport for more on portability concerns.\n\nOdd name/value argument for subroutine '%s'\n(F) A subroutine using a slurpy hash parameter in its signature received an odd number of\narguments to populate the hash.  It requires the arguments to be paired, with the same\nnumber of keys as values.  The caller of the subroutine is presumably at fault.\n\nThe message attempts to include the name of the called subroutine. If the subroutine has\nbeen aliased, the subroutine's original name will be shown, regardless of what name the\ncaller used.\n\nOdd number of arguments for overload::constant\n(W overload) The call to overload::constant contained an odd number of arguments.  The\narguments should come in pairs.\n\nOdd number of elements in anonymous hash\n(W misc) You specified an odd number of elements to initialize a hash, which is odd,\nbecause hashes come in key/value pairs.\n\nOdd number of elements in hash assignment\n(W misc) You specified an odd number of elements to initialize a hash, which is odd,\nbecause hashes come in key/value pairs.\n\nOffset outside string\n(F)(W layer) You tried to do a read/write/send/recv/seek operation with an offset\npointing outside the buffer.  This is difficult to imagine.  The sole exceptions to this\nare that zero padding will take place when going past the end of the string when either\n\"sysread()\"ing a file, or when seeking past the end of a scalar opened for I/O (in\nanticipation of future reads and to imitate the behavior with real files).\n\nOld package separator used in string\n(W syntax) You used the old package separator, \"'\", in a variable named inside a double-\nquoted string; e.g., \"In $name's house\".  This is equivalent to \"In $name::s house\".  If\nyou meant the former, put a backslash before the apostrophe (\"In $name\\'s house\").\n\n%s() on unopened %s\n(W unopened) An I/O operation was attempted on a filehandle that was never initialized.\nYou need to do an open(), a sysopen(), or a socket() call, or call a constructor from the\nFileHandle package.\n\n-%s on unopened filehandle %s\n(W unopened) You tried to invoke a file test operator on a filehandle that isn't open.\nCheck your control flow.  See also \"-X\" in perlfunc.\n\noops: oopsAV\n(S internal) An internal warning that the grammar is screwed up.\n\noops: oopsHV\n(S internal) An internal warning that the grammar is screwed up.\n\nOperand with no preceding operator in regex; marked by <-- HERE in m/%s/\n(F) You wrote something like\n\n(?[ \\p{Digit} \\p{Thai} ])\n\nThere are two operands, but no operator giving how you want to combine them.\n\nOperation \"%s\": no method found, %s\n(F) An attempt was made to perform an overloaded operation for which no handler was\ndefined.  While some handlers can be autogenerated in terms of other handlers, there is\nno default handler for any operation, unless the \"fallback\" overloading key is specified\nto be true.  See overload.\n\nOperation \"%s\" returns its argument for non-Unicode code point 0x%X\n(S nonunicode) You performed an operation requiring Unicode rules on a code point that\nis not in Unicode, so what it should do is not defined.  Perl has chosen to have it do\nnothing, and warn you.\n\nIf the operation shown is \"ToFold\", it means that case-insensitive matching in a regular\nexpression was done on the code point.\n\nIf you know what you are doing you can turn off this warning by \"no warnings\n'nonunicode';\".\n\nOperation \"%s\" returns its argument for UTF-16 surrogate U+%X\n(S surrogate) You performed an operation requiring Unicode rules on a Unicode surrogate.\nUnicode frowns upon the use of surrogates for anything but storing strings in UTF-16, but\nrules are (reluctantly) defined for the surrogates, and they are to do nothing for this\noperation.  Because the use of surrogates can be dangerous, Perl warns.\n\nIf the operation shown is \"ToFold\", it means that case-insensitive matching in a regular\nexpression was done on the code point.\n\nIf you know what you are doing you can turn off this warning by \"no warnings\n'surrogate';\".\n\nOperator or semicolon missing before %s\n(S ambiguous) You used a variable or subroutine call where the parser was expecting an\noperator.  The parser has assumed you really meant to use an operator, but this is highly\nlikely to be incorrect.  For example, if you say \"*foo *foo\" it will be interpreted as if\nyou said \"*foo * 'foo'\".\n\nOptional parameter lacks default expression\n(F) In a subroutine signature, you wrote something like \"$a =\", making a named optional\nparameter without a default value.  A nameless optional parameter is permitted to have no\ndefault value, but a named one must have a specific default.  You probably want \"$a =\nundef\".\n\n\"our\" variable %s redeclared\n(W shadow) You seem to have already declared the same global once before in the current\nlexical scope.\n\nOut of memory!\n(X) The malloc() function returned 0, indicating there was insufficient remaining memory\n(or virtual memory) to satisfy the request.  Perl has no option but to exit immediately.\n\nAt least in Unix you may be able to get past this by increasing your process datasize\nlimits: in csh/tcsh use \"limit\" and \"limit datasize n\" (where \"n\" is the number of\nkilobytes) to check the current limits and change them, and in ksh/bash/zsh use \"ulimit\n-a\" and \"ulimit -d n\", respectively.\n\nOut of memory during %s extend\n(X) An attempt was made to extend an array, a list, or a string beyond the largest\npossible memory allocation.\n\nOut of memory during \"large\" request for %s\n(F) The malloc() function returned 0, indicating there was insufficient remaining memory\n(or virtual memory) to satisfy the request.  However, the request was judged large enough\n(compile-time default is 64K), so a possibility to shut down by trapping this error is\ngranted.\n\nOut of memory during request for %s\n(X)(F) The malloc() function returned 0, indicating there was insufficient remaining\nmemory (or virtual memory) to satisfy the request.\n\nThe request was judged to be small, so the possibility to trap it depends on the way perl\nwas compiled.  By default it is not trappable.  However, if compiled for this, Perl may\nuse the contents of $^M as an emergency pool after die()ing with this message.  In this\ncase the error is trappable once, and the error message will include the line and file\nwhere the failed request happened.\n\nOut of memory during ridiculously large request\n(F) You can't allocate more than 2^31+\"small amount\" bytes.  This error is most likely to\nbe caused by a typo in the Perl program. e.g., $arr[time] instead of $arr[$time].\n\nOut of memory for yacc stack\n(F) The yacc parser wanted to grow its stack so it could continue parsing, but realloc()\nwouldn't give it more memory, virtual or otherwise.\n\n'.' outside of string in pack\n(F) The argument to a '.' in your template tried to move the working position to before\nthe start of the packed string being built.\n\n'@' outside of string in unpack\n(F) You had a template that specified an absolute position outside the string being\nunpacked.  See \"pack\" in perlfunc.\n\n'@' outside of string with malformed UTF-8 in unpack\n(F) You had a template that specified an absolute position outside the string being\nunpacked.  The string being unpacked was also invalid UTF-8.  See \"pack\" in perlfunc.\n\noverload arg '%s' is invalid\n(W overload) The overload pragma was passed an argument it did not recognize.  Did you\nmistype an operator?\n\nOverloaded dereference did not return a reference\n(F) An object with an overloaded dereference operator was dereferenced, but the\noverloaded operation did not return a reference.  See overload.\n\nOverloaded qr did not return a REGEXP\n(F) An object with a \"qr\" overload was used as part of a match, but the overloaded\noperation didn't return a compiled regexp.  See overload.\n\n%s package attribute may clash with future reserved word: %s\n(W reserved) A lowercase attribute name was used that had a package-specific handler.\nThat name might have a meaning to Perl itself some day, even though it doesn't yet.\nPerhaps you should use a mixed-case attribute name, instead.  See attributes.\n\npack/unpack repeat count overflow\n(F) You can't specify a repeat count so large that it overflows your signed integers.\nSee \"pack\" in perlfunc.\n\npage overflow\n(W io) A single call to write() produced more lines than can fit on a page.  See\nperlform.\n\npanic: %s\n(P) An internal error.\n\npanic: attempt to call %s in %s\n(P) One of the file test operators entered a code branch that calls an ACL related-\nfunction, but that function is not available on this platform.  Earlier checks mean that\nit should not be possible to enter this branch on this platform.\n\npanic: child pseudo-process was never scheduled\n(P) A child pseudo-process in the ithreads implementation on Windows was not scheduled\nwithin the time period allowed and therefore was not able to initialize properly.\n\npanic: ckgrep, type=%u\n(P) Failed an internal consistency check trying to compile a grep.\n\npanic: corrupt saved stack index %ld\n(P) The savestack was requested to restore more localized values than there are in the\nsavestack.\n\npanic: delbackref\n(P) Failed an internal consistency check while trying to reset a weak reference.\n\npanic: dosubst\n(P) The internal ppsubst() routine was called with invalid operational data.\n\npanic: dotrans%s\n(P) The internal dotrans routines were called with invalid operational data.\n\npanic: foldconstants JMPENVPUSH returned %d\n(P) While attempting folding constants an exception other than an \"eval\" failure was\ncaught.\n\npanic: frexp: %f\n(P) The library function frexp() failed, making printf(\"%f\") impossible.\n\npanic: goto, type=%u, ix=%ld\n(P) We popped the context stack to a context with the specified label, and then\ndiscovered it wasn't a context we know how to do a goto in.\n\npanic: gpfree failed to free glob pointer\n(P) The internal routine used to clear a typeglob's entries tried repeatedly, but each\ntime something re-created entries in the glob.  Most likely the glob contains an object\nwith a reference back to the glob and a destructor that adds a new object to the glob.\n\npanic: INTERPCASEMOD, %s\n(P) The lexer got into a bad state at a case modifier.\n\npanic: INTERPCONCAT, %s\n(P) The lexer got into a bad state parsing a string with brackets.\n\npanic: kid popen errno read\n(F) A forked child returned an incomprehensible message about its errno.\n\npanic: last, type=%u\n(P) We popped the context stack to a block context, and then discovered it wasn't a block\ncontext.\n\npanic: leavescope clearsv\n(P) A writable lexical variable became read-only somehow within the scope.\n\npanic: leavescope inconsistency %u\n(P) The savestack probably got out of sync.  At least, there was an invalid enum on the\ntop of it.\n\npanic: magickillbackrefs\n(P) Failed an internal consistency check while trying to reset all weak references to an\nobject.\n\npanic: malloc, %s\n(P) Something requested a negative number of bytes of malloc.\n\npanic: memory wrap\n(P) Something tried to allocate either more memory than possible or a negative amount.\n\npanic: padalloc, %p!=%p\n(P) The compiler got confused about which scratch pad it was allocating and freeing\ntemporaries and lexicals from.\n\npanic: padfree curpad, %p!=%p\n(P) The compiler got confused about which scratch pad it was allocating and freeing\ntemporaries and lexicals from.\n\npanic: padfree po\n(P) A zero scratch pad offset was detected internally.  An attempt was made to free a\ntarget that had not been allocated to begin with.\n\npanic: padreset curpad, %p!=%p\n(P) The compiler got confused about which scratch pad it was allocating and freeing\ntemporaries and lexicals from.\n\npanic: padsv po\n(P) A zero scratch pad offset was detected internally.  Most likely an operator needed a\ntarget but that target had not been allocated for whatever reason.\n\npanic: padswipe curpad, %p!=%p\n(P) The compiler got confused about which scratch pad it was allocating and freeing\ntemporaries and lexicals from.\n\npanic: padswipe po\n(P) An invalid scratch pad offset was detected internally.\n\npanic: ppiter, type=%u\n(P) The foreach iterator got called in a non-loop context frame.\n\npanic: ppmatch%s\n(P) The internal ppmatch() routine was called with invalid operational data.\n\npanic: realloc, %s\n(P) Something requested a negative number of bytes of realloc.\n\npanic: reference miscount on nsv in svreplace() (%d != 1)\n(P) The internal svreplace() function was handed a new SV with a reference count other\nthan 1.\n\npanic: restartop in %s\n(P) Some internal routine requested a goto (or something like it), and didn't supply the\ndestination.\n\npanic: return, type=%u\n(P) We popped the context stack to a subroutine or eval context, and then discovered it\nwasn't a subroutine or eval context.\n\npanic: scannum, %s\n(P) scannum() got called on something that wasn't a number.\n\npanic: Sequence (?{...}): no code block found in regex m/%s/\n(P) While compiling a pattern that has embedded (?{}) or (??{}) code blocks, perl\ncouldn't locate the code block that should have already been seen and compiled by perl\nbefore control passed to the regex compiler.\n\npanic: strxfrm() gets absurd - a => %u, ab => %u\n(P) The interpreter's sanity check of the C function strxfrm() failed.  In your current\nlocale the returned transformation of the string \"ab\" is shorter than that of the string\n\"a\", which makes no sense.\n\npanic: svchop %s\n(P) The svchop() routine was passed a position that is not within the scalar's string\nbuffer.\n\npanic: svinsert, midend=%p, bigend=%p\n(P) The svinsert() routine was told to remove more string than there was string.\n\npanic: topenv\n(P) The compiler attempted to do a goto, or something weird like that.\n\npanic: unimplemented op %s (#%d) called\n(P) The compiler is screwed up and attempted to use an op that isn't permitted at run\ntime.\n\npanic: unknown OA*: %x\n(P) The internal routine that handles arguments to \"&CORE::foo()\" subroutine calls was\nunable to determine what type of arguments were expected.\n\npanic: utf16toutf8: odd bytelen\n(P) Something tried to call utf16toutf8 with an odd (as opposed to even) byte length.\n\npanic: utf16toutf8reversed: odd bytelen\n(P) Something tried to call utf16toutf8reversed with an odd (as opposed to even) byte\nlength.\n\npanic: yylex, %s\n(P) The lexer got into a bad state while processing a case modifier.\n\nParentheses missing around \"%s\" list\n(W parenthesis) You said something like\n\nmy $foo, $bar = @;\n\nwhen you meant\n\nmy ($foo, $bar) = @;\n\nRemember that \"my\", \"our\", \"local\" and \"state\" bind tighter than comma.\n\nParsing code internal error (%s)\n(F) Parsing code supplied by an extension violated the parser's API in a detectable way.\n\nPattern subroutine nesting without pos change exceeded limit in regex\n(F) You used a pattern that uses too many nested subpattern calls without consuming any\ntext.  Restructure the pattern so text is consumed before the nesting limit is exceeded.\n\n\"-p\" destination: %s\n(F) An error occurred during the implicit output invoked by the \"-p\" command-line switch.\n(This output goes to STDOUT unless you've redirected it with select().)\n\nPerl API version %s of %s does not match %s\n(F) The XS module in question was compiled against a different incompatible version of\nPerl than the one that has loaded the XS module.\n\nPerl folding rules are not up-to-date for 0x%X; please use the perlbug utility to report; in\nregex; marked by <-- HERE in m/%s/\n(S regexp) You used a regular expression with case-insensitive matching, and there is a\nbug in Perl in which the built-in regular expression folding rules are not accurate.\nThis may lead to incorrect results.  Please report this as a bug to\n<https://github.com/Perl/perl5/issues>.\n\nPerlIO layer ':win32' is experimental\n(S experimental::win32perlio) The \":win32\" PerlIO layer is experimental.  If you want to\ntake the risk of using this layer, simply disable this warning:\n\nno warnings \"experimental::win32perlio\";\n\nPerlmy%s() not available\n(F) Your platform has very uncommon byte-order and integer size, so it was not possible\nto set up some or all fixed-width byte-order conversion functions.  This is only a\nproblem when you're using the '<' or '>' modifiers in (un)pack templates.  See \"pack\" in\nperlfunc.\n\nPerl %s required (did you mean %s?)--this is only %s, stopped\n(F) The code you are trying to run has asked for a newer version of Perl than you are\nrunning.  Perhaps \"use 5.10\" was written instead of \"use 5.010\" or \"use v5.10\".  Without\nthe leading \"v\", the number is interpreted as a decimal, with every three digits after\nthe decimal point representing a part of the version number.  So 5.10 is equivalent to\nv5.100.\n\nPerl %s required--this is only %s, stopped\n(F) The module in question uses features of a version of Perl more recent than the\ncurrently running version.  How long has it been since you upgraded, anyway?  See\n\"require\" in perlfunc.\n\nPERLSHDIR too long\n(F) An error peculiar to OS/2.  PERLSHDIR is the directory to find the \"sh\"-shell in.\nSee \"PERLSHDIR\" in perlos2.\n\nPERLSIGNALS illegal: \"%s\"\n(X) See \"PERLSIGNALS\" in perlrun for legal values.\n\nPerls since %s too modern--this is %s, stopped\n(F) The code you are trying to run claims it will not run on the version of Perl you are\nusing because it is too new.  Maybe the code needs to be updated, or maybe it is simply\nwrong and the version check should just be removed.\n\nperl: warning: Non hex character in '$ENV{PERLHASHSEED}', seed only partially set\n(S) PERLHASHSEED should match /^\\s*(?:0x)?[0-9a-fA-F]+\\s*\\z/ but it contained a non hex\ncharacter.  This could mean you are not using the hash seed you think you are.\n\nperl: warning: Setting locale failed.\n(S) The whole warning message will look something like:\n\nperl: warning: Setting locale failed.\nperl: warning: Please check that your locale settings:\nLCALL = \"EnUS\",\nLANG = (unset)\nare supported and installed on your system.\nperl: warning: Falling back to the standard locale (\"C\").\n\nExactly what were the failed locale settings varies.  In the above the settings were that\nthe LCALL was \"EnUS\" and the LANG had no value.  This error means that Perl detected\nthat you and/or your operating system supplier and/or system administrator have set up\nthe so-called locale system but Perl could not use those settings.  This was not dead\nserious, fortunately: there is a \"default locale\" called \"C\" that Perl can and will use,\nand the script will be run.  Before you really fix the problem, however, you will get the\nsame error message each time you run Perl.  How to really fix the problem can be found in\nperllocale section LOCALE PROBLEMS.\n\nperl: warning: strange setting in '$ENV{PERLPERTURBKEYS}': '%s'\n(S) Perl was run with the environment variable PERLPERTURBKEYS defined but containing\nan unexpected value.  The legal values of this setting are as follows.\n\nNumeric | String        | Result\n--------+---------------+-----------------------------------------\n0       | NO            | Disables key traversal randomization\n1       | RANDOM        | Enables full key traversal randomization\n2       | DETERMINISTIC | Enables repeatable key traversal\n|               | randomization\n\nBoth numeric and string values are accepted, but note that string values are case\nsensitive.  The default for this setting is \"RANDOM\" or 1.\n\npid %x not a child\n(W exec) A warning peculiar to VMS.  Waitpid() was asked to wait for a process which\nisn't a subprocess of the current process.  While this is fine from VMS' perspective,\nit's probably not what you intended.\n\n'P' must have an explicit size in unpack\n(F) The unpack format P must have an explicit size, not \"*\".\n\nPOSIX class [:%s:] unknown in regex; marked by <-- HERE in m/%s/\n(F) The class in the character class [: :] syntax is unknown.  The <-- HERE shows\nwhereabouts in the regular expression the problem was discovered.  Note that the POSIX\ncharacter classes do not have the \"is\" prefix the corresponding C interfaces have: in\nother words, it's \"[[:print:]]\", not \"isprint\".  See perlre.\n\nPOSIX getpgrp can't take an argument\n(F) Your system has POSIX getpgrp(), which takes no argument, unlike the BSD version,\nwhich takes a pid.\n\nPOSIX syntax [%c %c] belongs inside character classes%s in regex; marked by <-- HERE in m/%s/\n(W regexp) Perl thinks that you intended to write a POSIX character class, but didn't use\nenough brackets.  These POSIX class constructs [: :], [= =], and [. .]  go inside\ncharacter classes, the [] are part of the construct, for example:\n\"qr/[012[:alpha:]345]/\".  What the regular expression pattern compiled to is probably not\nwhat you were intending.  For example, \"qr/[:alpha:]/\" compiles to a regular bracketed\ncharacter class consisting of the four characters \":\",  \"a\",  \"l\", \"h\", and \"p\".  To\nspecify the POSIX class, it should have been written \"qr/[[:alpha:]]/\".\n\nNote that [= =] and [. .] are not currently implemented; they are simply placeholders for\nfuture extensions and will cause fatal errors.  The <-- HERE shows whereabouts in the\nregular expression the problem was discovered.  See perlre.\n\nIf the specification of the class was not completely valid, the message indicates that.\n\nPOSIX syntax [. .] is reserved for future extensions in regex; marked by <-- HERE in m/%s/\n(F) Within regular expression character classes ([]) the syntax beginning with \"[.\" and\nending with \".]\" is reserved for future extensions.  If you need to represent those\ncharacter sequences inside a regular expression character class, just quote the square\nbrackets with the backslash: \"\\[.\"  and \".\\]\".  The <-- HERE shows whereabouts in the\nregular expression the problem was discovered.  See perlre.\n\nPOSIX syntax [= =] is reserved for future extensions in regex; marked by <-- HERE in m/%s/\n(F) Within regular expression character classes ([]) the syntax beginning with \"[=\" and\nending with \"=]\" is reserved for future extensions.  If you need to represent those\ncharacter sequences inside a regular expression character class, just quote the square\nbrackets with the backslash: \"\\[=\" and \"=\\]\".  The <-- HERE shows whereabouts in the\nregular expression the problem was discovered.  See perlre.\n\nPossible attempt to put comments in qw() list\n(W qw) qw() lists contain items separated by whitespace; as with literal strings, comment\ncharacters are not ignored, but are instead treated as literal data.  (You may have used\ndifferent delimiters than the parentheses shown here; braces are also frequently used.)\n\nYou probably wrote something like this:\n\n@list = qw(\na # a comment\nb # another comment\n);\n\nwhen you should have written this:\n\n@list = qw(\na\nb\n);\n\nIf you really want comments, build your list the old-fashioned way, with quotes and\ncommas:\n\n@list = (\n'a',    # a comment\n'b',    # another comment\n);\n\nPossible attempt to separate words with commas\n(W qw) qw() lists contain items separated by whitespace; therefore commas aren't needed\nto separate the items.  (You may have used different delimiters than the parentheses\nshown here; braces are also frequently used.)\n\nYou probably wrote something like this:\n\nqw! a, b, c !;\n\nwhich puts literal commas into some of the list items.  Write it without commas if you\ndon't want them to appear in your data:\n\nqw! a b c !;\n\nPossible memory corruption: %s overflowed 3rd argument\n(F) An ioctl() or fcntl() returned more than Perl was bargaining for.  Perl guesses a\nreasonable buffer size, but puts a sentinel byte at the end of the buffer just in case.\nThis sentinel byte got clobbered, and Perl assumes that memory is now corrupted.  See\n\"ioctl\" in perlfunc.\n\nPossible precedence issue with control flow operator\n(W syntax) There is a possible problem with the mixing of a control flow operator (e.g.\n\"return\") and a low-precedence operator like \"or\".  Consider:\n\nsub { return $a or $b; }\n\nThis is parsed as:\n\nsub { (return $a) or $b; }\n\nWhich is effectively just:\n\nsub { return $a; }\n\nEither use parentheses or the high-precedence variant of the operator.\n\nNote this may be also triggered for constructs like:\n\nsub { 1 if die; }\n\nPossible precedence problem on bitwise %s operator\n(W precedence) Your program uses a bitwise logical operator in conjunction with a numeric\ncomparison operator, like this :\n\nif ($x & $y == 0) { ... }\n\nThis expression is actually equivalent to \"$x & ($y == 0)\", due to the higher precedence\nof \"==\".  This is probably not what you want.  (If you really meant to write this,\ndisable the warning, or, better, put the parentheses explicitly and write \"$x & ($y ==\n0)\").\n\nPossible unintended interpolation of $\\ in regex\n(W ambiguous) You said something like \"m/$\\/\" in a regex.  The regex \"m/foo$\\s+bar/m\"\ntranslates to: match the word 'foo', the output record separator (see \"$\\\" in perlvar)\nand the letter 's' (one time or more) followed by the word 'bar'.\n\nIf this is what you intended then you can silence the warning by using \"m/${\\}/\" (for\nexample: \"m/foo${\\}s+bar/\").\n\nIf instead you intended to match the word 'foo' at the end of the line followed by\nwhitespace and the word 'bar' on the next line then you can use \"m/$(?)\\/\" (for example:\n\"m/foo$(?)\\s+bar/\").\n\nPossible unintended interpolation of %s in string\n(W ambiguous) You said something like '@foo' in a double-quoted string but there was no\narray @foo in scope at the time.  If you wanted a literal @foo, then write it as \\@foo;\notherwise find out what happened to the array you apparently lost track of.\n\nPrecedence problem: open %s should be open(%s)\n(S precedence) The old irregular construct\n\nopen FOO || die;\n\nis now misinterpreted as\n\nopen(FOO || die);\n\nbecause of the strict regularization of Perl 5's grammar into unary and list operators.\n(The old open was a little of both.)  You must put parentheses around the filehandle, or\nuse the new \"or\" operator instead of \"||\".\n\nPremature end of script headers\nSee \"500 Server error\".\n\nprintf() on closed filehandle %s\n(W closed) The filehandle you're writing to got itself closed sometime before now.  Check\nyour control flow.\n\nprint() on closed filehandle %s\n(W closed) The filehandle you're printing on got itself closed sometime before now.\nCheck your control flow.\n\nProcess terminated by SIG%s\n(W) This is a standard message issued by OS/2 applications, while *nix applications die\nin silence.  It is considered a feature of the OS/2 port.  One can easily disable this by\nappropriate sighandlers, see \"Signals\" in perlipc.  See also \"Process terminated by\nSIGTERM/SIGINT\" in perlos2.\n\nPrototype after '%c' for %s : %s\n(W illegalproto) A character follows % or @ in a prototype.  This is useless, since % and\n@ gobble the rest of the subroutine arguments.\n\nPrototype mismatch: %s vs %s\n(S prototype) The subroutine being declared or defined had previously been declared or\ndefined with a different function prototype.\n\nPrototype not terminated\n(F) You've omitted the closing parenthesis in a function prototype definition.\n\nPrototype '%s' overridden by attribute 'prototype(%s)' in %s\n(W prototype) A prototype was declared in both the parentheses after the sub name and via\nthe prototype attribute.  The prototype in parentheses is useless, since it will be\nreplaced by the prototype from the attribute before it's ever used.\n\nQuantifier follows nothing in regex; marked by <-- HERE in m/%s/\n(F) You started a regular expression with a quantifier.  Backslash it if you meant it\nliterally.  The <-- HERE shows whereabouts in the regular expression the problem was\ndiscovered.  See perlre.\n\nQuantifier in {,} bigger than %d in regex; marked by <-- HERE in m/%s/\n(F) There is currently a limit to the size of the min and max values of the {min,max}\nconstruct.  The <-- HERE shows whereabouts in the regular expression the problem was\ndiscovered.  See perlre.\n\nQuantifier {n,m} with n > m can't match in regex\nQuantifier {n,m} with n > m can't match in regex; marked by <-- HERE in m/%s/\n(W regexp) Minima should be less than or equal to maxima.  If you really want your regexp\nto match something 0 times, just put {0}.\n\nQuantifier unexpected on zero-length expression in regex m/%s/\n(W regexp) You applied a regular expression quantifier in a place where it makes no\nsense, such as on a zero-width assertion.  Try putting the quantifier inside the\nassertion instead.  For example, the way to match \"abc\" provided that it is followed by\nthree repetitions of \"xyz\" is \"/abc(?=(?:xyz){3})/\", not \"/abc(?=xyz){3}/\".\n\nRange iterator outside integer range\n(F) One (or both) of the numeric arguments to the range operator \"..\"  are outside the\nrange which can be represented by integers internally.  One possible workaround is to\nforce Perl to use magical string increment by prepending \"0\" to your numbers.\n\nRanges of ASCII printables should be some subset of \"0-9\", \"A-Z\", or \"a-z\" in regex; marked\nby <-- HERE in m/%s/\n(W regexp) (only under \"use re 'strict'\" or within \"(?[...])\")\n\nStricter rules help to find typos and other errors.  Perhaps you didn't even intend a\nrange here, if the \"-\" was meant to be some other character, or should have been escaped\n(like \"\\-\").  If you did intend a range, the one that was used is not portable between\nASCII and EBCDIC platforms, and doesn't have an obvious meaning to a casual reader.\n\n[3-7]    # OK; Obvious and portable\n[d-g]    # OK; Obvious and portable\n[A-Y]    # OK; Obvious and portable\n[A-z]    # WRONG; Not portable; not clear what is meant\n[a-Z]    # WRONG; Not portable; not clear what is meant\n[%-.]    # WRONG; Not portable; not clear what is meant\n[\\x41-Z] # WRONG; Not portable; not obvious to non-geek\n\n(You can force portability by specifying a Unicode range, which means that the endpoints\nare specified by \"\\N{...}\", but the meaning may still not be obvious.)  The stricter\nrules require that ranges that start or stop with an ASCII character that is not a\ncontrol have all their endpoints be the literal character, and not some escape sequence\n(like \"\\x41\"), and the ranges must be all digits, or all uppercase letters, or all\nlowercase letters.\n\nRanges of digits should be from the same group in regex; marked by <-- HERE in m/%s/\n(W regexp) (only under \"use re 'strict'\" or within \"(?[...])\")\n\nStricter rules help to find typos and other errors.  You included a range, and at least\none of the end points is a decimal digit.  Under the stricter rules, when this happens,\nboth end points should be digits in the same group of 10 consecutive digits.\n\nreaddir() attempted on invalid dirhandle %s\n(W io) The dirhandle you're reading from is either closed or not really a dirhandle.\nCheck your control flow.\n\nreadline() on closed filehandle %s\n(W closed) The filehandle you're reading from got itself closed sometime before now.\nCheck your control flow.\n\nreadline() on unopened filehandle %s\n(W unopened) The filehandle you're reading from was never opened.  Check your control\nflow.\n\nread() on closed filehandle %s\n(W closed) You tried to read from a closed filehandle.\n\nread() on unopened filehandle %s\n(W unopened) You tried to read from a filehandle that was never opened.\n\nReallocation too large: %x\n(F) You can't allocate more than 64K on an MS-DOS machine.\n\nrealloc() of freed memory ignored\n(S malloc) An internal routine called realloc() on something that had already been freed.\n\nRecompile perl with -DDEBUGGING to use -D switch\n(S debugging) You can't use the -D option unless the code to produce the desired output\nis compiled into Perl, which entails some overhead, which is why it's currently left out\nof your copy.\n\nRecursive call to Perlloadmodule in PerlIOfindlayer\n(P) It is currently not permitted to load modules when creating a filehandle inside an\n%INC hook.  This can happen with \"open my $fh, '<', \\$scalar\", which implicitly loads\nPerlIO::scalar.  Try loading PerlIO::scalar explicitly first.\n\nRecursive inheritance detected in package '%s'\n(F) While calculating the method resolution order (MRO) of a package, Perl believes it\nfound an infinite loop in the @ISA hierarchy.  This is a crude check that bails out after\n100 levels of @ISA depth.\n\nRedundant argument in %s\n(W redundant) You called a function with more arguments than other arguments you supplied\nindicated would be needed.  Currently only emitted when a printf-type format required\nfewer arguments than were supplied, but might be used in the future for e.g. \"pack\" in\nperlfunc.\n\nrefcntdec: fd %d%s\nrefcnt: fd %d%s\nrefcntinc: fd %d%s\n(P) Perl's I/O implementation failed an internal consistency check.  If you see this\nmessage, something is very wrong.\n\nReference found where even-sized list expected\n(W misc) You gave a single reference where Perl was expecting a list with an even number\nof elements (for assignment to a hash).  This usually means that you used the anon hash\nconstructor when you meant to use parens.  In any case, a hash requires key/value pairs.\n\n%hash = { one => 1, two => 2, };    # WRONG\n%hash = [ qw/ an anon array / ];    # WRONG\n%hash = ( one => 1, two => 2, );    # right\n%hash = qw( one 1 two 2 );                  # also fine\n\nReference is already weak\n(W misc) You have attempted to weaken a reference that is already weak.  Doing so has no\neffect.\n\nReference is not weak\n(W misc) You have attempted to unweaken a reference that is not weak.  Doing so has no\neffect.\n\nReference to invalid group 0 in regex; marked by <-- HERE in m/%s/\n(F) You used \"\\g0\" or similar in a regular expression.  You may refer to capturing\nparentheses only with strictly positive integers (normal backreferences) or with strictly\nnegative integers (relative backreferences).  Using 0 does not make sense.\n\nReference to nonexistent group in regex; marked by <-- HERE in m/%s/\n(F) You used something like \"\\7\" in your regular expression, but there are not at least\nseven sets of capturing parentheses in the expression.  If you wanted to have the\ncharacter with ordinal 7 inserted into the regular expression, prepend zeroes to make it\nthree digits long: \"\\007\"\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.\n\nReference to nonexistent named group in regex; marked by <-- HERE in m/%s/\n(F) You used something like \"\\k'NAME'\" or \"\\k<NAME>\" in your regular expression, but\nthere is no corresponding named capturing parentheses such as \"(?'NAME'...)\" or\n\"(?<NAME>...)\".  Check if the name has been spelled correctly both in the backreference\nand the declaration.\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.\n\nReference to nonexistent or unclosed group in regex; marked by <-- HERE in m/%s/\n(F) You used something like \"\\g{-7}\" in your regular expression, but there are not at\nleast seven sets of closed capturing parentheses in the expression before where the\n\"\\g{-7}\" was located.\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.\n\nregexp memory corruption\n(P) The regular expression engine got confused by what the regular expression compiler\ngave it.\n\nRegexp modifier \"/%c\" may appear a maximum of twice\nRegexp modifier \"%c\" may appear a maximum of twice in regex; marked by <-- HERE in m/%s/\n(F) The regular expression pattern had too many occurrences of the specified modifier.\nRemove the extraneous ones.\n\nRegexp modifier \"%c\" may not appear after the \"-\" in regex; marked by <-- HERE in m/%s/\n(F) Turning off the given modifier has the side effect of turning on another one.  Perl\ncurrently doesn't allow this.  Reword the regular expression to use the modifier you want\nto turn on (and place it before the minus), instead of the one you want to turn off.\n\nRegexp modifier \"/%c\" may not appear twice\nRegexp modifier \"%c\" may not appear twice in regex; marked by <-- HERE in m/%s/\n(F) The regular expression pattern had too many occurrences of the specified modifier.\nRemove the extraneous ones.\n\nRegexp modifiers \"/%c\" and \"/%c\" are mutually exclusive\nRegexp modifiers \"%c\" and \"%c\" are mutually exclusive in regex; marked by <-- HERE in m/%s/\n(F) The regular expression pattern had more than one of these mutually exclusive\nmodifiers.  Retain only the modifier that is supposed to be there.\n\nRegexp out of space in regex m/%s/\n(P) A \"can't happen\" error, because safemalloc() should have caught it earlier.\n\nRepeated format line will never terminate (~~ and @#)\n(F) Your format contains the ~~ repeat-until-blank sequence and a numeric field that will\nnever go blank so that the repetition never terminates.  You might use ^# instead.  See\nperlform.\n\nReplacement list is longer than search list\n(W misc) You have used a replacement list that is longer than the search list.  So the\nadditional elements in the replacement list are meaningless.\n\n'(*%s' requires a terminating ':' in regex; marked by <-- HERE in m/%s/\n(F) You used a construct that needs a colon and pattern argument.  Supply these or check\nthat you are using the right construct.\n\n'%s' resolved to '\\o{%s}%d'\nAs of Perl 5.32, this message is no longer generated.  Instead, see \"Non-octal character\n'%c' terminates \\o early.  Resolved as \"%s\"\".  (W misc, regexp)  You wrote something like\n\"\\08\", or \"\\179\" in a double-quotish string.  All but the last digit is treated as a\nsingle character, specified in octal.  The last digit is the next character in the\nstring.  To tell Perl that this is indeed what you want, you can use the \"\\o{ }\" syntax,\nor use exactly three digits to specify the octal for the character.\n\nReversed %s= operator\n(W syntax) You wrote your assignment operator backwards.  The = must always come last, to\navoid ambiguity with subsequent unary operators.\n\nrewinddir() attempted on invalid dirhandle %s\n(W io) The dirhandle you tried to do a rewinddir() on is either closed or not really a\ndirhandle.  Check your control flow.\n\nScalars leaked: %d\n(S internal) Something went wrong in Perl's internal bookkeeping of scalars: not all\nscalar variables were deallocated by the time Perl exited.  What this usually indicates\nis a memory leak, which is of course bad, especially if the Perl program is intended to\nbe long-running.\n\nScalar value @%s[%s] better written as $%s[%s]\n(W syntax) You've used an array slice (indicated by @) to select a single element of an\narray.  Generally it's better to ask for a scalar value (indicated by $).  The difference\nis that $foo[&bar] always behaves like a scalar, both when assigning to it and when\nevaluating its argument, while @foo[&bar] behaves like a list when you assign to it, and\nprovides a list context to its subscript, which can do weird things if you're expecting\nonly one subscript.\n\nOn the other hand, if you were actually hoping to treat the array element as a list, you\nneed to look into how references work, because Perl will not magically convert between\nscalars and lists for you.  See perlref.\n\nScalar value @%s{%s} better written as $%s{%s}\n(W syntax) You've used a hash slice (indicated by @) to select a single element of a\nhash.  Generally it's better to ask for a scalar value (indicated by $).  The difference\nis that $foo{&bar} always behaves like a scalar, both when assigning to it and when\nevaluating its argument, while @foo{&bar} behaves like a list when you assign to it, and\nprovides a list context to its subscript, which can do weird things if you're expecting\nonly one subscript.\n\nOn the other hand, if you were actually hoping to treat the hash element as a list, you\nneed to look into how references work, because Perl will not magically convert between\nscalars and lists for you.  See perlref.\n\nSearch pattern not terminated\n(F) The lexer couldn't find the final delimiter of a // or m{} construct.  Remember that\nbracketing delimiters count nesting level.  Missing the leading \"$\" from a variable $m\nmay cause this error.\n\nNote that since Perl 5.10.0 a // can also be the defined-or construct, not just the empty\nsearch pattern.  Therefore code written in Perl 5.10.0 or later that uses the // as the\ndefined-or can be misparsed by pre-5.10.0 Perls as a non-terminated search pattern.\n\nseekdir() attempted on invalid dirhandle %s\n(W io) The dirhandle you are doing a seekdir() on is either closed or not really a\ndirhandle.  Check your control flow.\n\n%sseek() on unopened filehandle\n(W unopened) You tried to use the seek() or sysseek() function on a filehandle that was\neither never opened or has since been closed.\n\nselect not implemented\n(F) This machine doesn't implement the select() system call.\n\nSelf-ties of arrays and hashes are not supported\n(F) Self-ties are of arrays and hashes are not supported in the current implementation.\n\nSemicolon seems to be missing\n(W semicolon) A nearby syntax error was probably caused by a missing semicolon, or\npossibly some other missing operator, such as a comma.\n\nsemi-panic: attempt to dup freed string\n(S internal) The internal newSVsv() routine was called to duplicate a scalar that had\npreviously been marked as free.\n\nsem%s not implemented\n(F) You don't have System V semaphore IPC on your system.\n\nsend() on closed socket %s\n(W closed) The socket you're sending to got itself closed sometime before now.  Check\nyour control flow.\n\nSequence \"\\c{\" invalid\n(F) These three characters may not appear in sequence in a double-quotish context.  This\nmessage is raised only on non-ASCII platforms (a different error message is output on\nASCII ones).  If you were intending to specify a control character with this sequence,\nyou'll have to use a different way to specify it.\n\nSequence (? incomplete in regex; marked by <-- HERE in m/%s/\n(F) A regular expression ended with an incomplete extension (?.  The <-- HERE shows\nwhereabouts in the regular expression the problem was discovered.  See perlre.\n\nSequence (?%c...) not implemented in regex; marked by <-- HERE in m/%s/\n(F) A proposed regular expression extension has the character reserved but has not yet\nbeen written.  The <-- HERE shows whereabouts in the regular expression the problem was\ndiscovered.  See perlre.\n\nSequence (?%s...) not recognized in regex; marked by <-- HERE in m/%s/\n(F) You used a regular expression extension that doesn't make sense.  The <-- HERE shows\nwhereabouts in the regular expression the problem was discovered.  This may happen when\nusing the \"(?^...)\" construct to tell Perl to use the default regular expression\nmodifiers, and you redundantly specify a default modifier.  For other causes, see perlre.\n\nSequence (?#... not terminated in regex m/%s/\n(F) A regular expression comment must be terminated by a closing parenthesis.  Embedded\nparentheses aren't allowed.  See perlre.\n\nSequence (?&... not terminated in regex; marked by <-- HERE in m/%s/\n(F) A named reference of the form \"(?&...)\" was missing the final closing parenthesis\nafter the name.  The <-- HERE shows whereabouts in the regular expression the problem was\ndiscovered.\n\nSequence (?%c... not terminated in regex; marked by <-- HERE in m/%s/\n(F) A named group of the form \"(?'...')\" or \"(?<...>)\" was missing the final closing\nquote or angle bracket.  The <-- HERE shows whereabouts in the regular expression the\nproblem was discovered.\n\nSequence (?(%c... not terminated in regex; marked by <-- HERE in m/%s/\n(F) A named reference of the form \"(?('...')...)\" or \"(?(<...>)...)\" was missing the\nfinal closing quote or angle bracket after the name.  The <-- HERE shows whereabouts in\nthe regular expression the problem was discovered.\n\nSequence (?... not terminated in regex; marked by <-- HERE in m/%s/\n(F) There was no matching closing parenthesis for the '('.  The <-- HERE shows\nwhereabouts in the regular expression the problem was discovered.\n\nSequence \\%s... not terminated in regex; marked by <-- HERE in m/%s/\n(F) The regular expression expects a mandatory argument following the escape sequence and\nthis has been omitted or incorrectly written.\n\nSequence (?{...}) not terminated with ')'\n(F) The end of the perl code contained within the {...} must be followed immediately by a\n')'.\n\nSequence (?P>... not terminated in regex; marked by <-- HERE in m/%s/\n(F) A named reference of the form \"(?P>...)\" was missing the final closing parenthesis\nafter the name.  The <-- HERE shows whereabouts in the regular expression the problem was\ndiscovered.\n\nSequence (?P<... not terminated in regex; marked by <-- HERE in m/%s/\n(F) A named group of the form \"(?P<...>')\" was missing the final closing angle bracket.\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.\n\nSequence ?P=... not terminated in regex; marked by <-- HERE in m/%s/\n(F) A named reference of the form \"(?P=...)\" was missing the final closing parenthesis\nafter the name.  The <-- HERE shows whereabouts in the regular expression the problem was\ndiscovered.\n\nSequence (?R) not terminated in regex m/%s/\n(F) An \"(?R)\" or \"(?0)\" sequence in a regular expression was missing the final\nparenthesis.\n\n500 Server error\n(A) This is the error message generally seen in a browser window when trying to run a CGI\nprogram (including SSI) over the web.  The actual error text varies widely from server to\nserver.  The most frequently-seen variants are \"500 Server error\", \"Method (something)\nnot permitted\", \"Document contains no data\", \"Premature end of script headers\", and \"Did\nnot produce a valid header\".\n\nThis is a CGI error, not a Perl error.\n\nYou need to make sure your script is executable, is accessible by the user CGI is running\nthe script under (which is probably not the user account you tested it under), does not\nrely on any environment variables (like PATH) from the user it isn't running under, and\nisn't in a location where the CGI server can't find it, basically, more or less.  Please\nsee the following for more information:\n\nhttps://www.perl.org/CGIMetaFAQ.html\nhttp://www.htmlhelp.org/faq/cgifaq.html\nhttp://www.w3.org/Security/Faq/\n\nYou should also look at perlfaq9.\n\nsetegid() not implemented\n(F) You tried to assign to $), and your operating system doesn't support the setegid()\nsystem call (or equivalent), or at least Configure didn't think so.\n\nseteuid() not implemented\n(F) You tried to assign to $>, and your operating system doesn't support the seteuid()\nsystem call (or equivalent), or at least Configure didn't think so.\n\nsetpgrp can't take arguments\n(F) Your system has the setpgrp() from BSD 4.2, which takes no arguments, unlike POSIX\nsetpgid(), which takes a process ID and process group ID.\n\nsetrgid() not implemented\n(F) You tried to assign to $(, and your operating system doesn't support the setrgid()\nsystem call (or equivalent), or at least Configure didn't think so.\n\nsetruid() not implemented\n(F) You tried to assign to $<, and your operating system doesn't support the setruid()\nsystem call (or equivalent), or at least Configure didn't think so.\n\nsetsockopt() on closed socket %s\n(W closed) You tried to set a socket option on a closed socket.  Did you forget to check\nthe return value of your socket() call?  See \"setsockopt\" in perlfunc.\n\nSetting $/ to a reference to %s is forbidden\n(F) You assigned a reference to a scalar to $/ where the referenced item is not a\npositive integer.  In older perls this appeared to work the same as setting it to \"undef\"\nbut was in fact internally different, less efficient and with very bad luck could have\nresulted in your file being split by a stringified form of the reference.\n\nIn Perl 5.20.0 this was changed so that it would be exactly the same as setting $/ to\nundef, with the exception that this warning would be thrown.\n\nYou are recommended to change your code to set $/ to \"undef\" explicitly if you wish to\nslurp the file.  As of Perl 5.28 assigning $/ to a reference to an integer which isn't\npositive is a fatal error.\n\nSetting $/ to %s reference is forbidden\n(F) You tried to assign a reference to a non integer to $/.  In older Perls this would\nhave behaved similarly to setting it to a reference to a positive integer, where the\ninteger was the address of the reference.  As of Perl 5.20.0 this is a fatal error, to\nallow future versions of Perl to use non-integer refs for more interesting purposes.\n\nshm%s not implemented\n(F) You don't have System V shared memory IPC on your system.\n\n!=~ should be !~\n(W syntax) The non-matching operator is !~, not !=~.  !=~ will be interpreted as the !=\n(numeric not equal) and ~ (1's complement) operators: probably not what you intended.\n\n/%s/ should probably be written as \"%s\"\n(W syntax) You have used a pattern where Perl expected to find a string, as in the first\nargument to \"join\".  Perl will treat the true or false result of matching the pattern\nagainst $ as the string, which is probably not what you had in mind.\n\nshutdown() on closed socket %s\n(W closed) You tried to do a shutdown on a closed socket.  Seems a bit superfluous.\n\nSIG%s handler \"%s\" not defined\n(W signal) The signal handler named in %SIG doesn't, in fact, exist.  Perhaps you put it\ninto the wrong package?\n\nSlab leaked from cv %p\n(S) If you see this message, then something is seriously wrong with the internal\nbookkeeping of op trees.  An op tree needed to be freed after a compilation error, but\ncould not be found, so it was leaked instead.\n\nsleep(%u) too large\n(W overflow) You called \"sleep\" with a number that was larger than it can reliably handle\nand \"sleep\" probably slept for less time than requested.\n\nSlurpy parameter not last\n(F) In a subroutine signature, you put something after a slurpy (array or hash)\nparameter.  The slurpy parameter takes all the available arguments, so there can't be any\nleft to fill later parameters.\n\nSmart matching a non-overloaded object breaks encapsulation\n(F) You should not use the \"~~\" operator on an object that does not overload it: Perl\nrefuses to use the object's underlying structure for the smart match.\n\nSmartmatch is experimental\n(S experimental::smartmatch) This warning is emitted if you use the smartmatch (\"~~\")\noperator.  This is currently an experimental feature, and its details are subject to\nchange in future releases of Perl.  Particularly, its current behavior is noticed for\nbeing unnecessarily complex and unintuitive, and is very likely to be overhauled.\n\nSorry, hash keys must be smaller than 231 bytes\n(F) You tried to create a hash containing a very large key, where \"very large\" means that\nit needs at least 2 gigabytes to store. Unfortunately, Perl doesn't yet handle such large\nhash keys. You should reconsider your design to avoid hashing such a long string\ndirectly.\n\nsort is now a reserved word\n(F) An ancient error message that almost nobody ever runs into anymore.  But before sort\nwas a keyword, people sometimes used it as a filehandle.\n\nSource filters apply only to byte streams\n(F) You tried to activate a source filter (usually by loading a source filter module)\nwithin a string passed to \"eval\".  This is not permitted under the \"unicodeeval\"\nfeature.  Consider using \"evalbytes\" instead.  See feature.\n\nsplice() offset past end of array\n(W misc) You attempted to specify an offset that was past the end of the array passed to\nsplice().  Splicing will instead commence at the end of the array, rather than past it.\nIf this isn't what you want, try explicitly pre-extending the array by assigning $#array\n= $offset.  See \"splice\" in perlfunc.\n\nSplit loop\n(P) The split was looping infinitely.  (Obviously, a split shouldn't iterate more times\nthan there are characters of input, which is what happened.)  See \"split\" in perlfunc.\n\nStatement unlikely to be reached\n(W exec) You did an exec() with some statement after it other than a die().  This is\nalmost always an error, because exec() never returns unless there was a failure.  You\nprobably wanted to use system() instead, which does return.  To suppress this warning,\nput the exec() in a block by itself.\n\n\"state\" subroutine %s can't be in a package\n(F) Lexically scoped subroutines aren't in a package, so it doesn't make sense to try to\ndeclare one with a package qualifier on the front.\n\n\"state %s\" used in sort comparison\n(W syntax) The package variables $a and $b are used for sort comparisons.  You used $a or\n$b in as an operand to the \"<=>\" or \"cmp\" operator inside a sort comparison block, and\nthe variable had earlier been declared as a lexical variable.  Either qualify the sort\nvariable with the package name, or rename the lexical variable.\n\n\"state\" variable %s can't be in a package\n(F) Lexically scoped variables aren't in a package, so it doesn't make sense to try to\ndeclare one with a package qualifier on the front.  Use local() if you want to localize a\npackage variable.\n\nstat() on unopened filehandle %s\n(W unopened) You tried to use the stat() function on a filehandle that was either never\nopened or has since been closed.\n\nStrings with code points over 0xFF may not be mapped into in-memory file handles\n(W utf8) You tried to open a reference to a scalar for read or append where the scalar\ncontained code points over 0xFF.  In-memory files model on-disk files and can only\ncontain bytes.\n\nStub found while resolving method \"%s\" overloading \"%s\" in package \"%s\"\n(P) Overloading resolution over @ISA tree may be broken by importation stubs.  Stubs\nshould never be implicitly created, but explicit calls to \"can\" may break this.\n\nSubroutine attributes must come before the signature\n(F) When subroutine signatures are enabled, any subroutine attributes must come before\nthe signature. Note that this order was the opposite in versions 5.22..5.26. So:\n\nsub foo :lvalue ($a, $b) { ... }  # 5.20 and 5.28 +\nsub foo ($a, $b) :lvalue { ... }  # 5.22 .. 5.26\n\nSubroutine \"&%s\" is not available\n(W closure) During compilation, an inner named subroutine or eval is attempting to\ncapture an outer lexical subroutine that is not currently available.  This can happen for\none of two reasons.  First, the lexical subroutine may be declared in an outer anonymous\nsubroutine that has not yet been created.  (Remember that named subs are created at\ncompile time, while anonymous subs are created at run-time.)  For example,\n\nsub { my sub a {...} sub f { \\&a } }\n\nAt the time that f is created, it can't capture the current \"a\" sub, since the anonymous\nsubroutine hasn't been created yet.  Conversely, the following won't give a warning since\nthe anonymous subroutine has by now been created and is live:\n\nsub { my sub a {...} eval 'sub f { \\&a }' }->();\n\nThe second situation is caused by an eval accessing a lexical subroutine that has gone\nout of scope, for example,\n\nsub f {\nmy sub a {...}\nsub { eval '\\&a' }\n}\nf()->();\n\nHere, when the '\\&a' in the eval is being compiled, f() is not currently being executed,\nso its &a is not available for capture.\n\n\"%s\" subroutine &%s masks earlier declaration in same %s\n(W shadow) A \"my\" or \"state\" subroutine has been redeclared in the current scope or\nstatement, effectively eliminating all access to the previous instance.  This is almost\nalways a typographical error.  Note that the earlier subroutine will still exist until\nthe end of the scope or until all closure references to it are destroyed.\n\nSubroutine %s redefined\n(W redefine) You redefined a subroutine.  To suppress this warning, say\n\n{\nno warnings 'redefine';\neval \"sub name { ... }\";\n}\n\nSubroutine \"%s\" will not stay shared\n(W closure) An inner (nested) named subroutine is referencing a \"my\" subroutine defined\nin an outer named subroutine.\n\nWhen the inner subroutine is called, it will see the value of the outer subroutine's\nlexical subroutine as it was before and during the *first* call to the outer subroutine;\nin this case, after the first call to the outer subroutine is complete, the inner and\nouter subroutines will no longer share a common value for the lexical subroutine.  In\nother words, it will no longer be shared.  This will especially make a difference if the\nlexical subroutines accesses lexical variables declared in its surrounding scope.\n\nThis problem can usually be solved by making the inner subroutine anonymous, using the\n\"sub {}\" syntax.  When inner anonymous subs that reference lexical subroutines in outer\nsubroutines are created, they are automatically rebound to the current values of such\nlexical subs.\n\nSubstitution loop\n(P) The substitution was looping infinitely.  (Obviously, a substitution shouldn't\niterate more times than there are characters of input, which is what happened.)  See the\ndiscussion of substitution in \"Regexp Quote-Like Operators\" in perlop.\n\nSubstitution pattern not terminated\n(F) The lexer couldn't find the interior delimiter of an s/// or s{}{} construct.\nRemember that bracketing delimiters count nesting level.  Missing the leading \"$\" from\nvariable $s may cause this error.\n\nSubstitution replacement not terminated\n(F) The lexer couldn't find the final delimiter of an s/// or s{}{} construct.  Remember\nthat bracketing delimiters count nesting level.  Missing the leading \"$\" from variable $s\nmay cause this error.\n\nsubstr outside of string\n(W substr)(F) You tried to reference a substr() that pointed outside of a string.  That\nis, the absolute value of the offset was larger than the length of the string.  See\n\"substr\" in perlfunc.  This warning is fatal if substr is used in an lvalue context (as\nthe left hand side of an assignment or as a subroutine argument for example).\n\nsvupgrade from type %d down to type %d\n(P) Perl tried to force the upgrade of an SV to a type which was actually inferior to its\ncurrent type.\n\nSwitch (?(condition)... contains too many branches in regex; marked by <-- HERE in m/%s/\n(F) A (?(condition)if-clause|else-clause) construct can have at most two branches (the\nif-clause and the else-clause).  If you want one or both to contain alternation, such as\nusing \"this|that|other\", enclose it in clustering parentheses:\n\n(?(condition)(?:this|that|other)|else-clause)\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.  See\nperlre.\n\nSwitch condition not recognized in regex; marked by <-- HERE in m/%s/\n(F) The condition part of a (?(condition)if-clause|else-clause) construct is not known.\nThe condition must be one of the following:\n\n(1) (2) ...        true if 1st, 2nd, etc., capture matched\n(<NAME>) ('NAME')  true if named capture matched\n(?=...) (?<=...)   true if subpattern matches\n(?!...) (?<!...)   true if subpattern fails to match\n(?{ CODE })        true if code returns a true value\n(R)                true if evaluating inside recursion\n(R1) (R2) ...      true if directly inside capture group 1, 2, etc.\n(R&NAME)           true if directly inside named capture\n(DEFINE)           always false; for defining named subpatterns\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.  See\nperlre.\n\nSwitch (?(condition)... not terminated in regex; marked by <-- HERE in m/%s/\n(F) You omitted to close a (?(condition)...) block somewhere in the pattern.  Add a\nclosing parenthesis in the appropriate position.  See perlre.\n\nswitching effective %s is not implemented\n(F) While under the \"use filetest\" pragma, we cannot switch the real and effective uids\nor gids.\n\nsyntax error\n(F) Probably means you had a syntax error.  Common reasons include:\n\nA keyword is misspelled.\nA semicolon is missing.\nA comma is missing.\nAn opening or closing parenthesis is missing.\nAn opening or closing brace is missing.\nA closing quote is missing.\n\nOften there will be another error message associated with the syntax error giving more\ninformation.  (Sometimes it helps to turn on -w.)  The error message itself often tells\nyou where it was in the line when it decided to give up.  Sometimes the actual error is\nseveral tokens before this, because Perl is good at understanding random input.\nOccasionally the line number may be misleading, and once in a blue moon the only way to\nfigure out what's triggering the error is to call \"perl -c\" repeatedly, chopping away\nhalf the program each time to see if the error went away.  Sort of the cybernetic version\nof 20 questions.\n\nsyntax error at line %d: '%s' unexpected\n(A) You've accidentally run your script through the Bourne shell instead of Perl.  Check\nthe #! line, or manually feed your script into Perl yourself.\n\nsyntax error in file %s at line %d, next 2 tokens \"%s\"\n(F) This error is likely to occur if you run a perl5 script through a perl4 interpreter,\nespecially if the next 2 tokens are \"use strict\" or \"my $var\" or \"our $var\".\n\nSyntax error in (?[...]) in regex; marked by <-- HERE in m/%s/\n(F) Perl could not figure out what you meant inside this construct; this notifies you\nthat it is giving up trying.\n\n%s syntax OK\n(F) The final summary message when a \"perl -c\" succeeds.\n\nsysread() on closed filehandle %s\n(W closed) You tried to read from a closed filehandle.\n\nsysread() on unopened filehandle %s\n(W unopened) You tried to read from a filehandle that was never opened.\n\nSystem V %s is not implemented on this machine\n(F) You tried to do something with a function beginning with \"sem\", \"shm\", or \"msg\" but\nthat System V IPC is not implemented in your machine.  In some machines the functionality\ncan exist but be unconfigured.  Consult your system support.\n\nsyswrite() on closed filehandle %s\n(W closed) The filehandle you're writing to got itself closed sometime before now.  Check\nyour control flow.\n\n\"-T\" and \"-B\" not implemented on filehandles\n(F) Perl can't peek at the stdio buffer of filehandles when it doesn't know about your\nkind of stdio.  You'll have to use a filename instead.\n\nTarget of goto is too deeply nested\n(F) You tried to use \"goto\" to reach a label that was too deeply nested for Perl to\nreach.  Perl is doing you a favor by refusing.\n\ntelldir() attempted on invalid dirhandle %s\n(W io) The dirhandle you tried to telldir() is either closed or not really a dirhandle.\nCheck your control flow.\n\ntell() on unopened filehandle\n(W unopened) You tried to use the tell() function on a filehandle that was either never\nopened or has since been closed.\n\nThe crypt() function is unimplemented due to excessive paranoia.\n(F) Configure couldn't find the crypt() function on your machine, probably because your\nvendor didn't supply it, probably because they think the U.S. Government thinks it's a\nsecret, or at least that they will continue to pretend that it is.  And if you quote me\non that, I will deny it.\n\nThe experimental declaredrefs feature is not enabled\n(F) To declare references to variables, as in \"my \\%x\", you must first enable the\nfeature:\n\nno warnings \"experimental::declaredrefs\";\nuse feature \"declaredrefs\";\n\nThe %s function is unimplemented\n(F) The function indicated isn't implemented on this architecture, according to the\nprobings of Configure.\n\nThe privateuse feature is experimental\n(S experimental::privateuse) This feature is actually a hook for future use.\n\nThe regexsets feature is experimental\n(S experimental::regexsets) This warning is emitted if you use the syntax \"(?[   ])\" in\na regular expression.  The details of this feature are subject to change.  If you want to\nuse it, but know that in doing so you are taking the risk of using an experimental\nfeature which may change in a future Perl version, you can do this to silence the\nwarning:\n\nno warnings \"experimental::regexsets\";\n\nThe signatures feature is experimental\n(S experimental::signatures) This warning is emitted if you unwrap a subroutine's\narguments using a signature.  Simply suppress the warning if you want to use the feature,\nbut know that in doing so you are taking the risk of using an experimental feature which\nmay change or be removed in a future Perl version:\n\nno warnings \"experimental::signatures\";\nuse feature \"signatures\";\nsub foo ($left, $right) { ... }\n\nThe stat preceding %s wasn't an lstat\n(F) It makes no sense to test the current stat buffer for symbolic linkhood if the last\nstat that wrote to the stat buffer already went past the symlink to get to the real file.\nUse an actual filename instead.\n\nThe Unicode property wildcards feature is experimental\n(S experimental::unipropwildcards) This feature is experimental and its behavior may in\nany future release of perl.  See \"Wildcards in Property Values\" in perlunicode.\n\nThe 'unique' attribute may only be applied to 'our' variables\n(F) This attribute was never supported on \"my\" or \"sub\" declarations.\n\nThis Perl can't reset CRTL environ elements (%s)\nThis Perl can't set CRTL environ elements (%s=%s)\n(W internal) Warnings peculiar to VMS.  You tried to change or delete an element of the\nCRTL's internal environ array, but your copy of Perl wasn't built with a CRTL that\ncontained the setenv() function.  You'll need to rebuild Perl with a CRTL that does, or\nredefine PERLENVTABLES (see perlvms) so that the environ array isn't the target of the\nchange to %ENV which produced the warning.\n\nThis Perl has not been built with support for randomized hash key traversal but something\ncalled Perlhvrandset().\n(F) Something has attempted to use an internal API call which depends on Perl being\ncompiled with the default support for randomized hash key traversal, but this Perl has\nbeen compiled without it.  You should report this warning to the relevant upstream party,\nor recompile perl with default options.\n\nThis use of my() in false conditional is no longer allowed\n(F) You used a declaration similar to \"my $x if 0\".  There has been a long-standing bug\nin Perl that causes a lexical variable not to be cleared at scope exit when its\ndeclaration includes a false conditional.  Some people have exploited this bug to achieve\na kind of static variable.  Since we intend to fix this bug, we don't want people relying\non this behavior.  You can achieve a similar static effect by declaring the variable in a\nseparate block outside the function, eg\n\nsub f { my $x if 0; return $x++ }\n\nbecomes\n\n{ my $x; sub f { return $x++ } }\n\nBeginning with perl 5.10.0, you can also use \"state\" variables to have lexicals that are\ninitialized only once (see feature):\n\nsub f { state $x; return $x++ }\n\nThis use of \"my()\" in a false conditional was deprecated beginning in Perl 5.10 and\nbecame a fatal error in Perl 5.30.\n\nTimeout waiting for another thread to define \\p{%s}\n(F) The first time a user-defined property (\"User-Defined Character Properties\" in\nperlunicode) is used, its definition is looked up and converted into an internal form for\nmore efficient handling in subsequent uses.  There could be a race if two or more threads\ntried to do this processing nearly simultaneously.  Instead, a critical section is\ncreated around this task, locking out all but one thread from doing it.  This message\nindicates that the thread that is doing the conversion is taking an unexpectedly long\ntime.  The timeout exists solely to prevent deadlock; it's long enough that the system\nwas likely thrashing and about to crash.  There is no real remedy but rebooting.\n\ntimes not implemented\n(F) Your version of the C library apparently doesn't do times().  I suspect you're not\nrunning on Unix.\n\n\"-T\" is on the #! line, it must also be used on the command line\n(X) The #! line (or local equivalent) in a Perl script contains the -T option (or the -t\noption), but Perl was not invoked with -T in its command line.  This is an error because,\nby the time Perl discovers a -T in a script, it's too late to properly taint everything\nfrom the environment.  So Perl gives up.\n\nIf the Perl script is being executed as a command using the #!  mechanism (or its local\nequivalent), this error can usually be fixed by editing the #! line so that the -%c\noption is a part of Perl's first argument: e.g. change \"perl -n -%c\" to \"perl -%c -n\".\n\nIf the Perl script is being executed as \"perl scriptname\", then the -%c option must\nappear on the command line: \"perl -%c scriptname\".\n\nTo%s: illegal mapping '%s'\n(F) You tried to define a customized To-mapping for lc(), lcfirst, uc(), or ucfirst() (or\ntheir string-inlined versions), but you specified an illegal mapping.  See \"User-Defined\nCharacter Properties\" in perlunicode.\n\nToo deeply nested ()-groups\n(F) Your template contains ()-groups with a ridiculously deep nesting level.\n\nToo few args to syscall\n(F) There has to be at least one argument to syscall() to specify the system call to\ncall, silly dilly.\n\nToo few arguments for subroutine '%s' (got %d; expected %d)\n(F) A subroutine using a signature fewer arguments than required by the signature.  The\ncaller of the subroutine is presumably at fault.\n\nThe message attempts to include the name of the called subroutine.  If the subroutine has\nbeen aliased, the subroutine's original name will be shown, regardless of what name the\ncaller used. It will also indicate the number of arguments given and the number expected.\n\nToo few arguments for subroutine '%s' (got %d; expected at least %d)\nSimilar to the previous message but for subroutines that accept a variable number of\narguments.\n\nToo late for \"-%s\" option\n(X) The #! line (or local equivalent) in a Perl script contains the -M, -m or -C option.\n\nIn the case of -M and -m, this is an error because those options are not intended for use\ninside scripts.  Use the \"use\" pragma instead.\n\nThe -C option only works if it is specified on the command line as well (with the same\nsequence of letters or numbers following).  Either specify this option on the command\nline, or, if your system supports it, make your script executable and run it directly\ninstead of passing it to perl.\n\nToo late to run %s block\n(W void) A CHECK or INIT block is being defined during run time proper, when the\nopportunity to run them has already passed.  Perhaps you are loading a file with\n\"require\" or \"do\" when you should be using \"use\" instead.  Or perhaps you should put the\n\"require\" or \"do\" inside a BEGIN block.\n\nToo many args to syscall\n(F) Perl supports a maximum of only 14 args to syscall().\n\nToo many arguments for %s\n(F) The function requires fewer arguments than you specified.\n\nToo many arguments for subroutine '%s' (got %d; expected %d)\n(F) A subroutine using a signature received more arguments than permitted by the\nsignature.  The caller of the subroutine is presumably at fault.\n\nThe message attempts to include the name of the called subroutine. If the subroutine has\nbeen aliased, the subroutine's original name will be shown, regardless of what name the\ncaller used. It will also indicate the number of arguments given and the number expected.\n\nToo many arguments for subroutine '%s' (got %d; expected at most %d)\nSimilar to the previous message but for subroutines that accept a variable number of\narguments.\n\nToo many nested open parens in regex; marked by <-- HERE in m/%s/\n(F) You have exceeded the number of open \"(\" parentheses that haven't been matched by\ncorresponding closing ones.  This limit prevents eating up too much memory.  It is\ninitially set to 1000, but may be changed by setting \"${^RECOMPILERECURSIONLIMIT}\" to\nsome other value.  This may need to be done in a BEGIN block before the regular\nexpression pattern is compiled.\n\nToo many )'s\n(A) You've accidentally run your script through csh instead of Perl.  Check the #! line,\nor manually feed your script into Perl yourself.\n\nToo many ('s\n(A) You've accidentally run your script through csh instead of Perl.  Check the #! line,\nor manually feed your script into Perl yourself.\n\nTrailing \\ in regex m/%s/\n(F) The regular expression ends with an unbackslashed backslash.  Backslash it.   See\nperlre.\n\nTransliteration pattern not terminated\n(F) The lexer couldn't find the interior delimiter of a tr/// or tr[][] or y/// or y[][]\nconstruct.  Missing the leading \"$\" from variables $tr or $y may cause this error.\n\nTransliteration replacement not terminated\n(F) The lexer couldn't find the final delimiter of a tr///, tr[][], y/// or y[][]\nconstruct.\n\n'%s' trapped by operation mask\n(F) You tried to use an operator from a Safe compartment in which it's disallowed.  See\nSafe.\n\ntruncate not implemented\n(F) Your machine doesn't implement a file truncation mechanism that Configure knows\nabout.\n\ntry/catch is experimental\n(S experimental::try) This warning is emitted if you use the \"try\" and \"catch\" syntax.\nThis syntax is currently experimental and its behaviour may change in future releases of\nPerl.\n\nType of arg %d to &CORE::%s must be %s\n(F) The subroutine in question in the CORE package requires its argument to be a hard\nreference to data of the specified type.  Overloading is ignored, so a reference to an\nobject that is not the specified type, but nonetheless has overloading to handle it, will\nstill not be accepted.\n\nType of arg %d to %s must be %s (not %s)\n(F) This function requires the argument in that position to be of a certain type.  Arrays\nmust be @NAME or \"@{EXPR}\".  Hashes must be %NAME or \"%{EXPR}\".  No implicit\ndereferencing is allowed--use the {EXPR} forms as an explicit dereference.  See perlref.\n\numask not implemented\n(F) Your machine doesn't implement the umask function and you tried to use it to restrict\npermissions for yourself (EXPR & 0700).\n\nUnbalanced context: %d more PUSHes than POPs\n(S internal) The exit code detected an internal inconsistency in how many execution\ncontexts were entered and left.\n\nUnbalanced saves: %d more saves than restores\n(S internal) The exit code detected an internal inconsistency in how many values were\ntemporarily localized.\n\nUnbalanced scopes: %d more ENTERs than LEAVEs\n(S internal) The exit code detected an internal inconsistency in how many blocks were\nentered and left.\n\nUnbalanced string table refcount: (%d) for \"%s\"\n(S internal) On exit, Perl found some strings remaining in the shared string table used\nfor copy on write and for hash keys.  The entries should have been freed, so this\nindicates a bug somewhere.\n\nUnbalanced tmps: %d more allocs than frees\n(S internal) The exit code detected an internal inconsistency in how many mortal scalars\nwere allocated and freed.\n\nUndefined format \"%s\" called\n(F) The format indicated doesn't seem to exist.  Perhaps it's really in another package?\nSee perlform.\n\nUndefined sort subroutine \"%s\" called\n(F) The sort comparison routine specified doesn't seem to exist.  Perhaps it's in a\ndifferent package?  See \"sort\" in perlfunc.\n\nUndefined subroutine &%s called\n(F) The subroutine indicated hasn't been defined, or if it was, it has since been\nundefined.\n\nUndefined subroutine called\n(F) The anonymous subroutine you're trying to call hasn't been defined, or if it was, it\nhas since been undefined.\n\nUndefined subroutine in sort\n(F) The sort comparison routine specified is declared but doesn't seem to have been\ndefined yet.  See \"sort\" in perlfunc.\n\nUndefined top format \"%s\" called\n(F) The format indicated doesn't seem to exist.  Perhaps it's really in another package?\nSee perlform.\n\nUndefined value assigned to typeglob\n(W misc) An undefined value was assigned to a typeglob, a la \"*foo = undef\".  This does\nnothing.  It's possible that you really mean \"undef *foo\".\n\n%s: Undefined variable\n(A) You've accidentally run your script through csh instead of Perl.  Check the #! line,\nor manually feed your script into Perl yourself.\n\nUnescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/%s/\n(F) The simple rule to remember, if you want to match a literal \"{\" character (U+007B\n\"LEFT CURLY BRACKET\") in a regular expression pattern, is to escape each literal instance\nof it in some way.  Generally easiest is to precede it with a backslash, like \"\\{\" or\nenclose it in square brackets (\"[{]\").  If the pattern delimiters are also braces, any\nmatching right brace (\"}\") should also be escaped to avoid confusing the parser, for\nexample,\n\nqr{abc\\{def\\}ghi}\n\nForcing literal \"{\" characters to be escaped enables the Perl language to be extended in\nvarious ways in future releases.  To avoid needlessly breaking existing code, the\nrestriction is not enforced in contexts where there are unlikely to ever be extensions\nthat could conflict with the use there of \"{\" as a literal.  Those that are not\npotentially ambiguous do not warn; those that are do raise a non-deprecation warning.\n\nThe contexts where no warnings or errors are raised are:\n\n•   as the first character in a pattern, or following \"^\" indicating to anchor the match\nto the beginning of a line.\n\n•   as the first character following a \"|\" indicating alternation.\n\n•   as the first character in a parenthesized grouping like\n\n/foo({bar)/\n/foo(?:{bar)/\n\n•   as the first character following a quantifier\n\n/\\s*{/\n\nUnescaped left brace in regex is passed through in regex; marked by <-- HERE in m/%s/\n(W regexp)  The simple rule to remember, if you want to match a literal \"{\" character\n(U+007B \"LEFT CURLY BRACKET\") in a regular expression pattern, is to escape each literal\ninstance of it in some way.  Generally easiest is to precede it with a backslash, like\n\"\\{\" or enclose it in square brackets (\"[{]\").  If the pattern delimiters are also\nbraces, any matching right brace (\"}\") should also be escaped to avoid confusing the\nparser, for example,\n\nqr{abc\\{def\\}ghi}\n\nForcing literal \"{\" characters to be escaped enables the Perl language to be extended in\nvarious ways in future releases.  To avoid needlessly breaking existing code, the\nrestriction is not enforced in contexts where there are unlikely to ever be extensions\nthat could conflict with the use there of \"{\" as a literal.  Those that are not\npotentially ambiguous do not warn; those that are raise this warning.  This makes sure\nthat an inadvertent typo doesn't silently cause the pattern to compile to something\nunintended.\n\nThe contexts where no warnings or errors are raised are:\n\n•   as the first character in a pattern, or following \"^\" indicating to anchor the match\nto the beginning of a line.\n\n•   as the first character following a \"|\" indicating alternation.\n\n•   as the first character in a parenthesized grouping like\n\n/foo({bar)/\n/foo(?:{bar)/\n\n•   as the first character following a quantifier\n\n/\\s*{/\n\nUnescaped literal '%c' in regex; marked by <-- HERE in m/%s/\n(W regexp) (only under \"use re 'strict'\")\n\nWithin the scope of \"use re 'strict'\" in a regular expression pattern, you included an\nunescaped \"}\" or \"]\" which was interpreted literally.  These two characters are sometimes\nmetacharacters, and sometimes literals, depending on what precedes them in the pattern.\nThis is unlike the similar \")\" which is always a metacharacter unless escaped.\n\nThis action at a distance, perhaps a large distance, can lead to Perl silently\nmisinterpreting what you meant, so when you specify that you want extra checking by\n\"use re 'strict'\", this warning is generated.  If you meant the character as a literal,\nsimply confirm that to Perl by preceding the character with a backslash, or make it into\na bracketed character class (like \"[}]\").  If you meant it as closing a corresponding \"[\"\nor \"{\", you'll need to look back through the pattern to find out why that isn't\nhappening.\n\nunexec of %s into %s failed!\n(F) The unexec() routine failed for some reason.  See your local FSF representative, who\nprobably put it there in the first place.\n\nUnexpected binary operator '%c' with no preceding operand in regex; marked by <-- HERE in\nm/%s/\n(F) You had something like this:\n\n(?[ | \\p{Digit} ])\n\nwhere the \"|\" is a binary operator with an operand on the right, but no operand on the\nleft.\n\nUnexpected character in regex; marked by <-- HERE in m/%s/\n(F) You had something like this:\n\n(?[ z ])\n\nWithin \"(?[ ])\", no literal characters are allowed unless they are within an inner pair\nof square brackets, like\n\n(?[ [ z ] ])\n\nAnother possibility is that you forgot a backslash.  Perl isn't smart enough to figure\nout what you really meant.\n\nUnexpected constant lvalue entersub entry via type/targ %d:%d\n(P) When compiling a subroutine call in lvalue context, Perl failed an internal\nconsistency check.  It encountered a malformed op tree.\n\nUnexpected exit %u\n(S) exit() was called or the script otherwise finished gracefully when \"PERLEXITWARN\"\nwas set in \"PLexitflags\".\n\nUnexpected exit failure %d\n(S) An uncaught die() was called when \"PERLEXITWARN\" was set in \"PLexitflags\".\n\nUnexpected ')' in regex; marked by <-- HERE in m/%s/\n(F) You had something like this:\n\n(?[ ( \\p{Digit} + ) ])\n\nThe \")\" is out-of-place.  Something apparently was supposed to be combined with the\ndigits, or the \"+\" shouldn't be there, or something like that.  Perl can't figure out\nwhat was intended.\n\nUnexpected ']' with no following ')' in (?[... in regex; marked by <-- HERE in m/%s/\n(F) While parsing an extended character class a ']' character was encountered at a point\nin the definition where the only legal use of ']' is to close the character class\ndefinition as part of a '])', you may have forgotten the close paren, or otherwise\nconfused the parser.\n\nUnexpected '(' with no preceding operator in regex; marked by <-- HERE in m/%s/\n(F) You had something like this:\n\n(?[ \\p{Digit} ( \\p{Lao} + \\p{Thai} ) ])\n\nThere should be an operator before the \"(\", as there's no indication as to how the digits\nare to be combined with the characters in the Lao and Thai scripts.\n\nUnicode non-character U+%X is not recommended for open interchange\n(S nonchar) Certain codepoints, such as U+FFFE and U+FFFF, are defined by the Unicode\nstandard to be non-characters.  Those are legal codepoints, but are reserved for internal\nuse; so, applications shouldn't attempt to exchange them.  An application may not be\nexpecting any of these characters at all, and receiving them may lead to bugs.  If you\nknow what you are doing you can turn off this warning by \"no warnings 'nonchar';\".\n\nThis is not really a \"severe\" error, but it is supposed to be raised by default even if\nwarnings are not enabled, and currently the only way to do that in Perl is to mark it as\nserious.\n\nUnicode property wildcard not terminated\n(F) A Unicode property wildcard looks like a delimited regular expression pattern (all\nwithin the braces of the enclosing \"\\p{...}\".  The closing delimtter to match the opening\none was not found.  If the opening one is escaped by preceding it with a backslash, the\nclosing one must also be so escaped.\n\nUnicode string properties are not implemented in (?[...]) in regex; marked by <-- HERE in\nm/%s/\n(F) A Unicode string property is one which expands to a sequence of multiple characters.\nAn example is \"\\p{name=KATAKANA LETTER AINU P}\", which is comprised of the sequence\n\"\\N{KATAKANA LETTER SMALL H}\" followed by \"\\N{COMBINING KATAKANA-HIRAGANA SEMI-VOICED\nSOUND MARK}\".  Extended character classes, \"(?[...])\" currently cannot handle these.\n\nUnicode surrogate U+%X is illegal in UTF-8\n(S surrogate) You had a UTF-16 surrogate in a context where they are not considered\nacceptable.  These code points, between U+D800 and U+DFFF (inclusive), are used by\nUnicode only for UTF-16.  However, Perl internally allows all unsigned integer code\npoints (up to the size limit available on your platform), including surrogates.  But\nthese can cause problems when being input or output, which is likely where this message\ncame from.  If you really really know what you are doing you can turn off this warning by\n\"no warnings 'surrogate';\".\n\nUnknown charname '%s'\n(F) The name you used inside \"\\N{}\" is unknown to Perl.  Check the spelling.  You can say\n\"use charnames \":loose\"\" to not have to be so precise about spaces, hyphens, and\ncapitalization on standard Unicode names.  (Any custom aliases that have been created\nmust be specified exactly, regardless of whether \":loose\" is used or not.)  This error\nmay also happen if the \"\\N{}\" is not in the scope of the corresponding \"use charnames\".\n\nUnknown '(*...)' construct '%s' in regex; marked by <-- HERE in m/%s/\n(F) The \"(*\" was followed by something that the regular expression compiler does not\nrecognize.  Check your spelling.\n\nUnknown error\n(P) Perl was about to print an error message in $@, but the $@ variable did not exist,\neven after an attempt to create it.\n\nUnknown locale category %d; can't set it to %s\n(W locale) You used a locale category that perl doesn't recognize, so it cannot carry out\nyour request.  Check that you are using a valid category.  If so, see \"Multi-threaded\" in\nperllocale for advice on reporting this as a bug, and for modifying perl locally to\naccommodate your needs.\n\nUnknown open() mode '%s'\n(F) The second argument of 3-argument open() is not among the list of valid modes: \"<\",\n\">\", \">>\", \"+<\", \"+>\", \"+>>\", \"-|\", \"|-\", \"<&\", \">&\".\n\nUnknown PerlIO layer \"%s\"\n(W layer) An attempt was made to push an unknown layer onto the Perl I/O system.  (Layers\ntake care of transforming data between external and internal representations.)  Note that\nsome layers, such as \"mmap\", are not supported in all environments.  If your program\ndidn't explicitly request the failing operation, it may be the result of the value of the\nenvironment variable PERLIO.\n\nUnknown process %x sent message to primeenviter: %s\n(P) An error peculiar to VMS.  Perl was reading values for %ENV before iterating over it,\nand someone else stuck a message in the stream of data Perl expected.  Someone's very\nconfused, or perhaps trying to subvert Perl's population of %ENV for nefarious purposes.\n\nUnknown regexp modifier \"/%s\"\n(F) Alphanumerics immediately following the closing delimiter of a regular expression\npattern are interpreted by Perl as modifier flags for the regex.  One of the ones you\nspecified is invalid.  One way this can happen is if you didn't put in white space\nbetween the end of the regex and a following alphanumeric operator:\n\nif ($a =~ /foo/and $bar == 3) { ... }\n\nThe \"a\" is a valid modifier flag, but the \"n\" is not, and raises this error.  Likely what\nwas meant instead was:\n\nif ($a =~ /foo/ and $bar == 3) { ... }\n\nUnknown \"re\" subpragma '%s' (known ones are: %s)\n(W) You tried to use an unknown subpragma of the \"re\" pragma.\n\nUnknown switch condition (?(...)) in regex; marked by <-- HERE in m/%s/\n(F) The condition part of a (?(condition)if-clause|else-clause) construct is not known.\nThe condition must be one of the following:\n\n(1) (2) ...            true if 1st, 2nd, etc., capture matched\n(<NAME>) ('NAME')      true if named capture matched\n(?=...) (?<=...)       true if subpattern matches\n(*pla:...) (*plb:...)  true if subpattern matches; also\n(*positivelookahead:...)\n(*positivelookbehind:...)\n(*nla:...) (*nlb:...)  true if subpattern fails to match; also\n(*negativelookahead:...)\n(*negativelookbehind:...)\n(?{ CODE })            true if code returns a true value\n(R)                    true if evaluating inside recursion\n(R1) (R2) ...          true if directly inside capture group 1, 2,\netc.\n(R&NAME)               true if directly inside named capture\n(DEFINE)               always false; for defining named subpatterns\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.  See\nperlre.\n\nUnknown Unicode option letter '%c'\n(F) You specified an unknown Unicode option.  See perlrun documentation of the \"-C\"\nswitch for the list of known options.\n\nUnknown Unicode option value %d\n(F) You specified an unknown Unicode option.  See perlrun documentation of the \"-C\"\nswitch for the list of known options.\n\nUnknown user-defined property name \\p{%s}\n(F) You specified to use a property within the \"\\p{...}\" which was a syntactically valid\nuser-defined property, but no definition was found for it by the time one was required to\nproceed.  Check your spelling.  See \"User-Defined Character Properties\" in perlunicode.\n\nUnknown verb pattern '%s' in regex; marked by <-- HERE in m/%s/\n(F) You either made a typo or have incorrectly put a \"*\" quantifier after an open brace\nin your pattern.  Check the pattern and review perlre for details on legal verb patterns.\n\nUnknown warnings category '%s'\n(F) An error issued by the \"warnings\" pragma.  You specified a warnings category that is\nunknown to perl at this point.\n\nNote that if you want to enable a warnings category registered by a module (e.g. \"use\nwarnings 'File::Find'\"), you must have loaded this module first.\n\nUnmatched [ in regex; marked by <-- HERE in m/%s/\n(F) The brackets around a character class must match.  If you wish to include a closing\nbracket in a character class, backslash it or put it first.  The <-- HERE shows\nwhereabouts in the regular expression the problem was discovered.  See perlre.\n\nUnmatched ( in regex; marked by <-- HERE in m/%s/\nUnmatched ) in regex; marked by <-- HERE in m/%s/\n(F) Unbackslashed parentheses must always be balanced in regular expressions.  If you're\na vi user, the % key is valuable for finding the matching parenthesis.  The <-- HERE\nshows whereabouts in the regular expression the problem was discovered.  See perlre.\n\nUnmatched right %s bracket\n(F) The lexer counted more closing curly or square brackets than opening ones, so you're\nprobably missing a matching opening bracket.  As a general rule, you'll find the missing\none (so to speak) near the place you were last editing.\n\nUnquoted string \"%s\" may clash with future reserved word\n(W reserved) You used a bareword that might someday be claimed as a reserved word.  It's\nbest to put such a word in quotes, or capitalize it somehow, or insert an underbar into\nit.  You might also declare it as a subroutine.\n\nUnrecognized character %s; marked by <-- HERE after %s near column %d\n(F) The Perl parser has no idea what to do with the specified character in your Perl\nscript (or eval) near the specified column.  Perhaps you tried  to run a compressed\nscript, a binary program, or a directory as a Perl program.\n\nUnrecognized escape \\%c in character class in regex; marked by <-- HERE in m/%s/\n(F) You used a backslash-character combination which is not recognized by Perl inside\ncharacter classes.  This is a fatal error when the character class is used within \"(?[\n])\".\n\nUnrecognized escape \\%c in character class passed through in regex; marked by <-- HERE in\nm/%s/\n(W regexp) You used a backslash-character combination which is not recognized by Perl\ninside character classes.  The character was understood literally, but this may change in\na future version of Perl.  The <-- HERE shows whereabouts in the regular expression the\nescape was discovered.\n\nUnrecognized escape \\%c passed through\n(W misc) You used a backslash-character combination which is not recognized by Perl.  The\ncharacter was understood literally, but this may change in a future version of Perl.\n\nUnrecognized escape \\%s passed through in regex; marked by <-- HERE in m/%s/\n(W regexp) You used a backslash-character combination which is not recognized by Perl.\nThe character(s) were understood literally, but this may change in a future version of\nPerl.  The <-- HERE shows whereabouts in the regular expression the escape was\ndiscovered.\n\nUnrecognized signal name \"%s\"\n(F) You specified a signal name to the kill() function that was not recognized.  Say\n\"kill -l\" in your shell to see the valid signal names on your system.\n\nUnrecognized switch: -%s  (-h will show valid options)\n(F) You specified an illegal option to Perl.  Don't do that.  (If you think you didn't do\nthat, check the #! line to see if it's supplying the bad switch on your behalf.)\n\nUnsuccessful %s on filename containing newline\n(W newline) A file operation was attempted on a filename, and that operation failed,\nPROBABLY because the filename contained a newline, PROBABLY because you forgot to chomp()\nit off.  See \"chomp\" in perlfunc.\n\nUnsupported directory function \"%s\" called\n(F) Your machine doesn't support opendir() and readdir().\n\nUnsupported function %s\n(F) This machine doesn't implement the indicated function, apparently.  At least,\nConfigure doesn't think so.\n\nUnsupported function fork\n(F) Your version of executable does not support forking.\n\nNote that under some systems, like OS/2, there may be different flavors of Perl\nexecutables, some of which may support fork, some not.  Try changing the name you call\nPerl by to \"perl\", \"perl\", and so on.\n\nUnsupported script encoding %s\n(F) Your program file begins with a Unicode Byte Order Mark (BOM) which declares it to be\nin a Unicode encoding that Perl cannot read.\n\nUnsupported socket function \"%s\" called\n(F) Your machine doesn't support the Berkeley socket mechanism, or at least that's what\nConfigure thought.\n\nUnterminated '(*...' argument in regex; marked by <-- HERE in m/%s/\n(F) You used a pattern of the form \"(*...:...)\" but did not terminate the pattern with a\n\")\".  Fix the pattern and retry.\n\nUnterminated attribute list\n(F) The lexer found something other than a simple identifier at the start of an\nattribute, and it wasn't a semicolon or the start of a block.  Perhaps you terminated the\nparameter list of the previous attribute too soon.  See attributes.\n\nUnterminated attribute parameter in attribute list\n(F) The lexer saw an opening (left) parenthesis character while parsing an attribute\nlist, but the matching closing (right) parenthesis character was not found.  You may need\nto add (or remove) a backslash character to get your parentheses to balance.  See\nattributes.\n\nUnterminated compressed integer\n(F) An argument to unpack(\"w\",...) was incompatible with the BER compressed integer\nformat and could not be converted to an integer.  See \"pack\" in perlfunc.\n\nUnterminated '(*...' construct in regex; marked by <-- HERE in m/%s/\n(F) You used a pattern of the form \"(*...)\" but did not terminate the pattern with a \")\".\nFix the pattern and retry.\n\nUnterminated delimiter for here document\n(F) This message occurs when a here document label has an initial quotation mark but the\nfinal quotation mark is missing.  Perhaps you wrote:\n\n<<\"foo\n\ninstead of:\n\n<<\"foo\"\n\nUnterminated \\g... pattern in regex; marked by <-- HERE in m/%s/\nUnterminated \\g{...} pattern in regex; marked by <-- HERE in m/%s/\n(F) In a regular expression, you had a \"\\g\" that wasn't followed by a proper group\nreference.  In the case of \"\\g{\", the closing brace is missing; otherwise the \"\\g\" must\nbe followed by an integer.  Fix the pattern and retry.\n\nUnterminated <> operator\n(F) The lexer saw a left angle bracket in a place where it was expecting a term, so it's\nlooking for the corresponding right angle bracket, and not finding it.  Chances are you\nleft some needed parentheses out earlier in the line, and you really meant a \"less than\".\n\nUnterminated verb pattern argument in regex; marked by <-- HERE in m/%s/\n(F) You used a pattern of the form \"(*VERB:ARG)\" but did not terminate the pattern with a\n\")\".  Fix the pattern and retry.\n\nUnterminated verb pattern in regex; marked by <-- HERE in m/%s/\n(F) You used a pattern of the form \"(*VERB)\" but did not terminate the pattern with a\n\")\".  Fix the pattern and retry.\n\nuntie attempted while %d inner references still exist\n(W untie) A copy of the object returned from \"tie\" (or \"tied\") was still valid when\n\"untie\" was called.\n\nUsage: POSIX::%s(%s)\n(F) You called a POSIX function with incorrect arguments.  See \"FUNCTIONS\" in POSIX for\nmore information.\n\nUsage: Win32::%s(%s)\n(F) You called a Win32 function with incorrect arguments.  See Win32 for more\ninformation.\n\n$[ used in %s (did you mean $] ?)\n(W syntax) You used $[ in a comparison, such as:\n\nif ($[ > 5.006) {\n...\n}\n\nYou probably meant to use $] instead.  $[ is the base for indexing arrays.  $] is the\nPerl version number in decimal.\n\nUse \"%s\" instead of \"%s\"\n(F) The second listed construct is no longer legal.  Use the first one instead.\n\nUseless assignment to a temporary\n(W misc) You assigned to an lvalue subroutine, but what the subroutine returned was a\ntemporary scalar about to be discarded, so the assignment had no effect.\n\nUseless (?-%s) - don't use /%s modifier in regex; marked by <-- HERE in m/%s/\n(W regexp) You have used an internal modifier such as (?-o) that has no meaning unless\nremoved from the entire regexp:\n\nif ($string =~ /(?-o)$pattern/o) { ... }\n\nmust be written as\n\nif ($string =~ /$pattern/) { ... }\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.  See\nperlre.\n\nUseless localization of %s\n(W syntax) The localization of lvalues such as \"local($x=10)\" is legal, but in fact the\nlocal() currently has no effect.  This may change at some point in the future, but in the\nmeantime such code is discouraged.\n\nUseless (?%s) - use /%s modifier in regex; marked by <-- HERE in m/%s/\n(W regexp) You have used an internal modifier such as (?o) that has no meaning unless\napplied to the entire regexp:\n\nif ($string =~ /(?o)$pattern/) { ... }\n\nmust be written as\n\nif ($string =~ /$pattern/o) { ... }\n\nThe <-- HERE shows whereabouts in the regular expression the problem was discovered.  See\nperlre.\n\nUseless use of attribute \"const\"\n(W misc) The \"const\" attribute has no effect except on anonymous closure prototypes.  You\napplied it to a subroutine via attributes.pm.  This is only useful inside an attribute\nhandler for an anonymous subroutine.\n\nUseless use of /d modifier in transliteration operator\n(W misc) You have used the /d modifier where the searchlist has the same length as the\nreplacelist.  See perlop for more information about the /d modifier.\n\nUseless use of \\E\n(W misc) You have a \\E in a double-quotish string without a \"\\U\", \"\\L\" or \"\\Q\" preceding\nit.\n\nUseless use of greediness modifier '%c' in regex; marked by <-- HERE in m/%s/\n(W regexp) You specified something like these:\n\nqr/a{3}?/\nqr/b{1,1}+/\n\nThe \"?\" and \"+\" don't have any effect, as they modify whether to match more or fewer when\nthere is a choice, and by specifying to match exactly a given numer, there is no room\nleft for a choice.\n\nUseless use of %s in void context\n(W void) You did something without a side effect in a context that does nothing with the\nreturn value, such as a statement that doesn't return a value from a block, or the left\nside of a scalar comma operator.  Very often this points not to stupidity on your part,\nbut a failure of Perl to parse your program the way you thought it would.  For example,\nyou'd get this if you mixed up your C precedence with Python precedence and said\n\n$one, $two = 1, 2;\n\nwhen you meant to say\n\n($one, $two) = (1, 2);\n\nAnother common error is to use ordinary parentheses to construct a list reference when\nyou should be using square or curly brackets, for example, if you say\n\n$array = (1,2);\n\nwhen you should have said\n\n$array = [1,2];\n\nThe square brackets explicitly turn a list value into a scalar value, while parentheses\ndo not.  So when a parenthesized list is evaluated in a scalar context, the comma is\ntreated like C's comma operator, which throws away the left argument, which is not what\nyou want.  See perlref for more on this.\n\nThis warning will not be issued for numerical constants equal to 0 or 1 since they are\noften used in statements like\n\n1 while subwithsideeffects();\n\nString constants that would normally evaluate to 0 or 1 are warned about.\n\nUseless use of (?-p) in regex; marked by <-- HERE in m/%s/\n(W regexp) The \"p\" modifier cannot be turned off once set.  Trying to do so is futile.\n\nUseless use of \"re\" pragma\n(W) You did \"use re;\" without any arguments.  That isn't very useful.\n\nUseless use of sort in scalar context\n(W void) You used sort in scalar context, as in :\n\nmy $x = sort @y;\n\nThis is not very useful, and perl currently optimizes this away.\n\nUseless use of %s with no values\n(W syntax) You used the push() or unshift() function with no arguments apart from the\narray, like \"push(@x)\" or \"unshift(@foo)\".  That won't usually have any effect on the\narray, so is completely useless.  It's possible in principle that push(@tiedarray) could\nhave some effect if the array is tied to a class which implements a PUSH method.  If so,\nyou can write it as \"push(@tiedarray,())\" to avoid this warning.\n\n\"use\" not allowed in expression\n(F) The \"use\" keyword is recognized and executed at compile time, and returns no useful\nvalue.  See perlmod.\n\nUse of bare << to mean <<\"\" is forbidden\n(F) You are now required to use the explicitly quoted form if you wish to use an empty\nline as the terminator of the here-document.\n\nUse of a bare terminator was deprecated in Perl 5.000, and is a fatal error as of Perl\n5.28.\n\nUse of /c modifier is meaningless in s///\n(W regexp) You used the /c modifier in a substitution.  The /c modifier is not presently\nmeaningful in substitutions.\n\nUse of /c modifier is meaningless without /g\n(W regexp) You used the /c modifier with a regex operand, but didn't use the /g modifier.\nCurrently, /c is meaningful only when /g is used.  (This may change in the future.)\n\nUse of code point 0x%s is not allowed; the permissible max is 0x%X\nUse of code point 0x%s is not allowed; the permissible max is 0x%X in regex; marked by <--\nHERE in m/%s/\n(F) You used a code point that is not allowed, because it is too large.  Unicode only\nallows code points up to 0x10FFFF, but Perl allows much larger ones. Earlier versions of\nPerl allowed code points above IVMAX (0x7FFFFFF on 32-bit platforms, 0x7FFFFFFFFFFFFFFF\non 64-bit platforms), however, this could possibly break the perl interpreter in some\nconstructs, including causing it to hang in a few cases.\n\nIf your code is to run on various platforms, keep in mind that the upper limit depends on\nthe platform.  It is much larger on 64-bit word sizes than 32-bit ones.\n\nThe use of out of range code points was deprecated in Perl 5.24, and became a fatal error\nin Perl 5.28.\n\nUse of each() on hash after insertion without resetting hash iterator results in undefined\nbehavior\n(S internal) The behavior of \"each()\" after insertion is undefined; it may skip items, or\nvisit items more than once.  Consider using \"keys()\" instead of \"each()\".\n\nUse of := for an empty attribute list is not allowed\n(F) The construction \"my $x := 42\" used to parse as equivalent to \"my $x : = 42\"\n(applying an empty attribute list to $x).  This construct was deprecated in 5.12.0, and\nhas now been made a syntax error, so \":=\" can be reclaimed as a new operator in the\nfuture.\n\nIf you need an empty attribute list, for example in a code generator, add a space before\nthe \"=\".\n\nUse of %s for non-UTF-8 locale is wrong.  Assuming a UTF-8 locale\n(W locale)  You are matching a regular expression using locale rules, and the specified\nconstruct was encountered.  This construct is only valid for UTF-8 locales, which the\ncurrent locale isn't.  This doesn't make sense.  Perl will continue, assuming a Unicode\n(UTF-8) locale, but the results are likely to be wrong.\n\nUse of freed value in iteration\n(F) Perhaps you modified the iterated array within the loop?  This error is typically\ncaused by code like the following:\n\n@a = (3,4);\n@a = () for (1,2,@a);\n\nYou are not supposed to modify arrays while they are being iterated over.  For speed and\nefficiency reasons, Perl internally does not do full reference-counting of iterated\nitems, hence deleting such an item in the middle of an iteration causes Perl to see a\nfreed value.\n\nUse of /g modifier is meaningless in split\n(W regexp) You used the /g modifier on the pattern for a \"split\" operator.  Since \"split\"\nalways tries to match the pattern repeatedly, the \"/g\" has no effect.\n\nUse of \"goto\" to jump into a construct is deprecated\n(D deprecated) Using \"goto\" to jump from an outer scope into an inner scope is deprecated\nand should be avoided.\n\nThis was deprecated in Perl 5.12.\n\nUse of '%s' in \\p{} or \\P{} is deprecated because: %s\n(D deprecated) Certain properties are deprecated by Unicode, and may eventually be\nremoved from the Standard, at which time Perl will follow along.  In the meantime, this\nmessage is raised to notify you.\n\nUse of inherited AUTOLOAD for non-method %s::%s() is no longer allowed\n(F) As an accidental feature, \"AUTOLOAD\" subroutines were looked up as methods (using the\n@ISA hierarchy), even when the subroutines to be autoloaded were called as plain\nfunctions (e.g. \"Foo::bar()\"), not as methods (e.g. \"Foo->bar()\" or \"$obj->bar()\").\n\nThis was deprecated in Perl 5.004, and was made fatal in Perl 5.28.\n\nUse of %s in printf format not supported\n(F) You attempted to use a feature of printf that is accessible from only C.  This\nusually means there's a better way to do it in Perl.\n\nUse of %s is not allowed in Unicode property wildcard subpatterns in regex; marked by\n<-- HERE in m/%s/\n(F) You were using a wildcard subpattern a Unicode property value, and the subpattern\ncontained something that is illegal.  Not all regular expression capabilities are legal\nin such subpatterns, and this is one.  Rewrite your subppattern to not use the offending\nconstruct.  See \"Wildcards in Property Values\" in perlunicode.\n\nUse of -l on filehandle%s\n(W io) A filehandle represents an opened file, and when you opened the file it already\nwent past any symlink you are presumably trying to look for.  The operation returned\n\"undef\".  Use a filename instead.\n\nUse of reference \"%s\" as array index\n(W misc) You tried to use a reference as an array index; this probably isn't what you\nmean, because references in numerical context tend to be huge numbers, and so usually\nindicates programmer error.\n\nIf you really do mean it, explicitly numify your reference, like so: $array[0+$ref].\nThis warning is not given for overloaded objects, however, because you can overload the\nnumification and stringification operators and then you presumably know what you are\ndoing.\n\nUse of strings with code points over 0xFF as arguments to %s operator is not allowed\n(F) You tried to use one of the string bitwise operators (\"&\" or \"|\" or \"^\" or \"~\") on a\nstring containing a code point over 0xFF.  The string bitwise operators treat their\noperands as strings of bytes, and values beyond 0xFF are nonsensical in this context.\n\nCertain instances became fatal in Perl 5.28; others in perl 5.32.\n\nUse of strings with code points over 0xFF as arguments to vec is forbidden\n(F) You tried to use \"vec\" on a string containing a code point over 0xFF, which is\nnonsensical here.\n\nThis became fatal in Perl 5.32.\n\nUse of tainted arguments in %s is deprecated\n(W taint, deprecated) You have supplied \"system()\" or \"exec()\" with multiple arguments\nand at least one of them is tainted.  This used to be allowed but will become a fatal\nerror in a future version of perl.  Untaint your arguments.  See perlsec.\n\nUse of unassigned code point or non-standalone grapheme for a delimiter is not allowed\n(F) A grapheme is what appears to a native-speaker of a language to be a character.  In\nUnicode (and hence Perl) a grapheme may actually be several adjacent characters that\ntogether form a complete grapheme.  For example, there can be a base character, like \"R\"\nand an accent, like a circumflex \"^\", that appear when displayed to be a single character\nwith the circumflex hovering over the \"R\".  Perl currently allows things like that\ncircumflex to be delimiters of strings, patterns, etc.  When displayed, the circumflex\nwould look like it belongs to the character just to the left of it.  In order to move the\nlanguage to be able to accept graphemes as delimiters, we cannot allow the use of\ndelimiters which aren't graphemes by themselves.  Also, a delimiter must already be\nassigned (or known to be never going to be assigned) to try to future-proof code, for\notherwise code that works today would fail to compile if the currently unassigned\ndelimiter ends up being something that isn't a stand-alone grapheme.  Because Unicode is\nnever going to assign non-character code points, nor code points that are above the legal\nUnicode maximum, those can be delimiters, and their use is legal.\n\nUse of uninitialized value%s\n(W uninitialized) An undefined value was used as if it were already defined.  It was\ninterpreted as a \"\" or a 0, but maybe it was a mistake.  To suppress this warning assign\na defined value to your variables.\n\nTo help you figure out what was undefined, perl will try to tell you the name of the\nvariable (if any) that was undefined.  In some cases it cannot do this, so it also tells\nyou what operation you used the undefined value in.  Note, however, that perl optimizes\nyour program and the operation displayed in the warning may not necessarily appear\nliterally in your program.  For example, \"that $foo\" is usually optimized into \"\"that \" .\n$foo\", and the warning will refer to the \"concatenation (.)\" operator, even though there\nis no \".\" in your program.\n\n\"use re 'strict'\" is experimental\n(S experimental::restrict) The things that are different when a regular expression\npattern is compiled under 'strict' are subject to change in future Perl releases in\nincompatible ways.  This means that a pattern that compiles today may not in a future\nPerl release.  This warning is to alert you to that risk.\n\nUse \\x{...} for more than two hex characters in regex; marked by <-- HERE in m/%s/\n(F) In a regular expression, you said something like\n\n(?[ [ \\xBEEF ] ])\n\nPerl isn't sure if you meant this\n\n(?[ [ \\x{BEEF} ] ])\n\nor if you meant this\n\n(?[ [ \\x{BE} E F ] ])\n\nYou need to add either braces or blanks to disambiguate.\n\nUsing just the first character returned by \\N{} in character class in regex; marked by\n<-- HERE in m/%s/\n(W regexp) Named Unicode character escapes \"(\\N{...})\" may return a multi-character\nsequence.  Even though a character class is supposed to match just one character of\ninput, perl will match the whole thing correctly, except when the class is inverted\n(\"[^...]\"), or the escape is the beginning or final end point of a range.  For these,\nwhat should happen isn't clear at all.  In these circumstances, Perl discards all but the\nfirst character of the returned sequence, which is not likely what you want.\n\nUsing just the single character results returned by \\p{} in (?[...]) in regex; marked by\n<-- HERE in m/%s/\n(W regexp) Extended character classes currently cannot handle operands that evaluate to\nmore than one character.  These are removed from the results of the expansion of the\n\"\\p{}\".\n\nThis situation can happen, for example, in\n\n(?[ \\p{name=/KATAKANA/} ])\n\n\"KATAKANA LETTER AINU P\" is a legal Unicode name (technically a \"named sequence\"), but it\nis actually two characters.  The above expression with match only the Unicode names\ncontaining KATAKANA that represent single characters.\n\nUsing /u for '%s' instead of /%s in regex; marked by <-- HERE in m/%s/\n(W regexp) You used a Unicode boundary (\"\\b{...}\" or \"\\B{...}\") in a portion of a regular\nexpression where the character set modifiers \"/a\" or \"/aa\" are in effect.  These two\nmodifiers indicate an ASCII interpretation, and this doesn't make sense for a Unicode\ndefinition.  The generated regular expression will compile so that the boundary uses all\nof Unicode.  No other portion of the regular expression is affected.\n\nUsing !~ with %s doesn't make sense\n(F) Using the \"!~\" operator with \"s///r\", \"tr///r\" or \"y///r\" is currently reserved for\nfuture use, as the exact behavior has not been decided.  (Simply returning the boolean\nopposite of the modified string is usually not particularly useful.)\n\nUTF-16 surrogate U+%X\n(S surrogate) You had a UTF-16 surrogate in a context where they are not considered\nacceptable.  These code points, between U+D800 and U+DFFF (inclusive), are used by\nUnicode only for UTF-16.  However, Perl internally allows all unsigned integer code\npoints (up to the size limit available on your platform), including surrogates.  But\nthese can cause problems when being input or output, which is likely where this message\ncame from.  If you really really know what you are doing you can turn off this warning by\n\"no warnings 'surrogate';\".\n\nValue of %s can be \"0\"; test with defined()\n(W misc) In a conditional expression, you used <HANDLE>, <*> (glob), \"each()\", or\n\"readdir()\" as a boolean value.  Each of these constructs can return a value of \"0\"; that\nwould make the conditional expression false, which is probably not what you intended.\nWhen using these constructs in conditional expressions, test their values with the\n\"defined\" operator.\n\nValue of CLI symbol \"%s\" too long\n(W misc) A warning peculiar to VMS.  Perl tried to read the value of an %ENV element from\na CLI symbol table, and found a resultant string longer than 1024 characters.  The return\nvalue has been truncated to 1024 characters.\n\nVariable \"%s\" is not available\n(W closure) During compilation, an inner named subroutine or eval is attempting to\ncapture an outer lexical that is not currently available.  This can happen for one of two\nreasons.  First, the outer lexical may be declared in an outer anonymous subroutine that\nhas not yet been created.  (Remember that named subs are created at compile time, while\nanonymous subs are created at run-time.)  For example,\n\nsub { my $a; sub f { $a } }\n\nAt the time that f is created, it can't capture the current value of $a, since the\nanonymous subroutine hasn't been created yet.  Conversely, the following won't give a\nwarning since the anonymous subroutine has by now been created and is live:\n\nsub { my $a; eval 'sub f { $a }' }->();\n\nThe second situation is caused by an eval accessing a variable that has gone out of\nscope, for example,\n\nsub f {\nmy $a;\nsub { eval '$a' }\n}\nf()->();\n\nHere, when the '$a' in the eval is being compiled, f() is not currently being executed,\nso its $a is not available for capture.\n\nVariable \"%s\" is not imported%s\n(S misc) With \"use strict\" in effect, you referred to a global variable that you\napparently thought was imported from another module, because something else of the same\nname (usually a subroutine) is exported by that module.  It usually means you put the\nwrong funny character on the front of your variable. It is also possible you used an\n\"our\" variable whose scope has ended.\n\nVariable length lookbehind not implemented in regex m/%s/\n(F) This message no longer should be raised as of Perl 5.30.  It is retained in this\ndocument as a convenience for people using an earlier Perl version.\n\nIn Perl 5.30 and earlier, lookbehind is allowed only for subexpressions whose length is\nfixed and known at compile time.  For positive lookbehind, you can use the \"\\K\" regex\nconstruct as a way to get the equivalent functionality.  See (?<=pattern) and \\K in\nperlre.\n\nStarting in Perl 5.18, there are non-obvious Unicode rules under \"/i\" that can match\nvariably, but which you might not think could.  For example, the substring \"ss\" can match\nthe single character LATIN SMALL LETTER SHARP S.  Here's a complete list of the current\nones affecting ASCII characters:\n\nASCII\nsequence      Matches single letter under /i\nFF          U+FB00 LATIN SMALL LIGATURE FF\nFFI         U+FB03 LATIN SMALL LIGATURE FFI\nFFL         U+FB04 LATIN SMALL LIGATURE FFL\nFI          U+FB01 LATIN SMALL LIGATURE FI\nFL          U+FB02 LATIN SMALL LIGATURE FL\nSS          U+00DF LATIN SMALL LETTER SHARP S\nU+1E9E LATIN CAPITAL LETTER SHARP S\nST          U+FB06 LATIN SMALL LIGATURE ST\nU+FB05 LATIN SMALL LIGATURE LONG S T\n\nThis list is subject to change, but is quite unlikely to.  Each ASCII sequence can be any\ncombination of upper- and lowercase.\n\nYou can avoid this by using a bracketed character class in the lookbehind assertion, like\n\n(?<![sS]t)\n(?<![fF]f[iI])\n\nThis fools Perl into not matching the ligatures.\n\nAnother option for Perls starting with 5.16, if you only care about ASCII matches, is to\nadd the \"/aa\" modifier to the regex.  This will exclude all these non-obvious matches,\nthus getting rid of this message.  You can also say\n\nuse if $] ge 5.016, re => '/aa';\n\nto apply \"/aa\" to all regular expressions compiled within its scope.  See re.\n\n\"%s\" variable %s masks earlier declaration in same %s\n(W shadow) A \"my\", \"our\" or \"state\" variable has been redeclared in the current scope or\nstatement, effectively eliminating all access to the previous instance.  This is almost\nalways a typographical error.  Note that the earlier variable will still exist until the\nend of the scope or until all closure references to it are destroyed.\n\nVariable syntax\n(A) You've accidentally run your script through csh instead of Perl.  Check the #! line,\nor manually feed your script into Perl yourself.\n\nVariable \"%s\" will not stay shared\n(W closure) An inner (nested) named subroutine is referencing a lexical variable defined\nin an outer named subroutine.\n\nWhen the inner subroutine is called, it will see the value of the outer subroutine's\nvariable as it was before and during the *first* call to the outer subroutine; in this\ncase, after the first call to the outer subroutine is complete, the inner and outer\nsubroutines will no longer share a common value for the variable.  In other words, the\nvariable will no longer be shared.\n\nThis problem can usually be solved by making the inner subroutine anonymous, using the\n\"sub {}\" syntax.  When inner anonymous subs that reference variables in outer subroutines\nare created, they are automatically rebound to the current values of such variables.\n\nvector argument not supported with alpha versions\n(S printf) The %vd (s)printf format does not support version objects with alpha parts.\n\nVerb pattern '%s' has a mandatory argument in regex; marked by <-- HERE in m/%s/\n(F) You used a verb pattern that requires an argument.  Supply an argument or check that\nyou are using the right verb.\n\nVerb pattern '%s' may not have an argument in regex; marked by <-- HERE in m/%s/\n(F) You used a verb pattern that is not allowed an argument.  Remove the argument or\ncheck that you are using the right verb.\n\nVersion control conflict marker\n(F) The parser found a line starting with \"<<<<<<<\", \">>>>>>>\", or \"=======\".  These may\nbe left by a version control system to mark conflicts after a failed merge operation.\n\nVersion number must be a constant number\n(P) The attempt to translate a \"use Module n.n LIST\" statement into its equivalent\n\"BEGIN\" block found an internal inconsistency with the version number.\n\nVersion string '%s' contains invalid data; ignoring: '%s'\n(W misc) The version string contains invalid characters at the end, which are being\nignored.\n\nWarning: something's wrong\n(W) You passed warn() an empty string (the equivalent of \"warn \"\"\") or you called it with\nno args and $@ was empty.\n\nWarning: unable to close filehandle %s properly\n(S) The implicit close() done by an open() got an error indication on the close().  This\nusually indicates your file system ran out of disk space.\n\nWarning: unable to close filehandle properly: %s\nWarning: unable to close filehandle %s properly: %s\n(S io) There were errors during the implicit close() done on a filehandle when its\nreference count reached zero while it was still open, e.g.:\n\n{\nopen my $fh, '>', $file  or die \"open: '$file': $!\\n\";\nprint $fh $data or die \"print: $!\";\n} # implicit close here\n\nBecause various errors may only be detected by close() (e.g. buffering could allow the\n\"print\" in this example to return true even when the disk is full), it is dangerous to\nignore its result.  So when it happens implicitly, perl will signal errors by warning.\n\nPrior to version 5.22.0, perl ignored such errors, so the common idiom shown above was\nliable to cause silent data loss.\n\nWarning: Use of \"%s\" without parentheses is ambiguous\n(S ambiguous) You wrote a unary operator followed by something that looks like a binary\noperator that could also have been interpreted as a term or unary operator.  For\ninstance, if you know that the rand function has a default argument of 1.0, and you write\n\nrand + 5;\n\nyou may THINK you wrote the same thing as\n\nrand() + 5;\n\nbut in actual fact, you got\n\nrand(+5);\n\nSo put in parentheses to say what you really mean.\n\nwhen is experimental\n(S experimental::smartmatch) \"when\" depends on smartmatch, which is experimental.\nAdditionally, it has several special cases that may not be immediately obvious, and their\nbehavior may change or even be removed in any future release of perl.  See the\nexplanation under \"Experimental Details on given and when\" in perlsyn.\n\nWide character in %s\n(S utf8) Perl met a wide character (ordinal >255) when it wasn't expecting one.  This\nwarning is by default on for I/O (like print).\n\nIf this warning does come from I/O, the easiest way to quiet it is simply to add the\n\":utf8\" layer, e.g., \"binmode STDOUT, ':utf8'\".  Another way to turn off the warning is\nto add \"no warnings 'utf8';\" but that is often closer to cheating.  In general, you are\nsupposed to explicitly mark the filehandle with an encoding, see open and \"binmode\" in\nperlfunc.\n\nIf the warning comes from other than I/O, this diagnostic probably indicates that\nincorrect results are being obtained.  You should examine your code to determine how a\nwide character is getting to an operation that doesn't handle them.\n\nWide character (U+%X) in %s\n(W locale) While in a single-byte locale (i.e., a non-UTF-8 one), a multi-byte character\nwas encountered.   Perl considers this character to be the specified Unicode code point.\nCombining non-UTF-8 locales and Unicode is dangerous.  Almost certainly some characters\nwill have two different representations.  For example, in the ISO 8859-7 (Greek) locale,\nthe code point 0xC3 represents a Capital Gamma.  But so also does 0x393.  This will make\nstring comparisons unreliable.\n\nYou likely need to figure out how this multi-byte character got mixed up with your\nsingle-byte locale (or perhaps you thought you had a UTF-8 locale, but Perl disagrees).\n\nWithin []-length '%c' not allowed\n(F) The count in the (un)pack template may be replaced by \"[TEMPLATE]\" only if \"TEMPLATE\"\nalways matches the same amount of packed bytes that can be determined from the template\nalone.  This is not possible if it contains any of the codes @, /, U, u, w or a *-length.\nRedesign the template.\n\nWhile trying to resolve method call %s->%s() can not locate package \"%s\" yet it is mentioned\nin @%s::ISA (perhaps you forgot to load \"%s\"?)\n(W syntax) It is possible that the @ISA contains a misspelled or never loaded package\nname, which can result in perl choosing an unexpected parent class's method to resolve\nthe method call. If this is deliberate you can do something like\n\n@Missing::Package::ISA = ();\n\nto silence the warnings, otherwise you should correct the package name, or ensure that\nthe package is loaded prior to the method call.\n\n%s() with negative argument\n(S misc) Certain operations make no sense with negative arguments.  Warning is given and\nthe operation is not done.\n\nwrite() on closed filehandle %s\n(W closed) The filehandle you're writing to got itself closed sometime before now.  Check\nyour control flow.\n\n%s \"\\x%X\" does not map to Unicode\n(S utf8) When reading in different encodings, Perl tries to map everything into Unicode\ncharacters.  The bytes you read in are not legal in this encoding.  For example\n\nutf8 \"\\xE4\" does not map to Unicode\n\nif you try to read in the a-diaereses Latin-1 as UTF-8.\n\n'X' outside of string\n(F) You had a (un)pack template that specified a relative position before the beginning\nof the string being (un)packed.  See \"pack\" in perlfunc.\n\n'x' outside of string in unpack\n(F) You had a pack template that specified a relative position after the end of the\nstring being unpacked.  See \"pack\" in perlfunc.\n\nYOU HAVEN'T DISABLED SET-ID SCRIPTS IN THE KERNEL YET!\n(F) And you probably never will, because you probably don't have the sources to your\nkernel, and your vendor probably doesn't give a rip about what you want.  There is a\nvulnerability anywhere that you have a set-id script, and to close it you need to remove\nthe set-id bit from the script that you're attempting to run.  To actually run the script\nset-id, your best bet is to put a set-id C wrapper around your script.\n\nYou need to quote \"%s\"\n(W syntax) You assigned a bareword as a signal handler name.  Unfortunately, you already\nhave a subroutine of that name declared, which means that Perl 5 will try to call the\nsubroutine when the assignment is executed, which is probably not what you want.  (If it\nIS what you want, put an & in front.)\n\nYour random numbers are not that random\n(F) When trying to initialize the random seed for hashes, Perl could not get any\nrandomness out of your system.  This usually indicates Something Very Wrong.\n\nZero length \\N{} in regex; marked by <-- HERE in m/%s/\n(F) Named Unicode character escapes (\"\\N{...}\") may return a zero-length sequence.  Such\nan escape was used in an extended character class, i.e.  \"(?[...])\", or under \"use re\n'strict'\", which is not permitted.  Check that the correct escape has been used, and the\ncorrect charnames handler is in scope.  The <-- HERE shows whereabouts in the regular\nexpression the problem was discovered.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "warnings, diagnostics.\n\n\n\nperl v5.34.0                                 2025-07-25                                  PERLDIAG(1)",
            "subsections": []
        }
    },
    "summary": "perldiag - various Perl diagnostics",
    "flags": [],
    "examples": [],
    "see_also": []
}