{ "content": [ { "type": "text", "text": "# perldiag (perldoc)\n\n## NAME\n\nperldiag - various Perl diagnostics\n\n## DESCRIPTION\n\nThese messages are classified as follows (listed in increasing order of desperation):\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION** (45 subsections)\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "perldiag", "section": "", "mode": "perldoc", "summary": "perldiag - various Perl diagnostics", "synopsis": null, "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 33, "subsections": [ { "name": "accept", "lines": 430 }, { "name": "bind", "lines": 3 }, { "name": "binmode", "lines": 819 }, { "name": "chdir", "lines": 11 }, { "name": "closedir", "lines": 3 }, { "name": "close", "lines": 82 }, { "name": "connect", "lines": 237 }, { "name": "dump", "lines": 243 }, { "name": "flock", "lines": 47 }, { "name": "getsockopt", "lines": 28 }, { "name": "gmtime", "lines": 3 }, { "name": "gmtime", "lines": 4 }, { "name": "gmtime", "lines": 477 }, { "name": "ioctl", "lines": 108 }, { "name": "length", "lines": 20 }, { "name": "listen", "lines": 82 }, { "name": "localtime", "lines": 3 }, { "name": "localtime", "lines": 4 }, { "name": "localtime", "lines": 16 }, { "name": "lstat", "lines": 1307 }, { "name": "printf", "lines": 85 }, { "name": "readdir", "lines": 3 }, { "name": "readline", "lines": 3 }, { "name": "readline", "lines": 2 }, { "name": "read", "lines": 2 }, { "name": "read", "lines": 5 }, { "name": "realloc", "lines": 125 }, { "name": "rewinddir", "lines": 40 }, { "name": "seekdir", "lines": 24 }, { "name": "send", "lines": 93 }, { "name": "setegid", "lines": 3 }, { "name": "seteuid", "lines": 7 }, { "name": "setrgid", "lines": 3 }, { "name": "setruid", "lines": 3 }, { "name": "setsockopt", "lines": 34 }, { "name": "shutdown", "lines": 11 }, { "name": "sleep", "lines": 32 }, { "name": "splice", "lines": 30 }, { "name": "stat", "lines": 169 }, { "name": "sysread", "lines": 2 }, { "name": "sysread", "lines": 7 }, { "name": "syswrite", "lines": 11 }, { "name": "telldir", "lines": 3 }, { "name": "tell", "lines": 1257 }, { "name": "write", "lines": 43 } ] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] } ], "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 controlled\nusing the \"warnings\" pragma.\n\nIf a message can be controlled by the \"warnings\" pragma, its warning category is included with\nthe classification letter in the description below. E.g. \"(W closed)\" means a warning in the\n\"closed\" category.\n\nOptional warnings are enabled by using the \"warnings\" pragma or the -w and -W switches. Warnings\nmay be captured by setting $SIG{WARN} to a reference to a routine that will be called on\neach 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 all\ncases, warnings may be selectively disabled or promoted to fatal errors using the \"warnings\"\npragma. 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. These\nescapes are ignored by the alphabetical order, as are all characters other than letters. To look\nup your message, just ignore anything that is not a letter.\n", "subsections": [ { "name": "accept", "content": "(W closed) You tried to do an accept on a closed socket. Did you forget to check the return\nvalue 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 on\nthe left-hand side of an assignment to alias one variable to another. Simply suppress the\nwarning if you want to use the feature, but know that in doing so you are taking the risk of\nusing an experimental feature which may change or be removed in a future Perl version:\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 call\nthe builtin because the subroutine is not imported.\n\nTo force interpretation as a subroutine call, either put an ampersand before the subroutine\nname, or qualify the name with its package. Alternatively, you can import the subroutine (or\npretend 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 (e.g.\n\"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 a\n\"-\" character in a transliteration, put it either first or last. (In the past, \"tr/a-z-0//\"\nwas synonymous with \"tr/a-y//\", which was probably not what you would have expected.)\n\nAmbiguous use of %s resolved as %s\n(S ambiguous) You said something that may not be interpreted the way you thought. Normally\nit's pretty easy to disambiguate it by supplying a missing quote, operator, parenthesis pair\nor 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 call\nto the function \"foo\", negated. If you meant the string, just write \"-foo\". If you meant the\nfunction 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 of\nthem. We assumed you meant the infix operator, but please try to make it more clear -- in\nthe example given, you might write \"*foo * foo()\" if you really meant to multiply a glob by\nthe 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 the\nfunction, write \"@{foo()}\" ... or you could just not have a variable and a function with the\nsame 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 Perl\nkeyword), which might be looking for element number 2 of the array named @foo, in which case\nplease write $foo[2], or you might have meant to pass an anonymous arrayref to the function\nnamed foo, and then do a scalar deref on the value it returns. If you meant that, write\n\"${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 is\nwhat you want, you can avoid the warning by changing \"/${length[2345]}/\" to the unsightly\n\"/${\\$length[2345]}/\", by renaming your array to something that does not coincide with a\nbuilt-in keyword, or by simply turning off warnings with \"no warnings '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 stream\nto 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 () {\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 info\nof a hash) and then work on that scalar value. This is probably not what you meant to do.\nSee \"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 so\nunfortunate.\n\nNote that for the \"Inf\" and \"NaN\" (infinity and not-a-number) the definition of \"numeric\" is\nsomewhat unusual: the strings themselves (like \"Inf\") are considered numeric, and anything\nfollowing 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 ) that\ncloses the argument list. (Layers take care of transforming data between external and\ninternal representations.) Perl stopped parsing the layer list at this point and did not\nattempt to push this layer. If your program didn't explicitly request the failing operation,\nit 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 expects\neither a number or a string matching \"/^[a-zA-Z]*[0-9]*\\z/\". See \"Auto-increment and\nAuto-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 were\nnot of the same type. You cannot alias a scalar to an array, or an array to a hash; the two\ntypes 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 Perl\n5.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 be\nscalars or both be lists. Otherwise Perl won't know which context to supply to the right\nside.\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 \" 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 be\nfreed. 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 package\nto bless the resulting object into. You've supplied instead a reference to something:\nperhaps 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\" from a\ncustom 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 from a\nrestricted 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 decrement\nthe 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. This\nindicates that something else is freeing the SV before the freetmps() routine gets a\nchance, which means that the freetmps() routine will be freeing an unreferenced scalar when\nit 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 to\n0, and discovered that it had already gone to 0 earlier, and should have been freed, and in\nfact, probably was freed. This could indicate that SvREFCNTdec() was called too many times,\nor that SvREFCNTinc() was called too few times, or that the SV was mortalized when it\nshouldn'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 computed\nexpression) to the \"p\" pack() template. This means the result contains a pointer to a\nlocation that could become invalid anytime, even before the end of the current statement.\nUse literals or global values as arguments to the \"p\" pack() template to 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 by\nstoring 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. Since\neach sub can only have one prototype, the earlier declaration(s) are discarded while the\nlast one is applied.\n\navreify called on tied array\n(S debugging) This indicates that something went wrong and Perl got *very* confused about @\nor @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 filehandle\nassociated with it. Perhaps you didn't do an open(), or did it in another package.\n\nBad free() ignored\n(S malloc) An internal routine called free() on something that had never been malloc()ed in\nthe 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\n*forgiving* 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, or\nmanually 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 malloc()ed\nin the first place. Mandatory, but can be disabled by setting the environment variable\n\"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 table\nentry.\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 table\nentry.\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 been\ngenerated by a valid bareword permitted by the parser. You shouldn't be able to get this\nerror from Perl code, but XS code may throw it if it passes an invalid module name to\n\"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. Write\n\"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 package?\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 be\nused with the \"barewordfilehandles\" feature disabled.\n\nBEGIN failed--compilation aborted\n(F) An untrapped exception was raised while executing a BEGIN subroutine. Compilation stops\nimmediately 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 environment\nfor the \"BEGIN {}\" could not be guaranteed (due to the errors), and since subsequent code\nlikely 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 backslashes\nis grandfathered on the right-hand side of a substitution, but stylistically it's better to\nuse the variable form because other Perl programmers will expect it, and it works better if\nthere 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" }, { "name": "bind", "content": "(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" }, { "name": "binmode", "content": "(W unopened) You tried binmode() on a filehandle that was never opened. Check your control\nflow 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\nnon-portable 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 if\nyou had instead said \"[\\N{U+06}-\\N{U+08}]\", that is it matches the characters whose code\npoints in Unicode are 6, 7, and 8. But that \"\\x08\" might indicate that you meant something\ndifferent, 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, it\nencountered a logical name or symbol definition which was too long, so it was truncated to\nthe 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, you\nmay 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 of\na file specified by a relative path, and your system doesn't include the directory relative\nPOSIX 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, which\nmakes 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 large\nnumber (> 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 only be\nused 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 that\ntypeglob, but it there is no legal conversion from that type of reference to a typeglob.\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 open()\nor 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 supported.\n(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\nvariable-argument list (a \"valist\"). This is not currently supported. XS authors wanting to\ndo this 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 can\nonly be used with positive integers, and you attempted to compress something else. See\n\"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 this\nout from the object reference you supply, but you didn't supply an object reference in this\ncase. A reference isn't an object reference until it has been blessed. See perlobj.\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 object\nreference 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 get\nthe 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 find\nthe class (e.g. LISTOP) of a particular OP, and was unable to do so. This is likely to be\ndue to a bug in the perl internals, or due to a bug in XS code which manipulates perl\noptrees.\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 FIFO\nor 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 file\nwas 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 done;\ninstead the result is the indicated value, which is the best available that uses entirely\nUnicode rules. That turns out to almost always be the original character, unchanged.\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 result\nof this operation to contain a character that is in the range specified by the locale,\n0..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 \"\"use locale ':notcharacters'\"\".\n\nNote that failed case-changing operations done as a result of case-insensitive \"/i\" regular\nexpression matching will show up in this warning as having the \"fc\" operation (as that is\nwhat 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 flags\nis 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, it'd\nbe 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 and\npointers 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 the\nindicated reason. Typical reasons include: the permissions were wrong on the file, the file\nwasn'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 #! line\nsaid. 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 with\nthe 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 go\nto. 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 at\nleast not with the correct permissions. The script exists in the current directory, but PATH\nprohibits 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 whitespace\nbefore or after your closing tag or there may not be a linebreak after it. A good\nprogrammer'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-defined\nproperty 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 seconds.\n\nCan't get filespec - stale stat buffer?\n(S) A warning peculiar to VMS. This arises because of the difference between access checks\nunder VMS and under the Unix model Perl assumes. Under VMS, access checks are done by\nfilename, rather than by bits in the stat buffer, so that ACLs and other protections can be\ntaken into account. Unfortunately, Perl assumes that the stat buffer contains all the\nnecessary information, and passes it, instead of the filespec, to the access-checking\nroutine. It will try to retrieve the filespec using the device name and FID present in the\nstat buffer, but this works only if you haven't made a subsequent call to the CRTL stat()\nroutine, because the device name is overwritten with each call. If this warning appears, the\nname lookup failed, and the access-checking routine gave up and returned FALSE, just to be\nconservative. (Note: The access-checking routine knows about the Perl \"stat\" operator and\nfile tests, so you shouldn't ever see this warning in response to a Perl command; it arises\nonly if some internal code takes stat buffers lightly.)\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 retrieve\nits 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 to\nbe, 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 expression.\nYou can't get there from here. The reason for this restriction is that the interpreter would\nget confused as to how many arguments there are, resulting in stack corruption or crashes.\nThis 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 can't\nget 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 get\nthere 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 that\nit isn't a proper block. This usually occurs if you tried to jump out of a sort() block or\nsubroutine, 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 sort(),\nor 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 it\nout 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 known\nas SIGCLD) disabled. Since disabling this signal will interfere with proper determination of\nexit status of child processes, Perl has reset the signal to its default value. This\nsituation typically indicates that the parent program under which Perl may be running (e.g.\ncron) 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 kill()\nan 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 there's\nthis itty bitty problem called there isn't a current block. Note that an \"if\" or \"else\"\nblock doesn't count as a \"loopish\" block, as doesn't a block given to sort(), map() or\ngrep(). You can usually double the curlies to get the same effect though, because the inner\ncurlies will be considered a block that loops once. See \"last\" in perlfunc.\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 mean\nthat you upgraded your version of perl to one that is incompatible with your old dynamic\nextensions (which is known to happen between major versions of perl), or (more likely) that\nyour dynamic extension was built against an older version of the library that is installed\non 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 of\nthe 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 when\nit goes to restore the old value of whatever $ref pointed to after the scope of the local()\nis 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 for\nthe file in all the locations mentioned in @INC, unless the file name included the full path\nto the file. Perhaps you need to set the PERL5LIB or PERL5OPT environment variable to say\nwhere the extra library is, or maybe the script needs to add the library name to @INC. Or\nmaybe you just misspelled the name of the file. See \"require\" in perlfunc 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 or\nbar.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 in\nUNIVERSAL. This often means that a method requires a package that has not been loaded.\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 exist.\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 from\nthe stated file are made available globally within the process, but that functionality is\nnot available on this platform. Whilst the module likely will still work, this may prevent\nthe perl interpreter from loading other XS-based extensions which need to link directly to\nfunctions 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, such\nas 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 \"Lvalue\nsubroutines\" 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 them.\nSee \"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 clear\nexactly what it should do. If you meant to make @array refer to some other array, use\n\"\\@array = \\@otherarray\". If you want to make the elements of @array aliases of the scalars\nreferenced 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 other\nhash, use \"\\%hash = \\%otherhash\". If you want to make the elements of %hash into aliases of\nthe scalars referenced on the right-hand side, use a hash slice: \"\\@hash{@keys} =\n@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 get\nthe same effect though, because the inner curlies will be considered a block that loops\nonce. 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 which\nyou 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 open()\nsyntax:\n\nopen FH, '>', $ref;\n\nbut your version of perl is compiled without perlio, and this form of open is not supported.\n\nCan't open bidirectional pipe\n(W pipe) You tried to say \"open(CMD, \"|cmd|\")\", which is not supported. You can try any of\nseveral modules in the Perl library to do this, such as IPC::Open2. Alternately, direct the\npipe's output to a file using \">\", and then read it in under a different file handle.\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 open\nthe 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 open\nthe 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 open\nthe 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 open\nthe 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 search,\nthe -S option causes perl to do that search, so you don't have to type the path or `which\n$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 \"my\n($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 current\nblock. Note that an \"if\" or \"else\" block doesn't count as a \"loopish\" block, as doesn't a\nblock given to sort(), map() or grep(). You can usually double the curlies to get the same\neffect though, because the inner curlies will be considered a block that loops once. See\n\"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 unable to\nremove the original file to replace it with the modified file. The file was left 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 to\nthe 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 have\nwrite 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. The\nonly 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 not\nsupported 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 is an\ninternal 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 called\nthe subroutine in a way that made Perl think you meant to return only one value. You\nprobably meant to write parentheses around the call to the subroutine, which tell Perl that\nthe 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 to\ndo 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. There's\na Math::Complex package that comes standard with Perl, though, if you really want to do\nthat.\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 is\nrunning. 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]\". Versions\nof perl <= 5.22.0 used to allow this syntax, but shouldn't have. This was deprecated in perl\n5.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 have\na name. Symbol tables can become anonymous for example by undefining stashes: \"undef\n%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 value.\nThis 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 disallowed.\nSee 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. The\nErrno module is expected to tie the %! hash to provide symbolic names for $! errno values.\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 same\ntime, 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. If\nyou want to see if the array is empty, just use \"if (@array) { # not empty }\" for example.\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 several\nnon-obvious circumstances, including iterators, weak references, stash names, even remaining\ntrue after \"undef %hash\". These things make \"defined %hash\" fairly useless in practice, so\nit now generates a fatal error.\n\nIf a check for non-empty is what you wanted then just put it in boolean context (see \"Scalar\nvalues\" 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 a\npackage, 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 would\nbe incredibly confusing to have variables in your program that looked like magical variables\nbut 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 group\nwith a byte-order modifier. For example you cannot force little-endianness on a type that is\ninside 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 or $b\nin the same line as the <=> or cmp operator, and the variable had earlier been declared as a\nlexical variable. Either qualify the sort variable with the package name, or rename the\nlexical 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 type\nneeded. You can use the ref() function to test the type of the reference, if need be.\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 prevent\nit happening accidentally. See \"Symbolic references\" in perlref. This can be triggered by an\n\"@\" or \"$\" in a double-quoted string immediately before interpolating a variable, for\nexample in \"user @$twitterid\", which says to treat the contents of $twitterid as an array\nreference; use a \"\\\" to have a literal \"@\" symbol followed by the contents of $twitterid:\n\"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 left\nof the brackets was an expression that didn't look like a hash or array reference, or\nanything 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 reference\nto its argument. The use of backslash to indicate a backreference to a matched substring is\nvalid only as part of a regular expression pattern. Trying to do this in ordinary Perl code\nproduces a value that prints out looking like SCALAR(0xdecaf). Use the $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 the\nerror 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 to a\ntemporary, and repeat that.\n\nCharacter following \"\\c\" must be printable ASCII\n(F) In \"\\c*X*\", *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; marked\nby <-- 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{...}\". But\nif 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 native\noperating system characters (ASCII, EBCDIC, and so on) and not for Unicode characters, so\nPerl 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 had\nprovided:\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 to\nfall 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 256),\nbut some of the characters had a higher value. Perl uses the character values modulus 256\ninstead, 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 256),\nbut some of the characters had a higher value. Perl uses the character values modulus 256\ninstead, 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 in\n%s\n(F) You defined a character name which had multiple space characters in a row. Change them\nto single spaces. Usually these names are defined in the \":alias\" import argument to \"use\ncharnames\", but they could be defined by a translator installed into $^H{charnames}. See\n\"CUSTOM ALIASES\" in charnames.\n" }, { "name": "chdir", "content": "(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 \"\\c*X*\" 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" }, { "name": "closedir", "content": "(W io) The dirhandle you tried to close is either closed or not really a dirhandle. Check\nyour control flow.\n" }, { "name": "close", "content": "(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 called.\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 to\nconvert 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 is\nlikely that languages other than Perl will NOT understand it. This code point also will not\nfit in a 32-bit word on ASCII platforms and therefore is non-portable between systems.\n\nAt one time, it was legal in some standards to have code points up to 0x7FFFFFFF, but not\nhigher, 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 at\nsome point in the future, say when machines become available that have larger than a 64-bit\nword. At that time, files containing any of these, written by an older Perl might require\nconversion 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 these\nlarge code points, they may have chosen a different representation for them than the\nUTF-8-like one that Perl has, which would mean files are not exchangeable between them and\nPerl.\n\nOn EBCDIC platforms, code points above 0x3FFFFFFF have a different representation in Perl\nv5.24 than before, so any file containing these that was written before that version will\nrequire 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. Check\nthe #! line, or manually feed your script into Perl yourself. The #! line at the top of your\nfile 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. Check\nthe #! line, or manually feed your script into Perl yourself. The #! line at the top of your\nfile 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. Check\nthe #! line, or manually feed your script into Perl yourself. The #! line at the top of your\nfile 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 generic\nmessage when none of the errors that it encountered were severe enough to halt compilation\nimmediately.\n\nComplex regular subexpression recursion limit (%d) exceeded\n(W regexp) The regular expression engine uses recursion in complex situations where\nback-tracking is required. Recursion depth is limited to 32766, or perhaps less in\narchitectures where the stack cannot grow arbitrarily. (\"Simple\" and \"medium\" situations are\nhandled without recursion and are not subject to a limit.) Try shortening the string under\nexamination; looping in Perl code (e.g. with \"while\") rather than in the regular expression\nengine; or rewriting the regular expression so that it is simpler or backtracks less. (See\nperlfaq2 for information on *Mastering Regular Expressions*.)\n" }, { "name": "connect", "content": "(W closed) You tried to do a connect on a closed socket. Did you forget to check the return\nvalue 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 type\nof reference that was expected. This usually indicates a syntax error in dereferencing the\nconstant 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 be\nmodified elsewhere, this breaks the behavior of closures, in which the subroutine captures\nthe variable itself, rather than its value, so future changes to the variable are reflected\nin the subroutine's return value.\n\nThis usage was deprecated, and as of Perl 5.32 is no longer allowed, making it possible to\nchange the behavior in the future.\n\nIf you intended for the subroutine to be eligible for inlining, then make sure the variable\nis 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 variable\nthat 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 inlining.\nSee \"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 the\nfeature, disable the warning with \"no warnings 'experimental::constattr'\", but know that in\ndoing so you are taking the risk that your code may break in a future Perl version.\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 at\nthe time that it is cloned. Named subroutines are not cloned like this, so the attribute\ndoes 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 a\nreference. 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 expression\nengine. If not the latter, report the problem to .\n\ncorrupted regexp pointers\n(P) The regular expression engine got confused by what the regular expression compiler gave\nit.\n\ncorrupted regexp program\n(P) The regular expression engine got passed a regexp program without a valid magic number.\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 constructor\non the right-hand side of \"my\", \"state\", \"our\", or \"local\". Simply suppress the warning if\nyou want to use the feature, but know that in doing so you are taking the risk of using an\nexperimental feature which may change or be removed in a future Perl version:\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 than\nit has returned. This probably indicates an infinite recursion, unless you're writing\nstrange 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 of\nthis 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 package\ndeclarations 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 \"< operator\n(F) The contents of a <> operator may not exceed the maximum size of a Perl identifier. If\nyou're just trying to glob a long list of filenames, try using the glob() operator, or put\nthe 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 perlport.\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 \"sort\"\nin perlfunc.\n\nExiting subroutine via %s\n(W exiting) You are exiting a subroutine by unconventional means, such as a goto, or a loop\ncontrol 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 character\nclass, 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. Consider\nproviding 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, or\nmanually 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 prematurely\nended.\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 another\ncharacter class like \"\\d\" or \"[:alpha:]\". The \"-\" in your false range is interpreted as a\nliteral \"-\". In a \"(?[...])\" construct, this is an error, rather than a warning. Consider\nquoting the \"-\", \"\\-\". The <-- HERE shows whereabouts in the regular expression the problem\nwas 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 something?\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 encode\nvalues above 63. So there is no point in asking for a line length bigger than that. Perl\nwill 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-write\nfilehandle, you needed to open it with \"+<\" or \"+>\" or \"+>>\" instead of with \"<\" or nothing.\nIf you intended only to write the file, use \">\" or \">>\". See \"open\" in perlfunc.\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 be\na read/write filehandle, you needed to open it with \"+<\" or \"+>\" or \"+>>\" instead of with\n\">\". If you intended only to read from the file, use \"<\". See \"open\" in perlfunc. Another\npossibility is that you attempted to open filedescriptor 0 (also known as STDIN) for output\n(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. This\noccurred 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 to\nput either the backslash or the name.\n" }, { "name": "flock", "content": "(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 call\nflock() 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 your\nfile 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 it\nknows to be a term when it was expecting to see an operator, it gives you this warning.\nUsually it indicates that an operator or delimiter was omitted, such as a semicolon.\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 forget\nto 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\" operator\nreturned an invalid UIC.\n" }, { "name": "getsockopt", "content": "(W closed) You tried to get a socket option on a closed socket. Did you forget to check the\nreturn 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 explanation\nunder \"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 must\neither be lexically scoped (using \"my\" or \"state\"), declared beforehand using \"our\", or\nexplicitly 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 to\nfail 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, make\nthem all empty (except that \"dcsh\" should be 'undef') so that Perl will think csh is\nmissing. In either case, after editing config.sh, run \"./Configure -S\" and rebuild Perl.\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 left\nsome needed parentheses out earlier in the line, and you really meant a \"less than\".\n" }, { "name": "gmtime", "content": "(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" }, { "name": "gmtime", "content": "(W overflow) You called \"gmtime\" with a number that was larger than it can reliably handle\nand \"gmtime\" probably returned the wrong date. This warning is also triggered with NaN (the\nspecial not-a-number value).\n" }, { "name": "gmtime", "content": "(W overflow) You called \"gmtime\" with a number that was smaller than it can reliably handle\nand \"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, and\nthis 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. See\n\"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 a\nnon-digit word character. A common cause of this error is using (?&0) instead of (?0). See\nperlre.\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 point\nsupports. With the IEEE 754 floating point, this may also mean that the subnormals (formerly\nknown 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 part\nbetween the 0x and the exponent, also known as the fraction or the significand) than the\nfloating point supports.\n\nHexadecimal float: precision loss\n(W overflow) The hexadecimal floating point had internally more digits than could be output.\nThis can be caused by unsupported long double formats, or by 64-bit integers not being\navailable (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 format\nare 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 characters\nfor simple names, and somewhat more for compound names (like $A::B). You've exceeded Perl's\nlimits. Future versions of Perl are likely to eliminate these arbitrary limitations.\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 digit\nother than one that is legal for the given type, such as only 0 and 1 for binary. For\noctals, this is raised only if the illegal character is an '8' or '9'. For hex, 'A' - 'F'\nand 'a' - 'f' are legal. Interpretation of the number stopped just before the offending\ndigit 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, or\none 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 standard\noptions. For some reason, your version of Perl appears to have been built without this\nsupport. 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 name\nor \"=\" etc. Perhaps you are trying use a prototype while in the scope of \"use feature\n'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 characters\nin prototypes are $, @, %, *, ;, [, ], &, \\, and +. Perhaps you were trying to write a\nsubroutine signature but didn't enable that feature first (\"use feature 'signatures'\"), so\nyour 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 need\nto 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 this\nkindly.\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 (or\n64, 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 \"\\p{}\"\nor \"\\P{}\") that Perl knows isn't an official Unicode property, and was likely meant to be a\nuser-defined property name, but it can't be one of those, as they must begin with either\n\"In\" or \"Is\". Check the spelling. See also \"Can't find Unicode property 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 number\nof 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 inside\nthe construct was completely empty, or if there are too many or few operands for the number\nof operators. Perl is not smart enough to give you a more precise indication as to what is\nwrong.\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 have\nenabled the C3 MRO for this class. See the C3 documentation in mro for more information.\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 the\nbeginning 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 1\nand 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 should\ncheck 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 depend\non the definitions of other user-defined properties. If the chain of dependencies leads back\nto this property, infinite recursion would occur, were it not for the check that raised this\nerror.\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 \"/(?{ s!!!\n})/\", which resulted in re-executing the same pattern, which is an infinite loop which is\nbroken 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. So\n\"state $a = 42\" and \"state @a = qw(a b c)\" are allowed, but not \"state ($a) = 42\" or \"(state\n$a) = 42\". To initialize more than one \"state\" variable, initialize them one at a 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 in\nthe value it returns and when evaluating its argument, while %foo[&bar] provides a list\ncontext to its subscript, which can do weird things if you're expecting only one subscript.\nWhen called in list context, it also returns the index (what &bar returns) in addition to\nthe 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 select\na single element of a hash. Generally it's better to ask for a scalar value (indicated by\n$). The difference is that $foo{&bar} always behaves like a scalar, both in the value it\nreturns and when evaluating its argument, while @foo{&bar} and provides a list context to\nits subscript, which can do weird things if you're expecting only one subscript. When called\nin list context, it also returns the key in addition to the value.\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 turn\nit 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 data\nis used in a \"dangerous\" operation, you get this error. See perlsec for more information.\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 of\n$ENV{PATH}, $ENV{IFS}, $ENV{CDPATH}, $ENV{ENV}, $ENV{BASHENV} or $ENV{TERM} are derived\nfrom data supplied (or potentially supplied) by the user. The script must set the path to a\nknown 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 a\ncall to a user-defined character property function, i.e. \"\\p{IsFoo}\" or \"\\p{InFoo}\". See\n\"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()\" are\ntoo 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 literal\nor as an argument to hex() or oct() is too big for your architecture, and has been converted\nto a floating point number. On a 32-bit architecture the largest hexadecimal, octal or\nbinary number representable without overflow is 0xFFFFFFFF, 037777777777, or\n0b11111111111111111111111111111111 respectively. Note that Perl transparently promotes all\nnumbers to a floating point representation internally--subject to loss of precision errors\nin 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 you\nexpect, because different random seeds above the maximum will return the same sequence of\nrandom 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 integers\nfor your architecture. This is not a warning because there is no rational reason for a\nversion to try and use an element larger than typically 232. This is usually caused by\ntrying 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 \"fork\"\nand \"exec\", to determine whether the current call to \"exec\" should affect the current script\nor a subprocess (see \"exec LIST\" in perlvms). Somehow, this count has become scrambled, so\nPerl is making a guess and treating this \"exec\" as a request to terminate the Perl script\nand execute the specified command.\n\ninternal %p might conflict with future printf extensions\n(S internal) Perl's internal routine that handles \"printf\" and \"sprintf\" formatting follows\na slightly different set of rules when called from C or XS code. Specifically, formats\nconsisting of digits followed by \"p\" (e.g., \"%7p\") are reserved for future use. If you see\nthis message, then an XS module tried to call that routine with one such reserved 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 should\nbe an indivisible token, with nothing intervening between the \"(\" and the \"?\", but you\nseparated 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 should\nbe an indivisible token, with nothing intervening between the \"(\" and the \"*\", but you\nseparated 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 a\nuser-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 by\na 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 \"CUSTOM\nALIASES\" 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 perlfunc.\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 a\nsingle character through the conversion from the encoding specified by the encoding pragma.\nThe escape was replaced with REPLACEMENT CHARACTER (U+FFFD) instead, except within\n\"(?[ ])\", where it is a fatal error. The <-- HERE shows whereabouts in the regular\nexpression 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. Either it\nis empty, or you tried to use a character other than 0 - 9 or A - F, a - f in a hexadecimal\nnumber.\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 not a\nvalid method resolution order (MRO). Currently, the only valid ones supported are \"dfs\" and\n\"c3\", unless you have loaded a module that is a MRO plugin. See mro and perlmroapi.\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 overflows\nperl'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 with\nno 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 as\na valid number - either it has leading zeroes, or it represents too big a number to cope\nwith. The <-- HERE shows where in the regular expression the problem was discovered. See\nperlre.\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 the\nregular 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 than\nthe 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 not\nwithin 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 attribute\nlist. If the previous attribute had a parenthesised parameter list, perhaps that list was\nterminated 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 a\nparenthesised 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 or\nelse a dotted-decimal v-string with a leading 'v' character and at least three components.\nThe parenthesized text indicates which criteria were not met. See the version module for\nmore 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 ignored.\n\nInvalid version format (%s)\n(F) A version number did not meet the \"lax\" criteria for versions. A \"lax\" version number is\na positive decimal number (integer or decimal-fraction) without exponentiation or else a\ndotted-decimal v-string. If the v-string has fewer than three components, it must have a\nleading 'v' character. Otherwise, the leading 'v' is optional. Both decimal and\ndotted-decimal versions may have a trailing \"alpha\" component separated by an underscore\ncharacter after a fractional or dotted-decimal component. The parenthesized text indicates\nwhich criteria were not met. See the version module for more details on allowed version\nformats.\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 would\nmean any sequence of characters from 0 to infinity in length that weren't these two in a\nrow, and that is likely not of any real use.)\n\n(F) The two-character sequence \"(*\" in this context in a regular expression pattern should\nbe an indivisible token, with nothing intervening between the \"(\" and the \"*\", but you\nseparated them.\n\nioctl is not implemented\n(F) Your machine apparently doesn't implement ioctl(), which is pretty strange for a machine\nthat supports C.\n" }, { "name": "ioctl", "content": "(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 call\nnor 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 valid\nones 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 it\nis forbidden. The <-- HERE shows whereabouts in the regular expression the problem was\ndiscovered. 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 that\nhave 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, ignoring\nthe actual layers. Since sysread() and recv() did no UTF-8 validation they can end up\ncreating invalidly encoded scalars.\n\nSimilarly, syswrite() and send() used only the \":utf8\" flag, otherwise ignoring any layers.\nIf the flag is set, both wrote the value UTF-8 encoded, even if the layer is some different\nencoding, such as the example above.\n\nIdeally, all of these operators would completely ignore the \":utf8\" state, working only with\nbytes, 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 longer\nsupported and is a fatal error as of Perl 5.30. In previous versions of perl the use of $*\nenabled 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 versions:\nwhen $* was set to a true value then all regular expressions behaved as if they were written\nusing \"/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 operator\nis currently experimental and its behaviour may change in future releases of Perl.\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, since\nediting STDIN in place doesn't make sense, and can be confusing because it can make perl\nlook like it is hanging when it is really just trying to read from STDIN. You should either\npass a filename to edit, or remove \"-i\" from the command line. See perlrun for 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.\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, not\neven 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 even\nif 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 even\nif 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 length.\nSee \"pack\" in perlfunc.\n" }, { "name": "length", "content": "(W syntax) You used length() on either an array or a hash when you probably wanted a count\nof 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 or\nsimilar), but tried to insert a character that couldn't be part of the current input. This\nis an inherent pitfall of the stuffing mechanism, and one of the reasons to avoid it. Where\nit 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" }, { "name": "listen", "content": "(W closed) You tried to do a listen on a closed socket. Did you forget to check the return\nvalue 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 not\nsupport pipes, such as \"open($pipe, '|-', @args)\". Use the two-argument \"open($pipe, '|prog\narg1 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 you\nreally mean to match a form-feed? If so, all the ASCII vertical space control characters are\nrepresentable by escape sequences which won't present such a jarring appearance as your\npattern 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 The\nPerl 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 from\nthe 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 from\nPerl'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 is\ndotted in both upper- and lowercase, and the other is dotless in both cases. Unicode allows\na locale to use either the Turkish rules, or the rules used in all other instances, where\nthere is only one type of \"I\", which is dotless in the uppercase, and dotted in the lower.\nThe perl core does not (yet) handle the Turkish case, and this message warns you of that.\nInstead, the Unicode::Casing module allows you to mostly implement 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 in\nthe C locale (and the POSIX standard defers to the C standard), and Unicode is generally\nconsidered a superset of the C locale. But Unicode has added an extra category, \"Symbol\",\nand classifies these particular characters as being symbols. Most UTF-8 locales have them\ntreated as punctuation, so that ispunct(2) returns non-zero for them. But a few locales have\nit return 0. Perl takes the first approach, not using \"ispunct()\" at all (see Note [5] in\nperlrecharclass), and this message is raised to notify you that you are getting Perl's\napproach, 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 reason.\n\nBy far the most common reason is that the locale has characters in it that are represented\nby more than one byte. The only such locales that Perl can handle are the UTF-8 locales.\nMost likely the specified locale is a non-UTF-8 one for an East Asian language such as\nChinese or Japanese. If the locale is a superset of ASCII, the ASCII portion of it may work\nin Perl.\n\nSome essentially obsolete locales that aren't supersets of ASCII, mainly those in ISO 646 or\nother 7-bit locales, such as ASMO 449, can also have problems, depending on what portions of\nthe ASCII character set get changed by the locale and are also used by the program. The\nwarning 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 locale\nor use Encode to translate from the locale into UTF-8; if that's impracticable, you have\nbeen 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 bad\none. It is not raised for any operations from the POSIX module.\n" }, { "name": "localtime", "content": "(W overflow) You called \"localtime\" with a number that it could not handle: too large, too\nsmall, or NaN. The returned value is \"undef\".\n" }, { "name": "localtime", "content": "(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 with\nNaN (the special not-a-number value).\n" }, { "name": "localtime", "content": "(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, the\ntarget of \"++\" or \"--\" is increased or decreased by quite different value than one, such as\nzero (*i.e.* the target is unchanged) or two, due to rounding. Perl issues this warning\nbecause it has already switched from integers to floating point when values are too large\nfor integers, and now even floating point is insufficient. You may wish to switch to using\nMath::BigInt explicitly.\n" }, { "name": "lstat", "content": "(W io) You tried to do an lstat on a filehandle. What did you mean by that? lstat() makes\nsense 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 do\nwhat you want, depending on what code is inside the subroutine, with exact details subject\nto change between Perl versions. Only do this if you really know what you are doing.\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 prefix1 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, or\nare 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 characters. A\nmore rigorous check is run when the function is called. Perhaps the function's author was\ntrying to write a subroutine signature but didn't enable that feature first (\"use feature\n'signatures'\"), so the signature was instead interpreted as a bad 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 the\nword size of the current platform (overflows). Details as to the exact malformation are\ngiven 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 in\nUTF-8 but it wasn't (it was for example legacy 8-bit data). To guard against this, you can\nuse \"Encode::decode('UTF-8', ...)\".\n\nIf you use the \":encoding(UTF-8)\" PerlIO layer for input, invalid byte sequences are handled\ngracefully, but if you use \":utf8\", the flag is set without validating the data, possibly\nresulting 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 trying\nto find out if a character, allegedly stored internally encoded as UTF-8, was of a given\ntype, such as being punctuation or a digit. But the character was not encoded in legal\nUTF-8. The %s is replaced by a string that can be used by knowledgeable people to determine\nwhat 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 was\nunable 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 was\nunable 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 a\nmalformed Unicode surrogate.\n\nMandatory parameter follows optional parameter\n(F) In a subroutine signature, you wrote something like \"$a = undef, $b\", making an earlier\nparameter optional and a later one mandatory. Parameters are filled from left to right, so\nit's impossible for the caller to omit an earlier one and pass a later one. If you want to\nact as if the parameters are filled from right to left, declare the rightmost optional and\nthen 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 code\npoint may be as large as what is storable in a signed integer on your system, but these may\nnot be accepted by other languages/systems. This message occurs when you matched a string\ncontaining such a code point against a regular expression pattern, and the code point was\nmatched against a Unicode property, \"\\p{...}\" or \"\\P{...}\". Unicode properties are only\ndefined on Unicode code points, so the result of this match is undefined by Unicode, but\nPerl (starting in v5.20) treats non-Unicode code points as if they were typical unassigned\nUnicode ones, and matched this one accordingly. Whether a given property matches these code\npoints or not is specified in \"Properties accessible through \\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 other\ncode points, Unicode or not, won't match it. (And \"\\P{ASCIIHexDigit}\" will match every\ncode point except these 22.)\n\nGetting this message indicates that the outcome of the match arguably should have been the\nopposite of what actually happened. If you think that is the case, you may wish to make the\n\"nonunicode\" warnings category fatal; if you agree with Perl's decision, you may wish to\nturn 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 expression\nengine didn't specifically check for that. The <-- HERE shows whereabouts in the regular\nexpression 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 that\nyour 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 process\nsignals 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 loses\ninformation, 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 to\na 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 line.\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 supplied,\nbut might be used in the future for other cases where we can statically determine that\narguments to functions are missing, e.g. for the \"pack\" in perlfunc function.\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 brace\nimmediately 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\" before\nthe 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, but\nthe 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 with\nthe $ 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; do\nexpects 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 (or\nsequence of characters) given by that name. Thus \"\\N{ASTERISK}\" is another way of writing\n\"*\", valid in both double-quoted strings and regular expression patterns. In patterns, it\ndoesn't have the meaning an unescaped \"*\" does.\n\nStarting in Perl 5.12.0, \"\\N\" also can have an additional meaning (only) in patterns, namely\nto match a non-newline character. (This is short for \"[^\\n]\", and like \".\" but is not\naffected by the \"/s\" regex modifier.)\n\nThis can lead to some ambiguities. When \"\\N\" is not followed immediately by a left brace,\nPerl assumes the \"[^\\n]\" meaning. Also, if the braces form a valid quantifier such as\n\"\\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, where\nthere 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 if\n\"[^\\n]{\" was desired, and raises this error. If you meant the former, add the right brace;\nif 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 general\nrule, 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 because\nyou 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 thing\nis:\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\nin the 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\nread-only 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 probably\nnegative, 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 name\nof 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 are\ntrying to open a pipe to a command that takes a list of arguments, but have forgotten to\nspecify 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), but\na 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), but\na 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 op\ntree 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 named\nsequence by definition is more than an individual character, and hence doing this operation\non 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 $b\nin as an operand to the \"<=>\" or \"cmp\" operator inside a sort comparison block, and the\nvariable had earlier been declared as a lexical variable. Either qualify the sort variable\nwith 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 message.\nThe \"our\" declaration is also provided for this purpose.\n\nNOTE: This warning detects package symbols that have been used only once. This means lexical\nvariables will never trigger this warning. It also means that all of the package variables\n$c, @c, %c, as well as *c, &c, sub c{}, c(), and c (the filehandle or format) are considered\nthe same; if a program uses $c only once but also uses any of the others it will not trigger\nthis warning. Symbols beginning with an underscore and symbols using special identifiers\n(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 long.\nThis helps catch some ambiguities. If your constant is too short, add leading zeros, 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 need\nto 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 \"pack\"\nin perlfunc.\n\nNegative length\n(F) You tried to do a read/write/send/recv operation with a buffer length that is less than\n0. 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 or\nequal 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 or +*\nor ?* are illegal. The <-- HERE shows whereabouts in the regular expression the problem was\ndiscovered.\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 package,\nand 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 m/%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: it\nmatches 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. Even\nthough a character class is supposed to match just one character of input, perl will match\nthe 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 the\nend 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, so\nthis is made an error.\n\nIn a regex set\nThe syntax \"(?[ ])\" in a regular expression yields a list of single code points, none\ncan 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 even\nbe allowed to attempt. Generally speaking there will be another way to do what you want that\nis, 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 empty\nprogram, pass the empty string as a separate argument or run a program consisting of a\nsingle 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 the\narguments.\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 your\noperating system does not support that particular constant. Hopefully you did use an\nexplicit import list for the constants you expect to see; please see \"use\" in perlfunc and\n\"import\" in perlfunc. While an explicit import list would probably have caught this error\nearlier it naturally does not remedy the fact that your operating system still does not\nsupport that constant. Maybe you have a typo in the constants of the symbol import list of\nuse 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 '|'\nat the end of the command line, so it doesn't know where you want to pipe the output from\nthis 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 nowadays,\nbecause 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\" routine\nto 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 following\n\"0b\".\n\nNo directory specified for -I\n(F) The -I command-line switch requires a directory name as part of the *same* argument. Use\n-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 write\ndata 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 '<'\non the command line, but can't find the name of the file from which to read data for stdin.\n\nNo next::method '%s' found for %s\n(F) \"next::method\" found no further instances of this method name in the remaining packages\nof 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 the\nending 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 tell\nPerl that this is indeed what you want, you can use the \"\\o{ }\" syntax, or use exactly three\ndigits to specify the octal for the character.\n\nNote that, within braces, every character starting with the first non-octal up to the ending\nbrace 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() function\nto 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 '>'\nor a '>>' on the command line, but can't find the name of the file to which to write data\ndestined 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 containing\nthe 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 class\ndoesn'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 key\nis not allowed by the package of the same type. The indicated package has restricted the set\nof 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 which\nhadn't been opened. This should have been caught earlier as an attempt to close an unopened\nfilehandle.\n\nNo such signal: SIG%s\n(W signal) You specified a signal name as a subscript to %SIG that was not recognized. Say\n\"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 property\nvalue 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 what\nkind 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 entry\nthat looks like *foo), but found a reference to something else instead. You can use the\nref() 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 with\nthe $# 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 what\nkind 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 perlform.\n\n%s: not found\n(A) You've accidentally run your script through the Bourne shell instead of Perl. Check the\n#! 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 it's\nassuming that local system time is equivalent to UTC. If it's not, define the logical name\nSYS$TIMEZONEDIFFERENTIAL to translate to the number of seconds which need to be added to\nUTC 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 characters.\nYou've exceeded that length. Future versions of Perl are likely to eliminate this arbitrary\nlimitation. In the meantime, try using scientific notation (e.g. \"1e6\" instead of\n\"1000000\").\n\nNumber with no digits\n(F) Perl was looking for a number but found nothing that looked like a number. This happens,\nfor 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 2GB.\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 a\nvariable that starts with 0 that has more than one digit. You probably want to remove the\nleading 0, or if the intent was to express a variable name in octal you should convert to\ndecimal.\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 number\nof 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, because\nhashes 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, because\nhashes 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 pointing\noutside the buffer. This is difficult to imagine. The sole exceptions to this are that zero\npadding will take place when going past the end of the string when either \"sysread()\"ing a\nfile, or when seeking past the end of a scalar opened for I/O (in anticipation of future\nreads 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\ndouble-quoted string; e.g., \"In $name's house\". This is equivalent to \"In $name::s house\".\nIf you 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. You\nneed 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. Check\nyour 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 defined.\nWhile some handlers can be autogenerated in terms of other handlers, there is no default\nhandler for any operation, unless the \"fallback\" overloading key is specified to be true.\nSee 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 is\nnot in Unicode, so what it should do is not defined. Perl has chosen to have it do nothing,\nand 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 '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 you\nsaid \"*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 = undef\".\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 (or\nvirtual 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 -a\"\nand \"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 possible\nmemory allocation.\n\nOut of memory during \"large\" request for %s\n(F) The malloc() function returned 0, indicating there was insufficient remaining memory (or\nvirtual 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 memory\n(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 use\nthe contents of $^M as an emergency pool after die()ing with this message. In this case the\nerror is trappable *once*, and the error message will include the line and file where the\nfailed 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 be\ncaused 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 the\nstart 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 overloaded\noperation 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 operation\ndidn'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. That\nname might have a meaning to Perl itself some day, even though it doesn't yet. Perhaps you\nshould 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. See\n\"pack\" in perlfunc.\n\npage overflow\n(W io) A single call to write() produced more lines than can fit on a page. See perlform.\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-function,\nbut that function is not available on this platform. Earlier checks mean that it should not\nbe 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 caught.\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 discovered\nit 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 time\nsomething re-created entries in the glob. Most likely the glob contains an object with a\nreference 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 top\nof 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 target\nthat 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 than\n1.\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 couldn't\nlocate the code block that should have already been seen and compiled by perl before control\npassed 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 time.\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 Perl\nthan 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 bug\nin Perl in which the built-in regular expression folding rules are not accurate. This may\nlead to incorrect results. Please report this as a bug to\n.\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 to\nset up some or all fixed-width byte-order conversion functions. This is only a problem when\nyou're using the '<' or '>' modifiers in (un)pack templates. See \"pack\" in perlfunc.\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 the\nleading \"v\", the number is interpreted as a decimal, with every three digits after the\ndecimal point representing a part of the version number. So 5.10 is equivalent to v5.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 currently\nrunning version. How long has it been since you upgraded, anyway? See \"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. See\n\"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 wrong\nand 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 the\nLCALL was \"EnUS\" and the LANG had no value. This error means that Perl detected that you\nand/or your operating system supplier and/or system administrator have set up the so-called\nlocale system but Perl could not use those settings. This was not dead serious, fortunately:\nthere is a \"default locale\" called \"C\" that Perl can and will use, and the script will be\nrun. Before you really fix the problem, however, you will get the same error message each\ntime you run Perl. How to really fix the problem can be found in perllocale section LOCALE\nPROBLEMS.\n\nperl: warning: strange setting in '$ENV{PERLPERTURBKEYS}': '%s'\n(S) Perl was run with the environment variable PERLPERTURBKEYS defined but containing an\nunexpected 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 sensitive.\nThe 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 isn't a\nsubprocess of the current process. While this is fine from VMS' perspective, it's probably\nnot 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 whereabouts\nin the regular expression the problem was discovered. Note that the POSIX character classes\ndo not have the \"is\" prefix the corresponding C interfaces have: in other words, it's\n\"[[: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, which\ntakes 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* character\nclasses, the [] are part of the construct, for example: \"qr/[012[:alpha:]345]/\". What the\nregular expression pattern compiled to is probably not what you were intending. For example,\n\"qr/[:alpha:]/\" compiles to a regular bracketed character class consisting of the four\ncharacters \":\", \"a\", \"l\", \"h\", and \"p\". To specify the POSIX class, it should have been\nwritten \"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 regular\nexpression 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 character\nsequences inside a regular expression character class, just quote the square brackets with\nthe backslash: \"\\[.\" and \".\\]\". The <-- HERE shows whereabouts in the regular expression the\nproblem 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 character\nsequences inside a regular expression character class, just quote the square brackets with\nthe backslash: \"\\[=\" and \"=\\]\". The <-- HERE shows whereabouts in the regular expression the\nproblem 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 commas:\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 to\nseparate the items. (You may have used different delimiters than the parentheses shown here;\nbraces 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 don't\nwant 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. This\nsentinel byte got clobbered, and Perl assumes that memory is now corrupted. See \"ioctl\" in\nperlfunc.\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 of\n\"==\". This is probably not what you want. (If you really meant to write this, disable the\nwarning, or, better, put the parentheses explicitly and write \"$x & ($y == 0)\").\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) and\nthe 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. (The\nold open was a little of both.) You must put parentheses around the filehandle, or use the\nnew \"or\" operator instead of \"||\".\n\nPremature end of script headers\nSee \"500 Server error\".\n" }, { "name": "printf", "content": "(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. Check\nyour control flow.\n\nProcess terminated by SIG%s\n(W) This is a standard message issued by OS/2 applications, while *nix applications die in\nsilence. 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 @\ngobble 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 replaced\nby 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 to\nmatch 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 sense,\nsuch as on a zero-width assertion. Try putting the quantifier inside the assertion instead.\nFor example, the way to match \"abc\" provided that it is followed by three repetitions of\n\"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 range\nwhich can be represented by integers internally. One possible workaround is to force Perl to\nuse 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 by\n<-- 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 range\nhere, if the \"-\" was meant to be some other character, or should have been escaped (like\n\"\\-\"). If you did intend a range, the one that was used is not portable between ASCII and\nEBCDIC 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 are\nspecified by \"\\N{...}\", but the meaning may still not be obvious.) The stricter rules\nrequire that ranges that start or stop with an ASCII character that is not a control have\nall their endpoints be the literal character, and not some escape sequence (like \"\\x41\"),\nand the ranges must be all digits, or all uppercase letters, or all lowercase 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 one\nof the end points is a decimal digit. Under the stricter rules, when this happens, both end\npoints should be digits in the same group of 10 consecutive digits.\n" }, { "name": "readdir", "content": "(W io) The dirhandle you're reading from is either closed or not really a dirhandle. Check\nyour control flow.\n" }, { "name": "readline", "content": "(W closed) The filehandle you're reading from got itself closed sometime before now. Check\nyour control flow.\n" }, { "name": "readline", "content": "(W unopened) The filehandle you're reading from was never opened. Check your control flow.\n" }, { "name": "read", "content": "(W closed) You tried to read from a closed filehandle.\n" }, { "name": "read", "content": "(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" }, { "name": "realloc", "content": "(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 is\ncompiled into Perl, which entails some overhead, which is why it's currently left out of\nyour copy.\n\nRecursive call to Perlloadmodule in PerlIOfindlayer\n(P) It is currently not permitted to load modules when creating a filehandle inside an %INC\nhook. 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 found\nan infinite loop in the @ISA hierarchy. This is a crude check that bails out after 100\nlevels 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 fewer\narguments than were supplied, but might be used in the future for e.g. \"pack\" in perlfunc.\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 message,\nsomething 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 of\nelements (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 character\nwith ordinal 7 inserted into the regular expression, prepend zeroes to make it three digits\nlong: \"\\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\" in your regular expression, but there\nis no corresponding named capturing parentheses such as \"(?'NAME'...)\" or \"(?...)\".\nCheck if the name has been spelled correctly both in the backreference and 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 least\nseven sets of closed capturing parentheses in the expression before where the \"\\g{-7}\" was\nlocated.\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 gave\nit.\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 to\nturn 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 modifiers.\nRetain 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 that\nyou 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 '%c'\nterminates \\o early. Resolved as \"%s\"\". (W misc, regexp) You wrote something like \"\\08\", or\n\"\\179\" in a double-quotish string. All but the last digit is treated as a single character,\nspecified in octal. The last digit is the next character in the string. To tell Perl that\nthis is indeed what you want, you can use the \"\\o{ }\" syntax, or use exactly three digits to\nspecify 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" }, { "name": "rewinddir", "content": "(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 scalar\nvariables were deallocated by the time Perl exited. What this usually indicates is a memory\nleak, which is of course bad, especially if the Perl program is intended to be 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 is\nthat $foo[&bar] always behaves like a scalar, both when assigning to it and when evaluating\nits argument, while @foo[&bar] behaves like a list when you assign to it, and provides a\nlist context to its subscript, which can do weird things if you're expecting only one\nsubscript.\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 hash.\nGenerally it's better to ask for a scalar value (indicated by $). The difference is that\n$foo{&bar} always behaves like a scalar, both when assigning to it and when evaluating its\nargument, while @foo{&bar} behaves like a list when you assign to it, and provides a list\ncontext to its subscript, which can do weird things if you're expecting only one subscript.\n\nOn the other hand, if you were actually hoping to treat the hash element as a list, you need\nto look into how references work, because Perl will not magically convert between scalars\nand 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 may\ncause 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\n*defined-or* can be misparsed by pre-5.10.0 Perls as a non-terminated search pattern.\n" }, { "name": "seekdir", "content": "(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 possibly\nsome 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" }, { "name": "send", "content": "(W closed) The socket you're sending to got itself closed sometime before now. Check your\ncontrol 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 ASCII\nones). If you were intending to specify a control character with this sequence, you'll have\nto 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 been\nwritten. 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 using\nthe \"(?^...)\" construct to tell Perl to use the default regular expression modifiers, and\nyou 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 after\nthe 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 quote\nor angle bracket. 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 reference of the form \"(?('...')...)\" or \"(?(<...>)...)\" was missing the final\nclosing quote or angle bracket after the name. The <-- HERE shows whereabouts in the regular\nexpression 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 whereabouts in\nthe 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 after\nthe 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. The\n<-- 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 after\nthe 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 parenthesis.\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) not\npermitted\", \"Document contains no data\", \"Premature end of script headers\", and \"Did not\nproduce 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 rely\non any environment variables (like PATH) from the user it isn't running under, and isn't in\na location where the CGI server can't find it, basically, more or less. Please see the\nfollowing 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" }, { "name": "setegid", "content": "(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" }, { "name": "seteuid", "content": "(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" }, { "name": "setrgid", "content": "(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" }, { "name": "setruid", "content": "(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" }, { "name": "setsockopt", "content": "(W closed) You tried to set a socket option on a closed socket. Did you forget to check the\nreturn 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 positive\ninteger. In older perls this appeared to work the same as setting it to \"undef\" but was in\nfact internally different, less efficient and with very bad luck could have resulted in your\nfile 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 undef,\nwith 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 slurp\nthe file. As of Perl 5.28 assigning $/ to a reference to an integer which isn't positive is\na 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 have\nbehaved similarly to setting it to a reference to a positive integer, where the integer was\nthe address of the reference. As of Perl 5.20.0 this is a fatal error, to allow future\nversions 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 against\n$ as the string, which is probably not what you had in mind.\n" }, { "name": "shutdown", "content": "(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 into\nthe wrong package?\n\nSlab leaked from cv %p\n(S) If you see this message, then something is seriously wrong with the internal bookkeeping\nof op trees. An op tree needed to be freed after a compilation error, but could not be\nfound, so it was leaked instead.\n" }, { "name": "sleep", "content": "(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) parameter.\nThe slurpy parameter takes all the available arguments, so there can't be any left to fill\nlater 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 change\nin future releases of Perl. Particularly, its current behavior is noticed for being\nunnecessarily 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 it\nneeds at least 2 gigabytes to store. Unfortunately, Perl doesn't yet handle such large hash\nkeys. You should reconsider your design to avoid hashing such a long string directly.\n\nsort is now a reserved word\n(F) An ancient error message that almost nobody ever runs into anymore. But before sort was\na 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) within\na string passed to \"eval\". This is not permitted under the \"unicodeeval\" feature. Consider\nusing \"evalbytes\" instead. See feature.\n" }, { "name": "splice", "content": "(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. If\nthis 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 than\nthere 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 almost\nalways an error, because exec() never returns unless there was a failure. You probably\nwanted to use system() instead, which does return. To suppress this warning, put the exec()\nin 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 $b\nin as an operand to the \"<=>\" or \"cmp\" operator inside a sort comparison block, and the\nvariable had earlier been declared as a lexical variable. Either qualify the sort variable\nwith 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" }, { "name": "stat", "content": "(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 contain\nbytes.\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 should\nnever 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 the\nsignature. 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 capture\nan outer lexical subroutine that is not currently available. This can happen for one of two\nreasons. First, the lexical subroutine 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 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 the\nanonymous 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 out\nof 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, so\nits &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 the\nend 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 in\nan outer named subroutine.\n\nWhen the inner subroutine is called, it will see the value of the outer subroutine's lexical\nsubroutine 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 lexical subroutine. In other words,\nit will no longer be shared. This will especially make a difference if the lexical\nsubroutines accesses lexical variables declared in its surrounding scope.\n\nThis problem can usually be solved by making the inner subroutine anonymous, using the \"sub\n{}\" 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 iterate\nmore times than there are characters of input, which is what happened.) See the discussion\nof 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. Remember\nthat bracketing delimiters count nesting level. Missing the leading \"$\" from variable $s may\ncause this error.\n\nSubstitution replacement not terminated\n(F) The lexer couldn't find the final delimiter of an s/// or s{}{} construct. Remember that\nbracketing delimiters count nesting level. Missing the leading \"$\" from variable $s may\ncause this error.\n\nsubstr outside of string\n(W substr)(F) You tried to reference a substr() that pointed outside of a string. That is,\nthe absolute value of the offset was larger than the length of the string. See \"substr\" in\nperlfunc. This warning is fatal if substr is used in an lvalue context (as the left hand\nside 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. The\ncondition must be one of the following:\n\n(1) (2) ... true if 1st, 2nd, etc., capture matched\n() ('NAME') true if named capture matched\n(?=...) (?<=...) true if subpattern matches\n(?!...) (?\",\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 didn't\nexplicitly 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, and\nsomeone else stuck a message in the stream of data Perl expected. Someone's very confused,\nor 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 between\nthe 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 was\nmeant 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. The\ncondition must be one of the following:\n\n(1) (2) ... true if 1st, 2nd, etc., capture matched\n() ('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\" switch\nfor 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\" switch\nfor 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 in\nyour 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 whereabouts\nin 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 a vi\nuser, the % key is valuable for finding the matching parenthesis. The <-- HERE shows\nwhereabouts 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 one\n(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 best\nto put such a word in quotes, or capitalize it somehow, or insert an underbar into it. You\nmight 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 script\n(or eval) near the specified column. Perhaps you tried to run a compressed script, a binary\nprogram, 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\nUnrecognized escape \\%c in character class 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 inside\ncharacter classes. The character was understood literally, but this may change in a future\nversion of Perl. The <-- HERE shows whereabouts in the regular expression the escape was\ndiscovered.\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. The\ncharacter(s) were understood literally, but this may change in a future version of Perl. The\n<-- HERE shows whereabouts in the regular expression the escape was discovered.\n\nUnrecognized signal name \"%s\"\n(F) You specified a signal name to the kill() function that was not recognized. Say \"kill\n-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() it\noff. 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, Configure\ndoesn'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 executables,\nsome of which may support fork, some not. Try changing the name you call Perl by to \"perl\",\n\"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 in\na 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 attribute,\nand it wasn't a semicolon or the start of a block. Perhaps you terminated the parameter list\nof 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 list,\nbut the matching closing (right) parenthesis character was not found. You may need to add\n(or remove) a backslash character to get your parentheses to balance. See attributes.\n\nUnterminated compressed integer\n(F) An argument to unpack(\"w\",...) was incompatible with the BER compressed integer format\nand 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 be\nfollowed 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 left\nsome 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 \")\".\nFix 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 \"untie\"\nwas called.\n\nUsage: POSIX::%s(%s)\n(F) You called a POSIX function with incorrect arguments. See \"FUNCTIONS\" in POSIX for more\ninformation.\n\nUsage: Win32::%s(%s)\n(F) You called a Win32 function with incorrect arguments. See Win32 for more information.\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 Perl\nversion 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 it.\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 left\nfor 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 side\nof a scalar comma operator. Very often this points not to stupidity on your part, but a\nfailure of Perl to parse your program the way you thought it would. For example, you'd get\nthis 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 you\nshould 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 do\nnot. So when a parenthesized list is evaluated in a scalar context, the comma is treated\nlike C's comma operator, which throws away the left argument, which is not what you want.\nSee perlref for more on this.\n\nThis warning will not be issued for numerical constants equal to 0 or 1 since they are often\nused 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 array,\nlike \"push(@x)\" or \"unshift(@foo)\". That won't usually have any effect on the array, so is\ncompletely useless. It's possible in principle that push(@tiedarray) could have some effect\nif the array is tied to a class which implements a PUSH method. If so, you can write it as\n\"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 line\nas 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 5.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 <-- HERE\nin m/%s/\n(F) You used a code point that is not allowed, because it is too large. Unicode only allows\ncode points up to 0x10FFFF, but Perl allows much larger ones. Earlier versions of Perl\nallowed code points above IVMAX (0x7FFFFFF on 32-bit platforms, 0x7FFFFFFFFFFFFFFF on\n64-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 in\nPerl 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\" (applying\nan empty attribute list to $x). This construct was deprecated in 5.12.0, and has now been\nmade a syntax error, so \":=\" can be reclaimed as a new operator in the future.\n\nIf you need an empty attribute list, for example in a code generator, add a space before the\n\"=\".\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 current\nlocale isn't. This doesn't make sense. Perl will continue, assuming a Unicode (UTF-8)\nlocale, 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 caused\nby 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 items,\nhence deleting such an item in the middle of an iteration causes Perl to see a freed 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 removed\nfrom the Standard, at which time Perl will follow along. In the meantime, this message is\nraised 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 functions\n(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 usually\nmeans 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 <-- HERE\nin 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 in\nsuch 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 went\npast any symlink you are presumably trying to look for. The operation returned \"undef\". Use\na 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 mean,\nbecause references in numerical context tend to be huge numbers, and so usually indicates\nprogrammer error.\n\nIf you really do mean it, explicitly numify your reference, like so: $array[0+$ref]. This\nwarning is not given for overloaded objects, however, because you can overload the\nnumification and stringification operators and then you presumably know what you are doing.\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 operands\nas 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 and\nat least one of them is tainted. This used to be allowed but will become a fatal error in a\nfuture 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\" and\nan accent, like a circumflex \"^\", that appear when displayed to be a single character with\nthe circumflex hovering over the \"R\". Perl currently allows things like that circumflex to\nbe delimiters of strings, patterns, *etc*. When displayed, the circumflex would look like it\nbelongs to the character just to the left of it. In order to move the language to be able to\naccept graphemes as delimiters, we cannot allow the use of delimiters which aren't graphemes\nby themselves. Also, a delimiter must already be assigned (or known to be never going to be\nassigned) to try to future-proof code, for otherwise code that works today would fail to\ncompile if the currently unassigned delimiter ends up being something that isn't a\nstand-alone grapheme. Because Unicode is never going to assign non-character code points,\nnor code points that are above the legal Unicode maximum, those can be delimiters, and their\nuse 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 a\ndefined 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 you\nwhat operation you used the undefined value in. Note, however, that perl optimizes your\nprogram and the operation displayed in the warning may not necessarily appear literally in\nyour program. For example, \"that $foo\" is usually optimized into \"\"that \" . $foo\", and the\nwarning will refer to the \"concatenation (.)\" operator, even though there is no \".\" in your\nprogram.\n\n\"use re 'strict'\" is experimental\n(S experimental::restrict) The things that are different when a regular expression pattern\nis compiled under 'strict' are subject to change in future Perl releases in incompatible\nways. This means that a pattern that compiles today may not in a future Perl release. This\nwarning 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 <-- HERE\nin 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 input,\nperl will match the whole thing correctly, except when the class is inverted (\"[^...]\"), or\nthe escape is the beginning or final end point of a range. For these, what should happen\nisn't clear at all. In these circumstances, Perl discards all but the first character of the\nreturned 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 more\nthan one character. These are removed from the results of the expansion of the \"\\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 is\nactually two characters. The above expression with match only the Unicode names containing\nKATAKANA 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 of\nUnicode. 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 Unicode\nonly for UTF-16. However, Perl internally allows all unsigned integer code points (up to the\nsize limit available on your platform), including surrogates. But these can cause problems\nwhen being input or output, which is likely where this message came from. If you really\nreally know what you are doing you can turn off this warning by \"no warnings 'surrogate';\".\n\nValue of %s can be \"0\"; test with defined()\n(W misc) In a conditional expression, you used , <*> (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. When\nusing these constructs in conditional expressions, test their values with the \"defined\"\noperator.\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 a\nCLI symbol table, and found a resultant string longer than 1024 characters. The return value\nhas 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 capture\nan outer lexical that is not currently available. This can happen for one of two reasons.\nFirst, the outer lexical may be declared in an outer anonymous subroutine that has not yet\nbeen created. (Remember that named subs are created at compile time, while anonymous subs\nare 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 anonymous\nsubroutine hasn't been created yet. Conversely, the following won't give a warning since the\nanonymous 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 scope,\nfor 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, so\nits $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 apparently\nthought was imported from another module, because something else of the same name (usually a\nsubroutine) is exported by that module. It usually means you put the wrong funny character\non the front of your variable. It is also possible you used an \"our\" variable whose scope\nhas 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 document\nas 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 perlre.\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 the\nsingle character LATIN SMALL LETTER SHARP S. Here's a complete list of the current ones\naffecting 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(? '/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 end\nof 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, or\nmanually 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 case,\nafter the first call to the outer subroutine is complete, the inner and outer subroutines\nwill no longer share a common value for the variable. In other words, the variable will no\nlonger be shared.\n\nThis problem can usually be solved by making the inner subroutine anonymous, using the \"sub\n{}\" syntax. When inner anonymous subs that reference variables in outer subroutines are\ncreated, 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 you\nare 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 check\nthat you are using the right verb.\n\nVersion control conflict marker\n(F) The parser found a line starting with \"<<<<<<<\", \">>>>>>>\", or \"=======\". These may be\nleft 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 \"BEGIN\"\nblock 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 ignored.\n\nWarning: something's wrong\n(W) You passed warn() an empty string (the equivalent of \"warn \"\"\") or you called it with no\nargs 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 reference\ncount 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 instance, if\nyou 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 explanation\nunder \"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 warning\nis 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 \":utf8\"\nlayer, *e.g.*, \"binmode STDOUT, ':utf8'\". Another way to turn off the warning is to add\n\"no warnings 'utf8';\" but that is often closer to cheating. In general, you are supposed to\nexplicitly mark the filehandle with an encoding, see open and \"binmode\" in perlfunc.\n\nIf the warning comes from other than I/O, this diagnostic probably indicates that incorrect\nresults are being obtained. You should examine your code to determine how a wide character\nis 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 will\nhave two different representations. For example, in the ISO 8859-7 (Greek) locale, the code\npoint 0xC3 represents a Capital Gamma. But so also does 0x393. This will make string\ncomparisons 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 in\n@%s::ISA (perhaps you forgot to load \"%s\"?)\n(W syntax) It is possible that the @ISA contains a misspelled or never loaded package name,\nwhich can result in perl choosing an unexpected parent class's method to resolve the method\ncall. 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 the\npackage 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 the\noperation is not done.\n" }, { "name": "write", "content": "(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 of\nthe 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 string\nbeing 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 kernel,\nand your vendor probably doesn't give a rip about what you want. There is a vulnerability\nanywhere that you have a set-id script, and to close it you need to remove the set-id bit\nfrom the script that you're attempting to run. To actually run the script set-id, your best\nbet 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 have\na subroutine of that name declared, which means that Perl 5 will try to call the subroutine\nwhen the assignment is executed, which is probably not what you want. (If it IS what you\nwant, 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 randomness\nout 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 an\nescape was used in an extended character class, i.e. \"(?[...])\", or under \"use re 'strict'\",\nwhich is not permitted. Check that the correct escape has been used, and the correct\ncharnames handler is in scope. The <-- HERE shows whereabouts in the regular expression the\nproblem was discovered.\n" } ] }, "SEE ALSO": { "content": "warnings, diagnostics.\n", "subsections": [] } } } }