Cari di Perl 
    Perl Tutorial
Daftar Isi
(Sebelumnya) Perl POD style guideWarning, lexical warnings warning (Berikutnya)
Language Reference

Various Perl diagnostics

Daftar Isi

NAME

perldiag - various Perl diagnostics

DESCRIPTION

These messages are classified as follows (listed in increasing order ofdesperation):

  1. (W) A warning (optional).
  2. (D) A deprecation (enabled by default).
  3. (S) A severe warning (enabled by default).
  4. (F) A fatal error (trappable).
  5. (P) An internal error you should never see (trappable).
  6. (X) A very fatal error (nontrappable).
  7. (A) An alien error message (not generated by Perl).

The majority of messages from the first three classifications above(W, D & S) can be controlled using the warnings pragma.

If a message can be controlled by the warnings pragma, its warningcategory is included with the classification letter in the descriptionbelow.

Optional warnings are enabled by using the warnings pragma or the -wand -W switches. Warnings may be captured by setting $SIG{__WARN__}to a reference to a routine that will be called on each warning insteadof printing it. See perlvar.

Severe warnings are always enabled, unless they are explicitly disabledwith the warnings pragma or the -X switch.

Trappable errors may be trapped using the eval operator. Seeeval. In almost all cases, warnings may be selectivelydisabled or promoted to fatal errors using the warnings pragma.See warnings.

The messages are in alphabetical order, without regard to upper orlower-case. Some of these messages are generic. Spots that vary aredenoted with a %s or other printf-style escape. These escapes areignored by the alphabetical order, as are all characters other thanletters. To look up your message, just ignore anything that is not aletter.

  • accept() on closed socket %s

    (W closed) You tried to do an accept on a closed socket. Did you forgetto check the return value of your socket() call? Seeaccept.

  • Allocation too large: %x

    (X) You can't allocate more than 64K on an MS-DOS machine.

  • '%c' allowed only after types %s

    (F) The modifiers '!', '<' and '>' are allowed in pack() or unpack() onlyafter certain types. See pack.

  • Ambiguous call resolved as CORE::%s(), qualify as such or use &

    (W ambiguous) A subroutine you have declared has the same name as a Perlkeyword, and you have used the name without qualification for callingone or the other. Perl decided to call the builtin because thesubroutine is not imported.

    To force interpretation as a subroutine call, either put an ampersandbefore the subroutine name, or qualify the name with its package.Alternatively, you can import the subroutine (or pretend that it'simported with the use subs pragma).

    To silently interpret it as the Perl operator, use the CORE:: prefixon the operator (e.g. CORE::log($x)) or declare the subroutineto be an object method (see Subroutine Attributes in perlsub orattributes).

  • Ambiguous range in transliteration operator

    (F) You wrote something like tr/a-z-0// which doesn't mean anything atall. To include a - character in a transliteration, put it eitherfirst or last. (In the past, tr/a-z-0// was synonymous withtr/a-y//, which was probably not what you would have expected.)

  • Ambiguous use of %s resolved as %s

    (W ambiguous)(S) You said something that may not be interpreted the wayyou thought. Normally it's pretty easy to disambiguate it by supplyinga missing quote, operator, parenthesis pair or declaration.

  • Ambiguous use of %c resolved as operator %c

    (W ambiguous) %, &, and * are both infix operators (modulus,bitwise and, and multiplication) and initial special characters(denoting hashes, subroutines and typeglobs), and you said somethinglike *foo * foo that might be interpreted as either of them. Weassumed you meant the infix operator, but please try to make it moreclear -- in the example given, you might write *foo * foo() if youreally meant to multiply a glob by the result of calling a function.

  • Ambiguous use of %c{%s} resolved to %c%s

    (W ambiguous) You wrote something like @{foo}, which might beasking for the variable @foo, or it might be calling a functionnamed foo, and dereferencing it as an array reference. If you wantedthe variable, you can just write @foo. If you wanted to call thefunction, write @{foo()} ... or you could just not have a variableand a function with the same name, and save yourself a lot of trouble.

  • Ambiguous use of %c{%s[...]} resolved to %c%s[...]
  • Ambiguous use of %c{%s{...}} resolved to %c%s{...}

    (W ambiguous) You wrote something like ${foo[2]} (where foo representsthe name of a Perl keyword), which might be looking for element number2 of the array named @foo, in which case please write $foo[2], or youmight have meant to pass an anonymous arrayref to the function namedfoo, and then do a scalar deref on the value it returns. If you meantthat, write ${foo([2])}.

    In regular expressions, the ${foo[2]} syntax is sometimes necessaryto disambiguate between array subscripts and character classes./$length[2345]/, for instance, will be interpreted as $length followedby the character class [2345]. If an array subscript is what youwant, you can avoid the warning by changing /${length[2345]}/ to theunsightly /${\$length[2345]}/, by renaming your array to somethingthat does not coincide with a built-in keyword, or by simply turningoff warnings with no warnings 'ambiguous';.

  • Ambiguous use of -%s resolved as -&%s()

    (W ambiguous) You wrote something like -foo, which might be thestring "-foo", or a call to the function foo, negated. If you meantthe string, just write "-foo". If you meant the function call,write -foo().

  • Ambiguous use of 's//le...' resolved as 's// le...'; Rewrite as 's//el' if you meant 'use locale rules and evaluate rhs as an expression'. In Perl 5.18, it will be resolved the other way

    (W deprecated, ambiguous) You wrote a pattern match with substitutionimmediately followed by "le". In Perl 5.16 and earlier, this isresolved as meaning to take the result of the substitution, and see ifit is stringwise less-than-or-equal-to what follows in the expression.Having the "le" immediately following a pattern is deprecated behavior,so in Perl 5.18, this expression will be resolved as meaning to do thepattern match using the rules of the current locale, and evaluate therhs as an expression when doing the substitution. In 5.14, and 5.16 ifyou want the latter interpretation, you can simply write "el" instead.But note that the /l modifier should not be used explicitly anyway;you should use use locale instead. See perllocale.

  • '|' and '<' may not both be specified on command line

    (F) An error peculiar to VMS. Perl does its own command lineredirection, and found that STDIN was a pipe, and that you also tried toredirect STDIN using '<'. Only one STDIN stream to a customer, please.

  • '|' and '>' may not both be specified on command line

    (F) An error peculiar to VMS. Perl does its own command lineredirection, and thinks you tried to redirect stdout both to a file andinto a pipe to another command. You need to choose one or the other,though nothing's stopping you from piping into a program or Perl scriptwhich 'splits' output into two streams, such as

    1. open(OUT,">$ARGV[0]") or die "Can't write to $ARGV[0]: $!";
    2. while (<STDIN>) {
    3. print;
    4. print OUT;
    5. }
    6. close OUT;
  • Applying %s to %s will act on scalar(%s)

    (W misc) The pattern match (//), substitution (s///), andtransliteration (tr///) operators work on scalar values. If you applyone of them to an array or a hash, it will convert the array or hash toa scalar value (the length of an array, or the population info of ahash) and then work on that scalar value. This is probably not whatyou meant to do. See grep and map foralternatives.

  • Arg too short for msgsnd

    (F) msgsnd() requires a string at least as long as sizeof(long).

  • %s argument is not a HASH or ARRAY element or a subroutine

    (F) The argument to exists() must be a hash or array element or asubroutine with an ampersand, such as:

    1. $foo{$bar}
    2. $ref->{"susie"}[12]
    3. &do_something
  • %s argument is not a HASH or ARRAY element or slice

    (F) The argument to delete() must be either a hash or array element,such as:

    1. $foo{$bar}
    2. $ref->{"susie"}[12]

    or a hash or array slice, such as:

    1. @foo[$bar, $baz, $xyzzy]
    2. @{$ref->[12]}{"susie", "queue"}
  • %s argument is not a subroutine name

    (F) The argument to exists() for exists &sub must be a subroutinename, and not a subroutine call. exists &sub() will generate thiserror.

  • Argument "%s" isn't numeric%s

    (W numeric) The indicated string was fed as an argument to an operatorthat expected a numeric value instead. If you're fortunate the messagewill identify which operator was so unfortunate.

  • Argument list not closed for PerlIO layer "%s"

    (W layer) When pushing a layer with arguments onto the Perl I/Osystem you forgot the ) that closes the argument list. (Layerstake care of transforming data between external and internalrepresentations.) Perl stopped parsing the layer list at thispoint and did not attempt to push this layer. If your programdidn't explicitly request the failing operation, it may be theresult of the value of the environment variable PERLIO.

  • Array @%s missing the @ in argument %d of %s()

    (D deprecated) Really old Perl let you omit the @ on array names in somespots. This is now heavily deprecated.

  • assertion botched: %s

    (X) The malloc package that comes with Perl had an internal failure.

  • Assertion failed: file "%s"

    (X) A general assertion failed. The file in question must be examined.

  • Assigning non-zero to $[ is no longer possible

    (F) When the "array_base" feature is disabled (e.g., under use v5.16;)the special variable $[, which is deprecated, is now a fixed zero value.

  • Assignment to both a list and a scalar

    (F) If you assign to a conditional operator, the 2nd and 3rd argumentsmust either both be scalars or both be lists. Otherwise Perl won'tknow which context to supply to the right side.

  • A thread exited while %d threads were running

    (W threads)(S) When using threaded Perl, a thread (not necessarilythe main thread) exited while there were still other threads running.Usually it's a good idea first to collect the return values of thecreated threads by joining them, and only then to exit from the mainthread. See threads.

  • Attempt to access disallowed key '%s' in a restricted hash

    (F) The failing code has attempted to get or set a key which is not inthe current set of allowed keys of a restricted hash.

  • Attempt to bless into a reference

    (F) The CLASSNAME argument to the bless() operator is expected to bethe name of the package to bless the resulting object into. You'vesupplied instead a reference to something: perhaps you wrote

    1. bless $self, $proto;

    when you intended

    1. bless $self, ref($proto) || $proto;

    If you actually want to bless into the stringified versionof the reference supplied, you need to stringify it yourself, forexample by:

    1. bless $self, "$proto";
  • Attempt to clear deleted array

    (S debugging) An array was assigned to when it was being freed.Freed values are not supposed to be visible to Perl code. Thiscan also happen if XS code calls av_clear from a custom magiccallback on the array.

  • Attempt to delete disallowed key '%s' from a restricted hash

    (F) The failing code attempted to delete from a restricted hash a keywhich is not in its key set.

  • Attempt to delete readonly key '%s' from a restricted hash

    (F) The failing code attempted to delete a key whose value has beendeclared readonly from a restricted hash.

  • Attempt to free non-arena SV: 0x%x

    (S internal) All SV objects are supposed to be allocated from arenasthat will be garbage collected on exit. An SV was discovered to beoutside any of those arenas.

  • Attempt to free nonexistent shared string '%s'%s

    (S internal) Perl maintains a reference-counted internal table ofstrings to optimize the storage and access of hash keys and otherstrings. This indicates someone tried to decrement the reference countof a string that can no longer be found in the table.

  • Attempt to free temp prematurely: SV 0x%x

    (S debugging) Mortalized values are supposed to be freed by thefree_tmps() routine. This indicates that something else is freeing theSV before the free_tmps() routine gets a chance, which means that thefree_tmps() routine will be freeing an unreferenced scalar when it doestry to free it.

  • Attempt to free unreferenced glob pointers

    (S internal) The reference counts got screwed up on symbol aliases.

  • Attempt to free unreferenced scalar: SV 0x%x

    (W internal) Perl went to decrement the reference count of a scalar tosee if it would go to 0, and discovered that it had already gone to 0earlier, and should have been freed, and in fact, probably was freed.This could indicate that SvREFCNT_dec() was called too many times, orthat SvREFCNT_inc() was called too few times, or that the SV wasmortalized when it shouldn't have been, or that memory has beencorrupted.

  • Attempt to join self

    (F) You tried to join a thread from within itself, which is animpossible task. You may be joining the wrong thread, or you may needto move the join() to some other thread.

  • Attempt to pack pointer to temporary value

    (W pack) You tried to pass a temporary value (like the result of afunction, or a computed expression) to the "p" pack() template. Thismeans the result contains a pointer to a location that could becomeinvalid anytime, even before the end of the current statement. Useliterals or global values as arguments to the "p" pack() template toavoid this warning.

  • Attempt to reload %s aborted.

    (F) You tried to load a file with use or require that failed tocompile once already. Perl will not try to compile this file againunless you delete its entry from %INC. See require and%INC in perlvar.

  • Attempt to set length of freed array

    (W) You tried to set the length of an array which has been freed. Youcan do this by storing a reference to the scalar representing the last indexof an array and later assigning through that reference. For example

    1. $r = do {my @a; \$#a};
    2. $$r = 503
  • Attempt to use reference as lvalue in substr

    (W substr) You supplied a reference as the first argument to substr()used as an lvalue, which is pretty strange. Perhaps you forgot todereference it first. See substr.

  • Attribute "locked" is deprecated

    (D deprecated) You have used the attributes pragma to modify the"locked" attribute on a code reference. The :locked attribute isobsolete, has had no effect since 5005 threads were removed, andwill be removed in a future release of Perl 5.

  • Attribute "unique" is deprecated

    (D deprecated) You have used the attributes pragma to modifythe "unique" attribute on an array, hash or scalar reference.The :unique attribute has had no effect since Perl 5.8.8, andwill be removed in a future release of Perl 5.

  • av_reify called on tied array

    (S debugging) This indicates that something went wrong and Perl got veryconfused about @_ or @DB::args being tied.

  • Bad arg length for %s, is %u, should be %d

    (F) You passed a buffer of the wrong size to one of msgctl(), semctl()or shmctl(). In C parlance, the correct sizes are, respectively,sizeof(struct msqid_ds *), sizeof(struct semid_ds *), andsizeof(struct shmid_ds *).

  • Bad evalled substitution pattern

    (F) You've used the /e switch to evaluate the replacement for asubstitution, but perl found a syntax error in the code to evaluate,most likely an unexpected right brace '}'.

  • Bad filehandle: %s

    (F) A symbol was passed to something wanting a filehandle, but thesymbol has no filehandle associated with it. Perhaps you didn't do anopen(), or did it in another package.

  • Bad free() ignored

    (S malloc) An internal routine called free() on something that had neverbeen malloc()ed in the first place. Mandatory, but can be disabled bysetting environment variable PERL_BADFREE to 0.

    This message can be seen quite often with DB_File on systems with "hard"dynamic linking, like AIX and OS/2. It is a bug of Berkeley DBwhich is left unnoticed if DB uses forgiving system malloc().

  • Bad hash

    (P) One of the internal hash routines was passed a null HV pointer.

  • Badly placed ()'s

    (A) You've accidentally run your script through csh insteadof Perl. Check the #! line, or manually feed your script intoPerl yourself.

  • Bad name after %s

    (F) You started to name a symbol by using a package prefix, and thendidn't finish the symbol. In particular, you can't interpolate outsideof quotes, so

    1. $var = 'myvar';
    2. $sym = mypack::$var;

    is not the same as

    1. $var = 'myvar';
    2. $sym = "mypack::$var";
  • Bad plugin affecting keyword '%s'

    (F) An extension using the keyword plugin mechanism violated theplugin API.

  • Bad realloc() ignored

    (S malloc) An internal routine called realloc() on something thathad never been malloc()ed in the first place. Mandatory, but canbe disabled by setting the environment variable PERL_BADFREE to 1.

  • Bad symbol for array

    (P) An internal request asked to add an array entry to something thatwasn't a symbol table entry.

  • Bad symbol for dirhandle

    (P) An internal request asked to add a dirhandle entry to somethingthat wasn't a symbol table entry.

  • Bad symbol for filehandle

    (P) An internal request asked to add a filehandle entry to somethingthat wasn't a symbol table entry.

  • Bad symbol for hash

    (P) An internal request asked to add a hash entry to something thatwasn't a symbol table entry.

  • Bareword found in conditional

    (W bareword) The compiler found a bareword where it expected aconditional, which often indicates that an || or && was parsed as partof the last argument of the previous construct, for example:

    1. open FOO || die;

    It may also indicate a misspelled constant that has been interpreted asa bareword:

    1. use constant TYPO => 1;
    2. if (TYOP) { print "foo" }

    The strict pragma is useful in avoiding such errors.

  • Bareword "%s" not allowed while "strict subs" in use

    (F) With "strict subs" in use, a bareword is only allowed as asubroutine identifier, in curly brackets or to the left of the "=>"symbol. Perhaps you need to predeclare a subroutine?

  • Bareword "%s" refers to nonexistent package

    (W bareword) You used a qualified bareword of the form Foo::, but thecompiler saw no other uses of that namespace before that point. Perhapsyou need to predeclare a package?

  • BEGIN failed--compilation aborted

    (F) An untrapped exception was raised while executing a BEGINsubroutine. Compilation stops immediately and the interpreter isexited.

  • BEGIN not safe after errors--compilation aborted

    (F) Perl found a BEGIN {} subroutine (or a use directive, whichimplies a BEGIN {}) after one or more compilation errors had alreadyoccurred. Since the intended environment for the BEGIN {} could notbe guaranteed (due to the errors), and since subsequent code likelydepends on its correct operation, Perl just gave up.

  • \1 better written as $1

    (W syntax) Outside of patterns, backreferences live on as variables.The use of backslashes is grandfathered on the right-hand side of asubstitution, but stylistically it's better to use the variable formbecause other Perl programmers will expect it, and it works better ifthere are more than 9 backreferences.

  • Binary number > 0b11111111111111111111111111111111 non-portable

    (W portable) The binary number you specified is larger than 2**32-1(4294967295) and therefore non-portable between systems. Seeperlport for more on portability concerns.

  • bind() on closed socket %s

    (W closed) You tried to do a bind on a closed socket. Did you forget tocheck the return value of your socket() call? See bind.

  • binmode() on closed filehandle %s

    (W unopened) You tried binmode() on a filehandle that was never opened.Check your control flow and number of arguments.

  • "\b{" is deprecated; use "\b\{" instead
  • "\B{" is deprecated; use "\B\{" instead

    (W deprecated, regexp) Use of an unescaped "{" immediately following a\b or \B is now deprecated so as to reserve its use for Perlitself in a future release.

  • Bit vector size > 32 non-portable

    (W portable) Using bit vector sizes larger than 32 is non-portable.

  • Bizarre copy of %s

    (P) Perl detected an attempt to copy an internal value that is notcopiable.

  • Buffer overflow in prime_env_iter: %s

    (W internal) A warning peculiar to VMS. While Perl was preparing toiterate over %ENV, it encountered a logical name or symbol definitionwhich was too long, so it was truncated to the string shown.

  • Bizarre SvTYPE [%d]

    (P) When starting a new thread or return values from a thread, Perlencountered an invalid data type.

  • Callback called exit

    (F) A subroutine invoked from an external package via call_sv()exited by calling exit.

  • %s() called too early to check prototype

    (W prototype) You've called a function that has a prototype before theparser saw a definition or declaration for it, and Perl could not checkthat the call conforms to the prototype. You need to either add anearly prototype declaration for the subroutine in question, or move thesubroutine definition ahead of the call to get proper prototypechecking. Alternatively, if you are certain that you're calling thefunction correctly, you may put an ampersand before the name to avoidthe warning. See perlsub.

  • Cannot compress integer in pack

    (F) An argument to pack("w",...) was too large to compress. The BERcompressed integer format can only be used with positive integers, and youattempted to compress Infinity or a very large number (> 1e308).See pack.

  • Cannot compress negative numbers in pack

    (F) An argument to pack("w",...) was negative. The BER compressed integerformat can only be used with positive integers. See pack.

  • Cannot convert a reference to %s to typeglob

    (F) You manipulated Perl's symbol table directly, stored a referencein it, then tried to access that symbol via conventional Perl syntax.The access triggers Perl to autovivify that typeglob, but it there isno legal conversion from that type of reference to a typeglob.

  • Cannot copy to %s

    (P) Perl detected an attempt to copy a value to an internal type that cannotbe directly assigned to.

  • Cannot find encoding "%s"

    (S io) You tried to apply an encoding that did not exist to a filehandle,either with open() or binmode().

  • Cannot set tied @DB::args

    (F) caller tried to set @DB::args, but found it tied. Tying @DB::argsis not supported. (Before this error was added, it used to crash.)

  • Cannot tie unreifiable array

    (P) You somehow managed to call tie on an array that does notkeep a reference count on its arguments and cannot be made todo so. Such arrays are not even supposed to be accessible toPerl code, but are only used internally.

  • Can only compress unsigned integers in pack

    (F) An argument to pack("w",...) was not an integer. The BER compressedinteger format can only be used with positive integers, and you attemptedto compress something else. See pack.

  • Can't bless non-reference value

    (F) Only hard references may be blessed. This is how Perl "enforces"encapsulation of objects. See perlobj.

  • Can't "break" in a loop topicalizer

    (F) You called break, but you're in a foreach block rather thana given block. You probably meant to use next or last.

  • Can't "break" outside a given block

    (F) You called break, but you're not inside a given block.

  • Can't call method "%s" on an undefined value

    (F) You used the syntax of a method call, but the slot filled by theobject reference or package name contains an undefined value. Somethinglike this will reproduce the error:

    1. $BADREF = undef;
    2. process $BADREF 1,2,3;
    3. $BADREF->process(1,2,3);
  • Can't call method "%s" on unblessed reference

    (F) A method call must know in what package it's supposed to run. Itordinarily finds this out from the object reference you supply, but youdidn't supply an object reference in this case. A reference isn't anobject reference until it has been blessed. See perlobj.

  • Can't call method "%s" without a package or object reference

    (F) You used the syntax of a method call, but the slot filled by theobject reference or package name contains an expression that returns adefined value which is neither an object reference nor a package name.Something like this will reproduce the error:

    1. $BADREF = 42;
    2. process $BADREF 1,2,3;
    3. $BADREF->process(1,2,3);
  • Can't chdir to %s

    (F) You called perl -x/foo/bar, but /foo/bar is not a directorythat you can chdir to, possibly because it doesn't exist.

  • Can't check filesystem of script "%s" for nosuid

    (P) For some reason you can't check the filesystem of the script fornosuid.

  • Can't coerce %s to %s in %s

    (F) Certain types of SVs, in particular real symbol table entries(typeglobs), can't be forced to stop being what they are. So you can'tsay things like:

    1. *foo += 1;

    You CAN say

    1. $foo = *foo;
    2. $foo += 1;

    but then $foo no longer contains a glob.

  • Can't "continue" outside a when block

    (F) You called continue, but you're not inside a whenor default block.

  • Can't create pipe mailbox

    (P) An error peculiar to VMS. The process is suffering from exhaustedquotas or other plumbing problems.

  • Can't declare %s in "%s"

    (F) Only scalar, array, and hash variables may be declared as "my", "our" or"state" variables. They must have ordinary identifiers as names.

  • Can't "default" outside a topicalizer

    (F) You have used a default block that is neither inside aforeach loop nor a given block. (Note that this error isissued on exit from the default block, so you won't get theerror if you use an explicit continue.)

  • Can't do inplace edit: %s is not a regular file

    (S inplace) You tried to use the -i switch on a special file, such asa file in /dev, or a FIFO. The file was ignored.

  • Can't do inplace edit on %s: %s

    (S inplace) The creation of the new file failed for the indicatedreason.

  • Can't do inplace edit without backup

    (F) You're on a system such as MS-DOS that gets confused if you tryreading from a deleted (but still opened) file. You have to say-i.bak, or some such.

  • Can't do inplace edit: %s would not be unique

    (S inplace) Your filesystem does not support filenames longer than 14characters and Perl was unable to create a unique filename duringinplace editing with the -i switch. The file was ignored.

  • Can't do {n,m} with n > m in regex; marked by <-- HERE in m/%s/

    (F) Minima must be less than or equal to maxima. If you reallywant your regexp to match something 0 times, just put {0}. The<-- HERE shows in the regular expression about where the problemwas discovered. See perlre.

  • Can't do waitpid with flags

    (F) This machine doesn't have either waitpid() or wait4(), so onlywaitpid() without flags is emulated.

  • Can't emulate -%s on #! line

    (F) The #! line specifies a switch that doesn't make sense at thispoint. For example, it'd be kind of silly to put a -x on the #!line.

  • Can't %s %s-endian %ss on this platform

    (F) Your platform's byte-order is neither big-endian nor little-endian,or it has a very strange pointer size. Packing and unpacking big- orlittle-endian floating point values and pointers may not be possible.See pack.

  • Can't exec "%s": %s

    (W exec) A system(), exec(), or piped open call could not execute thenamed program for the indicated reason. Typical reasons include: thepermissions were wrong on the file, the file wasn't found in$ENV{PATH}, the executable in question was compiled for anotherarchitecture, or the #! line in a script points to an interpreter thatcan't be run for similar reasons. (Or maybe your system doesn't support#! at all.)

  • Can't exec %s

    (F) Perl was trying to execute the indicated program for you becausethat's what the #! line said. If that's not what you wanted, you mayneed to mention "perl" on the #! line somewhere.

  • Can't execute %s

    (F) You used the -S switch, but the copies of the script to executefound in the PATH did not have correct permissions.

  • Can't find an opnumber for "%s"

    (F) A string of a form CORE::word was given to prototype(), but thereis no builtin with the name word.

  • Can't find %s character property "%s"

    (F) You used \p{} or \P{} but the character property by that namecould not be found. Maybe you misspelled the name of the property?See Properties accessible through \p{} and \P{} in perlunipropsfor a complete list of available properties.

  • Can't find label %s

    (F) You said to goto a label that isn't mentioned anywhere that it'spossible for us to go to. See goto.

  • Can't find %s on PATH

    (F) You used the -S switch, but the script to execute could not befound in the PATH.

  • Can't find %s on PATH, '.' not in PATH

    (F) You used the -S switch, but the script to execute could not befound in the PATH, or at least not with the correct permissions. Thescript exists in the current directory, but PATH prohibits running it.

  • Can't find string terminator %s anywhere before EOF

    (F) Perl strings can stretch over multiple lines. This message meansthat the closing delimiter was omitted. Because bracketed quotes countnesting levels, the following is missing its final parenthesis:

    1. print q(The character '(' starts a side comment.);

    If you're getting this error from a here-document, you may haveincluded unseen whitespace before or after your closing tag or theremay not be a linebreak after it. A good programmer's editor will havea way to help you find these characters (or lack of characters). Seeperlop for the full details on here-documents.

  • Can't find Unicode property definition "%s"

    (F) You may have tried to use \p which means a Unicodeproperty (for example \p{Lu} matches all uppercaseletters). If you did mean to use a Unicode property, seeProperties accessible through \p{} and \P{} in perlunipropsfor a complete list of available properties. If you didn'tmean to use a Unicode property, escape the \p, either by\p (just the \p) or by \Q\p (the rest of the string, oruntil \E).

  • Can't fork: %s

    (F) A fatal error occurred while trying to fork while opening apipeline.

  • Can't fork, trying again in 5 seconds

    (W pipe) A fork in a piped open failed with EAGAIN and will be retriedafter five seconds.

  • Can't get filespec - stale stat buffer?

    (S) A warning peculiar to VMS. This arises because of the differencebetween access checks under VMS and under the Unix model Perl assumes.Under VMS, access checks are done by filename, rather than by bits inthe stat buffer, so that ACLs and other protections can be taken intoaccount. Unfortunately, Perl assumes that the stat buffer contains allthe necessary information, and passes it, instead of the filespec, tothe access-checking routine. It will try to retrieve the filespec usingthe device name and FID present in the stat buffer, but this works onlyif you haven't made a subsequent call to the CRTL stat() routine,because the device name is overwritten with each call. If this warningappears, the name lookup failed, and the access-checking routine gave upand returned FALSE, just to be conservative. (Note: The access-checkingroutine knows about the Perl stat operator and file tests, so youshouldn't ever see this warning in response to a Perl command; it arisesonly if some internal code takes stat buffers lightly.)

  • Can't get pipe mailbox device name

    (P) An error peculiar to VMS. After creating a mailbox to act as apipe, Perl can't retrieve its name for later use.

  • Can't get SYSGEN parameter value for MAXBUF

    (P) An error peculiar to VMS. Perl asked $GETSYI how big you want yourmailbox buffers to be, and didn't get an answer.

  • Can't "goto" into the middle of a foreach loop

    (F) A "goto" statement was executed to jump into the middle of a foreachloop. You can't get there from here. See goto.

  • Can't "goto" out of a pseudo block

    (F) A "goto" statement was executed to jump out of what might look likea block, except that it isn't a proper block. This usually occurs ifyou tried to jump out of a sort() block or subroutine, which is a no-no.See goto.

  • Can't goto subroutine from a sort sub (or similar callback)

    (F) The "goto subroutine" call can't be used to jump out of thecomparison sub for a sort(), or from a similar callback (suchas the reduce() function in List::Util).

  • Can't goto subroutine from an eval-%s

    (F) The "goto subroutine" call can't be used to jump out of an eval"string" or block.

  • Can't goto subroutine outside a subroutine

    (F) The deeply magical "goto subroutine" call can only replace onesubroutine call for another. It can't manufacture one out of wholecloth. In general you should be calling it out of only an AUTOLOADroutine anyway. See goto.

  • Can't ignore signal CHLD, forcing to default

    (W signal) Perl has detected that it is being run with the SIGCHLDsignal (sometimes known as SIGCLD) disabled. Since disabling thissignal will interfere with proper determination of exit status of childprocesses, Perl has reset the signal to its default value. Thissituation typically indicates that the parent program under which Perlmay be running (e.g. cron) is being very careless.

  • Can't kill a non-numeric process ID

    (F) Process identifiers must be (signed) integers. It is a fatal error toattempt to kill() an undefined, empty-string or otherwise non-numericprocess identifier.

  • Can't "last" outside a loop block

    (F) A "last" statement was executed to break out of the current block,except that there's this itty bitty problem called there isn't a currentblock. Note that an "if" or "else" block doesn't count as a "loopish"block, as doesn't a block given to sort(), map() or grep(). You canusually double the curlies to get the same effect though, because theinner curlies will be considered a block that loops once. Seelast.

  • Can't linearize anonymous symbol table

    (F) Perl tried to calculate the method resolution order (MRO) of apackage, but failed because the package stash has no name.

  • Can't load '%s' for module %s

    (F) The module you tried to load failed to load a dynamic extension.This may either mean that you upgraded your version of perl to onethat is incompatible with your old dynamic extensions (which is knownto happen between major versions of perl), or (more likely) that yourdynamic extension was built against an older version of the librarythat is installed on your system. You may need to rebuild your olddynamic extensions.

  • Can't localize lexical variable %s

    (F) You used local on a variable name that was previously declared as alexical variable using "my" or "state". This is not allowed. If youwant to localize a package variable of the same name, qualify it withthe package name.

  • Can't localize through a reference

    (F) You said something like local $$ref, which Perl can't currentlyhandle, because when it goes to restore the old value of whatever $refpointed to after the scope of the local() is finished, it can't be surethat $ref will still be a reference.

  • Can't locate %s

    (F) You said to do (or require, or use) a file that couldn't be found.Perl looks for the file in all the locations mentioned in @INC, unlessthe file name included the full path to the file. Perhaps you needto set the PERL5LIB or PERL5OPT environment variable to say where theextra library is, or maybe the script needs to add the library nameto @INC. Or maybe you just misspelled the name of the file. Seerequire and lib.

  • Can't locate auto/%s.al in @INC

    (F) A function (or method) was called in a package which allowsautoload, but there is no function to autoload. Most probable causesare a misprint in a function/method name or a failure to AutoSplitthe file, say, by doing make install.

  • Can't locate loadable object for module %s in @INC

    (F) The module you loaded is trying to load an external library, likefor example, foo.so or bar.dll, but the DynaLoader module wasunable to locate this library. See DynaLoader.

  • Can't locate object method "%s" via package "%s"

    (F) You called a method correctly, and it correctly indicated a packagefunctioning as a class, but that package doesn't define that particularmethod, nor does any of its base classes. See perlobj.

  • Can't locate package %s for @%s::ISA

    (W syntax) The @ISA array contained the name of another package thatdoesn't seem to exist.

  • Can't locate PerlIO%s

    (F) You tried to use in open() a PerlIO layer that does not exist,e.g. open(FH, ">:nosuchlayer", "somefile").

  • Can't make list assignment to %ENV on this system

    (F) List assignment to %ENV is not supported on some systems, notablyVMS.

  • Can't modify %s in %s

    (F) You aren't allowed to assign to the item indicated, or otherwise tryto change it, such as with an auto-increment.

  • Can't modify nonexistent substring

    (P) The internal routine that does assignment to a substr() was handeda NULL.

  • Can't modify non-lvalue subroutine call

    (F) Subroutines meant to be used in lvalue context should be declared assuch. See Lvalue subroutines in perlsub.

  • Can't msgrcv to read-only var

    (F) The target of a msgrcv must be modifiable to be used as a receivebuffer.

  • Can't "next" outside a loop block

    (F) A "next" statement was executed to reiterate the current block, butthere isn't a current block. Note that an "if" or "else" block doesn'tcount as a "loopish" block, as doesn't a block given to sort(), map() orgrep(). You can usually double the curlies to get the same effectthough, because the inner curlies will be considered a block that loopsonce. See next.

  • Can't open %s

    (F) You tried to run a perl built with MAD support withthe PERL_XMLDUMP environment variable set, but the filenamed by that variable could not be opened.

  • Can't open %s: %s

    (S inplace) The implicit opening of a file through use of the <>filehandle, either implicitly under the -n or -p command-lineswitches, or explicitly, failed for the indicated reason. Usuallythis is because you don't have read permission for a file whichyou named on the command line.

    (F) You tried to call perl with the -e switch, but /dev/null (oryour operating system's equivalent) could not be opened.

  • Can't open a reference

    (W io) You tried to open a scalar reference for reading or writing,using the 3-arg open() syntax:

    1. open FH, '>', $ref;

    but your version of perl is compiled without perlio, and this form ofopen is not supported.

  • Can't open bidirectional pipe

    (W pipe) You tried to say open(CMD, "|cmd|"), which is not supported.You can try any of several modules in the Perl library to do this, suchas IPC::Open2. Alternately, direct the pipe's output to a file using">", and then read it in under a different file handle.

  • Can't open error file %s as stderr

    (F) An error peculiar to VMS. Perl does its own command lineredirection, and couldn't open the file specified after '2>' or '2>>' onthe command line for writing.

  • Can't open input file %s as stdin

    (F) An error peculiar to VMS. Perl does its own command lineredirection, and couldn't open the file specified after '<' on thecommand line for reading.

  • Can't open output file %s as stdout

    (F) An error peculiar to VMS. Perl does its own command lineredirection, and couldn't open the file specified after '>' or '>>' onthe command line for writing.

  • Can't open output pipe (name: %s)

    (P) An error peculiar to VMS. Perl does its own command lineredirection, and couldn't open the pipe into which to send data destinedfor stdout.

  • Can't open perl script "%s": %s

    (F) The script you specified can't be opened for the indicated reason.

    If you're debugging a script that uses #!, and normally relies on theshell's $PATH search, the -S option causes perl to do that search, soyou don't have to type the path or `which $scriptname`.

  • Can't read CRTL environ

    (S) A warning peculiar to VMS. Perl tried to read an element of %ENVfrom the CRTL's internal environment array and discovered the array wasmissing. You need to figure out where your CRTL misplaced its environor define PERL_ENV_TABLES (see perlvms) so that environ is notsearched.

  • Can't "redo" outside a loop block

    (F) A "redo" statement was executed to restart the current block, butthere isn't a current block. Note that an "if" or "else" block doesn'tcount as a "loopish" block, as doesn't a block given to sort(), map()or grep(). You can usually double the curlies to get the same effectthough, because the inner curlies will be considered a block thatloops once. See redo.

  • Can't remove %s: %s, skipping file

    (S inplace) You requested an inplace edit without creating a backupfile. Perl was unable to remove the original file to replace it withthe modified file. The file was left unmodified.

  • Can't rename %s to %s: %s, skipping file

    (S inplace) The rename done by the -i switch failed for some reason,probably because you don't have write permission to the directory.

  • Can't reopen input pipe (name: %s) in binary mode

    (P) An error peculiar to VMS. Perl thought stdin was a pipe, and triedto reopen it to accept binary data. Alas, it failed.

  • Can't reset %ENV on this system

    (F) You called reset('E') or similar, which tried to resetall variables in the current package beginning with "E". Inthe main package, that includes %ENV. Resetting %ENV is notsupported on some systems, notably VMS.

  • Can't resolve method "%s" overloading "%s" in package "%s"

    (F)(P) Error resolving overloading specified by a method name (asopposed to a subroutine reference): no such method callable via thepackage. If the method name is ???, this is an internal error.

  • Can't return %s from lvalue subroutine

    (F) Perl detected an attempt to return illegal lvalues (such astemporary or readonly values) from a subroutine used as an lvalue. Thisis not allowed.

  • Can't return outside a subroutine

    (F) The return statement was executed in mainline code, that is, wherethere was no subroutine call to return out of. See perlsub.

  • Can't return %s to lvalue scalar context

    (F) You tried to return a complete array or hash from an lvaluesubroutine, but you called the subroutine in a way that made Perlthink you meant to return only one value. You probably meant towrite parentheses around the call to the subroutine, which tellPerl that the call should be in list context.

  • Can't stat script "%s"

    (P) For some reason you can't fstat() the script even though you have itopen already. Bizarre.

  • Can't take log of %g

    (F) For ordinary real numbers, you can't take the logarithm of anegative number or zero. There's a Math::Complex package that comesstandard with Perl, though, if you really want to do that for thenegative numbers.

  • Can't take sqrt of %g

    (F) For ordinary real numbers, you can't take the square root of anegative number. There's a Math::Complex package that comes standardwith Perl, though, if you really want to do that.

  • Can't undef active subroutine

    (F) You can't undefine a routine that's currently running. You can,however, redefine it while it's running, and you can even undef theredefined subroutine while the old routine is running. Go figure.

  • Can't upgrade %s (%d) to %d

    (P) The internal sv_upgrade routine adds "members" to an SV, making itinto a more specialized kind of SV. The top several SV types are sospecialized, however, that they cannot be interconverted. This messageindicates that such a conversion was attempted.

  • Can't use '%c' after -mname

    (F) You tried to call perl with the -m switch, but you put somethingother than "=" after the module name.

  • Can't use anonymous symbol table for method lookup

    (F) The internal routine that does method lookup was handed a symboltable that doesn't have a name. Symbol tables can become anonymousfor example by undefining stashes: undef %Some::Package::.

  • Can't use an undefined value as %s reference

    (F) A value used as either a hard reference or a symbolic reference mustbe a defined value. This helps to delurk some insidious errors.

  • Can't use bareword ("%s") as %s ref while "strict refs" in use

    (F) Only hard references are allowed by "strict refs". Symbolicreferences are disallowed. See perlref.

  • Can't use %! because Errno.pm is not available

    (F) The first time the %! hash is used, perl automatically loads theErrno.pm module. The Errno module is expected to tie the %! hash toprovide symbolic names for $! errno values.

  • Can't use both '<' and '>' after type '%c' in %s

    (F) A type cannot be forced to have both big-endian and little-endianbyte-order at the same time, so this combination of modifiers is notallowed. See pack.

  • Can't use %s for loop variable

    (F) Only a simple scalar variable may be used as a loop variable on aforeach.

  • Can't use global %s in "%s"

    (F) You tried to declare a magical variable as a lexical variable. Thisis not allowed, because the magic can be tied to only one location(namely the global variable) and it would be incredibly confusing tohave variables in your program that looked like magical variables butweren't.

  • Can't use '%c' in a group with different byte-order in %s

    (F) You attempted to force a different byte-order on a typethat is already inside a group with a byte-order modifier.For example you cannot force little-endianness on a type thatis inside a big-endian group.

  • Can't use "my %s" in sort comparison

    (F) The global variables $a and $b are reserved for sort comparisons.You mentioned $a or $b in the same line as the <=> or cmp operator,and the variable had earlier been declared as a lexical variable.Either qualify the sort variable with the package name, or rename thelexical variable.

  • Can't use %s ref as %s ref

    (F) You've mixed up your reference types. You have to dereference areference of the type needed. You can use the ref() function totest the type of the reference, if need be.

  • Can't use string ("%s") as %s ref while "strict refs" in use

    (F) Only hard references are allowed by "strict refs". Symbolicreferences are disallowed. See perlref.

  • Can't use subscript on %s

    (F) The compiler tried to interpret a bracketed expression as asubscript. But to the left of the brackets was an expression thatdidn't look like a hash or array reference, or anything else subscriptable.

  • Can't use \%c to mean $%c in expression

    (W syntax) In an ordinary expression, backslash is a unary operator thatcreates a reference to its argument. The use of backslash to indicate abackreference to a matched substring is valid only as part of a regularexpression pattern. Trying to do this in ordinary Perl code produces avalue that prints out looking like SCALAR(0xdecaf). Use the $1 forminstead.

  • Can't weaken a nonreference

    (F) You attempted to weaken something that was not a reference. Onlyreferences can be weakened.

  • Can't "when" outside a topicalizer

    (F) You have used a when() block that is neither inside a foreachloop nor a given block. (Note that this error is issued on exitfrom the when block, so you won't get the error if the match fails,or if you use an explicit continue.)

  • Can't x= to read-only value

    (F) You tried to repeat a constant value (often the undefined value)with an assignment operator, which implies modifying the value itself.Perhaps you need to copy the value to a temporary, and repeat that.

  • Character following "\c" must be ASCII

    (F)(W deprecated, syntax) In \cX, X must be an ASCII character.It is planned to make this fatal in all instances in Perl 5.18. In thecases where it isn't fatal, the character this evaluates to isderived by exclusive or'ing the code point of this character with 0x40.

    Note that non-alphabetic ASCII characters are discouraged here as well.

  • Character in 'C' format wrapped in pack

    (W pack) You said

    1. pack("C", $x)

    where $x is either less than 0 or more than 255; the "C" format isonly for encoding native operating system characters (ASCII, EBCDIC,and so on) and not for Unicode characters, so Perl behaved as if you meant

    1. pack("C", $x & 255)

    If you actually want to pack Unicode codepoints, use the "U" formatinstead.

  • Character in 'W' format wrapped in pack

    (W pack) You said

    1. pack("U0W", $x)

    where $x is either less than 0 or more than 255. However, U0-modeexpects all values to fall in the interval [0, 255], so Perl behavedas if you meant:

    1. pack("U0W", $x & 255)
  • Character in 'c' format wrapped in pack

    (W pack) You said

    1. pack("c", $x)

    where $x is either less than -128 or more than 127; the "c" formatis only for encoding native operating system characters (ASCII, EBCDIC,and so on) and not for Unicode characters, so Perl behaved as if you meant

    1. pack("c", $x & 255);

    If you actually want to pack Unicode codepoints, use the "U" formatinstead.

  • Character in '%c' format wrapped in unpack

    (W unpack) You tried something like

    1. unpack("H", "\x{2a1}")

    where the format expects to process a byte (a character with a valuebelow 256), but a higher value was provided instead. Perl uses thevalue modulus 256 instead, as if you had provided:

    1. unpack("H", "\x{a1}")
  • Character(s) in '%c' format wrapped in pack

    (W pack) You tried something like

    1. pack("u", "\x{1f3}b")

    where the format expects to process a sequence of bytes (character with avalue below 256), but some of the characters had a higher value. Perluses the character values modulus 256 instead, as if you had provided:

    1. pack("u", "\x{f3}b")
  • Character(s) in '%c' format wrapped in unpack

    (W unpack) You tried something like

    1. unpack("s", "\x{1f3}b")

    where the format expects to process a sequence of bytes (character with avalue below 256), but some of the characters had a higher value. Perluses the character values modulus 256 instead, as if you had provided:

    1. unpack("s", "\x{f3}b")
  • "\c{" is deprecated and is more clearly written as ";"

    (D deprecated, syntax) The \cX construct is intended to be a wayto specify non-printable characters. You used it with a "{" whichevaluates to ";", which is printable. It is planned to remove theability to specify a semi-colon this way in Perl 5.18. Just use asemi-colon or a backslash-semi-colon without the "\c".

  • "\c%c" is more clearly written simply as "%s"

    (W syntax) The \cX construct is intended to be a way to specifynon-printable characters. You used it for a printable one, which is betterwritten as simply itself, perhaps preceded by a backslash for non-wordcharacters.

  • Cloning substitution context is unimplemented

    (F) Creating a new thread inside the s/// operator is not supported.

  • close() on unopened filehandle %s

    (W unopened) You tried to close a filehandle that was never opened.

  • closedir() attempted on invalid dirhandle %s

    (W io) The dirhandle you tried to close is either closed or not reallya dirhandle. Check your control flow.

  • Closure prototype called

    (F) If a closure has attributes, the subroutine passed to an attributehandler is the prototype that is cloned when a new closure is created.This subroutine cannot be called.

  • Code missing after '/'

    (F) You had a (sub-)template that ends with a '/'. There must beanother template code following the slash. See pack.

  • Code point 0x%X is not Unicode, may not be portable
  • Code point 0x%X is not Unicode, all \p{} matches fail; all \P{} matches succeed

    (W utf8, non_unicode) You had a code point above the Unicode maximumof U+10FFFF.

    Perl allows strings to contain a superset of Unicode code points, upto the limit of what is storable in an unsigned integer on your system,but these may not be accepted by other languages/systems. At one time,it was legal in some standards to have code points up to 0x7FFF_FFFF,but not higher. Code points above 0xFFFF_FFFF require larger than a32 bit word.

    None of the Unicode or Perl-defined properties will match a non-Unicodecode point. For example,

    1. chr(0x7FF_FFFF) =~ /\p{Any}/

    will not match, because the code point is not in Unicode. But

    1. chr(0x7FF_FFFF) =~ /\P{Any}/

    will match.

    This may be counterintuitive at times, as both these fail:

    1. chr(0x110000) =~ \p{ASCII_Hex_Digit=True} # Fails.
    2. chr(0x110000) =~ \p{ASCII_Hex_Digit=False} # Also fails!

    and both these succeed:

    1. chr(0x110000) =~ \P{ASCII_Hex_Digit=True} # Succeeds.
    2. chr(0x110000) =~ \P{ASCII_Hex_Digit=False} # Also succeeds!
  • %s: Command not found

    (A) You've accidentally run your script through csh or another shellshell instead of Perl. Check the #! line, or manually feed your scriptinto Perl yourself. The #! line at the top of your file could look like

    1. #!/usr/bin/perl -w
  • Compilation failed in require

    (F) Perl could not compile a file specified in a require statement.Perl uses this generic message when none of the errors that itencountered were severe enough to halt compilation immediately.

  • Complex regular subexpression recursion limit (%d) exceeded

    (W regexp) The regular expression engine uses recursion in complexsituations where back-tracking is required. Recursion depth is limitedto 32766, or perhaps less in architectures where the stack cannot growarbitrarily. ("Simple" and "medium" situations are handled withoutrecursion and are not subject to a limit.) Try shortening the stringunder examination; looping in Perl code (e.g. with while) rather thanin the regular expression engine; or rewriting the regular expression sothat it is simpler or backtracks less. (See perlfaq2 for informationon Mastering Regular Expressions.)

  • cond_broadcast() called on unlocked variable

    (W threads) Within a thread-enabled program, you tried tocall cond_broadcast() on a variable which wasn't locked.The cond_broadcast() function is used to wake up another threadthat is waiting in a cond_wait(). To ensure that the signal isn'tsent before the other thread has a chance to enter the wait, itis usual for the signaling thread first to wait for a lock onvariable. This lock attempt will only succeed after the otherthread has entered cond_wait() and thus relinquished the lock.

  • cond_signal() called on unlocked variable

    (W threads) Within a thread-enabled program, you tried tocall cond_signal() on a variable which wasn't locked. Thecond_signal() function is used to wake up another thread thatis waiting in a cond_wait(). To ensure that the signal isn'tsent before the other thread has a chance to enter the wait, itis usual for the signaling thread first to wait for a lock onvariable. This lock attempt will only succeed after the otherthread has entered cond_wait() and thus relinquished the lock.

  • connect() on closed socket %s

    (W closed) You tried to do a connect on a closed socket. Did you forgetto check the return value of your socket() call? Seeconnect.

  • Constant(%s)%s: %s

    (F) The parser found inconsistencies either while attempting to definean overloaded constant, or when trying to find the character namespecified in the \N{...} escape. Perhaps you forgot to load thecorresponding overload pragma?.

  • Constant(%s)%s: %s in regex; marked by <-- HERE in m/%s/

    (F) The parser found inconsistencies while attempting to findthe character name specified in the \N{...} escape.

  • Constant is not %s reference

    (F) A constant value (perhaps declared using the use constant pragma)is being dereferenced, but it amounts to the wrong type of reference.The message indicates the type of reference that was expected. Thisusually indicates a syntax error in dereferencing the constant value.See Constant Functions in perlsub and constant.

  • Constant subroutine %s redefined

    (W redefine)(S) You redefined a subroutine which had previouslybeen eligible for inlining. See Constant Functions in perlsubfor commentary and workarounds.

  • Constant subroutine %s undefined

    (W misc) You undefined a subroutine which had previously been eligiblefor inlining. See Constant Functions in perlsub for commentary andworkarounds.

  • Copy method did not return a reference

    (F) The method which overloads "=" is buggy. SeeCopy Constructor in overload.

  • &CORE::%s cannot be called directly

    (F) You tried to call a subroutine in the CORE:: namespacewith &foo syntax or through a reference. Some subroutinesin this package cannot yet be called that way, but must becalled as barewords. Something like this will work:

    1. BEGIN { *shove = \&CORE::push; }
    2. shove @array, 1,2,3; # pushes on to @array
  • CORE::%s is not a keyword

    (F) The CORE:: namespace is reserved for Perl keywords.

  • corrupted regexp pointers

    (P) The regular expression engine got confused by what the regularexpression compiler gave it.

  • corrupted regexp program

    (P) The regular expression engine got passed a regexp program without avalid magic number.

  • Corrupt malloc ptr 0x%x at 0x%x

    (P) The malloc package that comes with Perl had an internal failure.

  • Count after length/code in unpack

    (F) You had an unpack template indicating a counted-length string, butyou have also specified an explicit size for the string. Seepack.

  • Deep recursion on anonymous subroutine
  • Deep recursion on subroutine "%s"

    (W recursion) This subroutine has called itself (directly or indirectly)100 times more than it has returned. This probably indicates aninfinite recursion, unless you're writing strange benchmark programs, inwhich case it indicates something else.

    This threshold can be changed from 100, by recompiling the perl binary,setting the C pre-processor macro PERL_SUB_DEPTH_WARN to the desired value.

  • defined(@array) is deprecated

    (D deprecated) defined() is not usually useful on arrays because itchecks for an undefined scalar value. If you want to see if thearray is empty, just use if (@array) { # not empty } for example.

  • defined(%hash) is deprecated

    (D deprecated) defined() is not usually right on hashes and has beendiscouraged since 5.004.

    Although defined %hash is false on a plain not-yet-used hash, itbecomes true in several non-obvious circumstances, including iterators,weak references, stash names, even remaining true after undef %hash.These things make defined %hash fairly useless in practice.

    If a check for non-empty is what you wanted then just put it in booleancontext (see Scalar values in perldata):

    1. if (%hash) {
    2. # not empty
    3. }

    If you had defined %Foo::Bar::QUUX to check whether such a packagevariable exists then that's never really been reliable, and isn'ta good way to enquire about the features of a package, or whetherit's loaded, etc.

  • (?(DEFINE)....) does not allow branches in regex; marked by <-- HERE in m/%s/

    (F) You used something like (?(DEFINE)...|..) which is illegal. Themost likely cause of this error is that you left out a parenthesis insideof the .... part.

    The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • %s defines neither package nor VERSION--version check failed

    (F) You said something like "use Module 42" but in the Module filethere are neither package declarations nor a $VERSION.

  • Delimiter for here document is too long

    (F) In a here document construct like <<FOO, the label FOO is toolong for Perl to handle. You have to be seriously twisted to write codethat triggers this error.

  • Deprecated character in \N{...}; marked by <-- HERE in \N{%s<-- HERE %s

    (D deprecated) Just about anything is legal for the ... in \N{...}.But starting in 5.12, non-reasonable ones that don't look like namesare deprecated. A reasonable name begins with an alphabetic characterand continues with any combination of alphanumerics, dashes, spaces,parentheses or colons.

  • Deprecated use of my() in false conditional

    (D deprecated) You used a declaration similar to my $x if 0. Therehas been a long-standing bug in Perl that causes a lexical variablenot to be cleared at scope exit when its declaration includes a falseconditional. Some people have exploited this bug to achieve a kind ofstatic variable. Since we intend to fix this bug, we don't want peoplerelying on this behavior. You can achieve a similar static effect bydeclaring the variable in a separate block outside the function, eg

    1. sub f { my $x if 0; return $x++ }

    becomes

    1. { my $x; sub f { return $x++ } }

    Beginning with perl 5.9.4, you can also use state variables to havelexicals that are initialized only once (see feature):

    1. sub f { state $x; return $x++ }
  • DESTROY created new reference to dead object '%s'

    (F) A DESTROY() method created a new reference to the object which isjust being DESTROYed. Perl is confused, and prefers to abort ratherthan to create a dangling reference.

  • Did not produce a valid header

    See Server error.

  • %s did not return a true value

    (F) A required (or used) file must return a true value to indicate thatit compiled correctly and ran its initialization code correctly. It'straditional to end such a file with a "1;", though any true value woulddo. See require.

  • (Did you mean &%s instead?)

    (W misc) You probably referred to an imported subroutine &FOO as $FOO orsome such.

  • (Did you mean "local" instead of "our"?)

    (W misc) Remember that "our" does not localize the declared globalvariable. You have declared it again in the same lexical scope, whichseems superfluous.

  • (Did you mean $ or @ instead of %?)

    (W) You probably said %hash{$key} when you meant $hash{$key} or@hash{@keys}. On the other hand, maybe you just meant %hash and gotcarried away.

  • Died

    (F) You passed die() an empty string (the equivalent of die "") oryou called it with no args and $@ was empty.

  • Document contains no data

    See Server error.

  • %s does not define %s::VERSION--version check failed

    (F) You said something like "use Module 42" but the Module did notdefine a $VERSION.

  • '/' does not take a repeat count

    (F) You cannot put a repeat count of any kind right after the '/' code.See pack.

  • Don't know how to handle magic of type '%s'

    (P) The internal handling of magical variables has been cursed.

  • do_study: out of memory

    (P) This should have been caught by safemalloc() instead.

  • (Do you need to predeclare %s?)

    (S syntax) This is an educated guess made in conjunction with the message"%s found where operator expected". It often means a subroutine or modulename is being referenced that hasn't been declared yet. This may bebecause of ordering problems in your file, or because of a missing"sub", "package", "require", or "use" statement. If you're referencingsomething that isn't defined yet, you don't actually have to define thesubroutine or package before the current location. You can use an empty"sub foo;" or "package FOO;" to enter a "forward" declaration.

  • dump() better written as CORE::dump()

    (W misc) You used the obsolescent dump() built-in function, without fullyqualifying it as CORE::dump(). Maybe it's a typo. See dump.

  • dump is not supported

    (F) Your machine doesn't support dump/undump.

  • Duplicate free() ignored

    (S malloc) An internal routine called free() on something that hadalready been freed.

  • Duplicate modifier '%c' after '%c' in %s

    (W) You have applied the same modifier more than once after a typein a pack template. See pack.

  • elseif should be elsif

    (S syntax) There is no keyword "elseif" in Perl because Larry thinksit's ugly. Your code will be interpreted as an attempt to call a methodnamed "elseif" for the class returned by the following block. This isunlikely to be what you want.

  • Empty %s

    (F) \p and \P are used to introduce a named Unicode property, asdescribed in perlunicode and perlre. You used \p or \P ina regular expression without specifying the property name.

  • entering effective %s failed

    (F) While under the use filetest pragma, switching the real andeffective uids or gids failed.

  • %ENV is aliased to %s

    (F) You're running under taint mode, and the %ENV variable has beenaliased to another hash, so it doesn't reflect anymore the state of theprogram's environment. This is potentially insecure.

  • Error converting file specification %s

    (F) An error peculiar to VMS. Because Perl may have to deal with filespecifications in either VMS or Unix syntax, it converts them to asingle form when it must operate on them directly. Either you've passedan invalid file specification to Perl, or you've found a case theconversion routines don't handle. Drat.

  • %s: Eval-group in insecure regular expression

    (F) Perl detected tainted data when trying to compile a regularexpression that contains the (?{ ... }) zero-width assertion, whichis unsafe. See (?{ code }) in perlre, and perlsec.

  • %s: Eval-group not allowed at runtime, use re 'eval'

    (F) Perl tried to compile a regular expression containing the(?{ ... }) zero-width assertion at run time, as it would when thepattern contains interpolated values. Since that is a security risk,it is not allowed. If you insist, you may still do this by using there 'eval' pragma or by explicitly building the pattern from aninterpolated string at run time and using that in an eval(). See(?{ code }) in perlre.

  • %s: Eval-group not allowed, use re 'eval'

    (F) A regular expression contained the (?{ ... }) zero-widthassertion, but that construct is only allowed when the use re 'eval'pragma is in effect. See (?{ code }) in perlre.

  • EVAL without pos change exceeded limit in regex; marked by <-- HERE in m/%s/

    (F) You used a pattern that nested too many EVAL calls without consumingany text. Restructure the pattern so that text is consumed.

    The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • Excessively long <> operator

    (F) The contents of a <> operator may not exceed the maximum size of aPerl identifier. If you're just trying to glob a long list offilenames, try using the glob() operator, or put the filenames into avariable and glob that.

  • exec? I'm not *that* kind of operating system

    (F) The exec function is not implemented on some systems, e.g., SymbianOS. See perlport.

  • Execution of %s aborted due to compilation errors.

    (F) The final summary message when a Perl compilation fails.

  • Exiting eval via %s

    (W exiting) You are exiting an eval by unconventional means, such as agoto, or a loop control statement.

  • Exiting format via %s

    (W exiting) You are exiting a format by unconventional means, such as agoto, or a loop control statement.

  • Exiting pseudo-block via %s

    (W exiting) You are exiting a rather special block construct (like asort block or subroutine) by unconventional means, such as a goto, or aloop control statement. See sort.

  • Exiting subroutine via %s

    (W exiting) You are exiting a subroutine by unconventional means, suchas a goto, or a loop control statement.

  • Exiting substitution via %s

    (W exiting) You are exiting a substitution by unconventional means, suchas a return, a goto, or a loop control statement.

  • Explicit blessing to '' (assuming package main)

    (W misc) You are blessing a reference to a zero length string. This hasthe effect of blessing the reference into the package main. This isusually not what you want. Consider providing a default target package,e.g. bless($ref, $p || 'MyPackage');

  • %s: Expression syntax

    (A) You've accidentally run your script through csh instead of Perl.Check the #! line, or manually feed your script into Perl yourself.

  • %s failed--call queue aborted

    (F) An untrapped exception was raised while executing a UNITCHECK,CHECK, INIT, or END subroutine. Processing of the remainder of thequeue of such routines has been prematurely ended.

  • False [] range "%s" in regex; marked by <-- HERE in m/%s/

    (W regexp) A character class range must start and end at a literalcharacter, not another character class like \d or [:alpha:]. The "-"in your false range is interpreted as a literal "-". Consider quoting the"-", "\-". The <-- HERE shows in the regular expression about where theproblem was discovered. See perlre.

  • Fatal VMS error (status=%d) at %s, line %d

    (P) An error peculiar to VMS. Something untoward happened in a VMSsystem service or RTL routine; Perl's exit status should provide moredetails. The filename in "at %s" and the line number in "line %d" tellyou which section of the Perl source code is distressed.

  • fcntl is not implemented

    (F) Your machine apparently doesn't implement fcntl(). What is this, aPDP-11 or something?

  • FETCHSIZE returned a negative value

    (F) A tied array claimed to have a negative number of elements, whichis not possible.

  • Field too wide in 'u' format in pack

    (W pack) Each line in an uuencoded string start with a length indicatorwhich can't encode values above 63. So there is no point in asking fora line length bigger than that. Perl will behave as if you specifiedu63 as the format.

  • Filehandle %s opened only for input

    (W io) You tried to write on a read-only filehandle. If you intendedit to be a read-write filehandle, you needed to open it with "+<" or"+>" or "+>>" instead of with "<" or nothing. If you intended only towrite the file, use ">" or ">>". See open.

  • Filehandle %s opened only for output

    (W io) You tried to read from a filehandle opened only for writing, Ifyou intended it to be a read/write filehandle, you needed to open itwith "+<" or "+>" or "+>>" instead of with ">". If you intended only toread from the file, use "<". See open. Another possibilityis that you attempted to open filedescriptor 0 (also known as STDIN) foroutput (maybe you closed STDIN earlier?).

  • Filehandle %s reopened as %s only for input

    (W io) You opened for reading a filehandle that got the same filehandle idas STDOUT or STDERR. This occurred because you closed STDOUT or STDERRpreviously.

  • Filehandle STDIN reopened as %s only for output

    (W io) You opened for writing a filehandle that got the same filehandle idas STDIN. This occurred because you closed STDIN previously.

  • Final $ should be \$ or $name

    (F) You must now decide whether the final $ in a string was meant to bea literal dollar sign, or was meant to introduce a variable name thathappens to be missing. So you have to put either the backslash or thename.

  • flock() on closed filehandle %s

    (W closed) The filehandle you're attempting to flock() got itself closedsome time before now. Check your control flow. flock() operates onfilehandles. Are you attempting to call flock() on a dirhandle by thesame name?

  • Format not terminated

    (F) A format must be terminated by a line with a solitary dot. Perl gotto the end of your file without finding such a line.

  • Format %s redefined

    (W redefine) You redefined a format. To suppress this warning, say

    1. {
    2. no warnings 'redefine';
    3. eval "format NAME =...";
    4. }
  • Found = in conditional, should be ==

    (W syntax) You said

    1. if ($foo = 123)

    when you meant

    1. if ($foo == 123)

    (or something like that).

  • %s found where operator expected

    (S syntax) The Perl lexer knows whether to expect a term or an operator.If it sees what it knows to be a term when it was expecting to see anoperator, it gives you this warning. Usually it indicates that anoperator or delimiter was omitted, such as a semicolon.

  • gdbm store returned %d, errno %d, key "%s"

    (S) A warning from the GDBM_File extension that a store failed.

  • gethostent not implemented

    (F) Your C library apparently doesn't implement gethostent(), probablybecause if it did, it'd feel morally obligated to return every hostnameon the Internet.

  • get%sname() on closed socket %s

    (W closed) You tried to get a socket or peer socket name on a closedsocket. Did you forget to check the return value of your socket() call?

  • getpwnam returned invalid UIC %#o for user "%s"

    (S) A warning peculiar to VMS. The call to sys$getuai underlying thegetpwnam operator returned an invalid UIC.

  • getsockopt() on closed socket %s

    (W closed) You tried to get a socket option on a closed socket. Did youforget to check the return value of your socket() call? Seegetsockopt.

  • Global symbol "%s" requires explicit package name

    (F) You've said "use strict" or "use strict vars", which indicates that all variables must either be lexically scoped (using "my" or "state"), declared beforehand using "our", or explicitly qualified to say which package the global variable is in (using "::").

  • glob failed (%s)

    (S glob) Something went wrong with the external program(s) usedfor glob and <*.c>. Usually, this means that you supplied a globpattern that caused the external program to fail and exit with anonzero status. If the message indicates that the abnormal exitresulted in a coredump, this may also mean that your csh (C shell)is broken. If so, you should change all of the csh-related variablesin config.sh: If you have tcsh, make the variables refer to it asif it were csh (e.g. full_csh='/usr/bin/tcsh'); otherwise, make themall empty (except that d_csh should be 'undef') so that Perl willthink csh is missing. In either case, after editing config.sh, run./Configure -S and rebuild Perl.

  • Glob not terminated

    (F) The lexer saw a left angle bracket in a place where it was expectinga term, so it's looking for the corresponding right angle bracket, andnot finding it. Chances are you left some needed parentheses outearlier in the line, and you really meant a "less than".

  • gmtime(%f) too large

    (W overflow) You called gmtime with a number that was larger thanit can reliably handle and gmtime probably returned the wrongdate. This warning is also triggered with NaN (the specialnot-a-number value).

  • gmtime(%f) too small

    (W overflow) You called gmtime with a number that was smaller thanit can reliably handle and gmtime probably returned the wrong date.

  • Got an error from DosAllocMem

    (P) An error peculiar to OS/2. Most probably you're using an obsoleteversion of Perl, and this should not happen anyway.

  • goto must have label

    (F) Unlike with "next" or "last", you're not allowed to goto anunspecified destination. See goto.

  • Goto undefined subroutine%s

    (F) You tried to call a subroutine with goto &sub syntax, butthe indicated subroutine hasn't been defined, or if it was, ithas since been undefined.

  • ()-group starts with a count

    (F) A ()-group started with a count. A count is supposed to followsomething: a template character or a ()-group. See pack.

  • %s had compilation errors.

    (F) The final summary message when a perl -c fails.

  • Had to create %s unexpectedly

    (S internal) A routine asked for a symbol from a symbol table that oughtto have existed already, but for some reason it didn't, and had to becreated on an emergency basis to prevent a core dump.

  • Hash %%s missing the % in argument %d of %s()

    (D deprecated) Really old Perl let you omit the % on hash names in somespots. This is now heavily deprecated.

  • %s has too many errors

    (F) The parser has given up trying to parse the program after 10 errors.Further error messages would likely be uninformative.

  • Having no space between pattern and following word is deprecated

    (D syntax)

    You had a word that isn't a regex modifier immediately followinga pattern without an intervening space. If you are trying to usethe /le flags on a substitution, use /el instead. Otherwise, addwhite space between the pattern and following word to eliminatethe warning. As an example of the latter, the two constructs:

    1. $a =~ m/$foo/sand $bar
    2. $a =~ m/$foo/s and $bar

    both currently mean the same thing, but it is planned to disallowthe first form in Perl 5.18. And,

    1. $a =~ m/$foo/and $bar

    will be disallowed too.

  • Hexadecimal number > 0xffffffff non-portable

    (W portable) The hexadecimal number you specified is larger than 2**32-1(4294967295) and therefore non-portable between systems. Seeperlport for more on portability concerns.

  • Identifier too long

    (F) Perl limits identifiers (names for variables, functions, etc.) toabout 250 characters for simple names, and somewhat more for compoundnames (like $A::B). You've exceeded Perl's limits. Future versionsof Perl are likely to eliminate these arbitrary limitations.

  • Ignoring zero length \N{} in character class

    (W) Named Unicode character escapes (\N{...}) may return a zero-lengthsequence. When such an escape is used in a character class itsbehaviour is not well defined. Check that the correct escape hasbeen used, and the correct charname handler is in scope.

  • Illegal binary digit %s

    (F) You used a digit other than 0 or 1 in a binary number.

  • Illegal binary digit %s ignored

    (W digit) You may have tried to use a digit other than 0 or 1 in abinary number. Interpretation of the binary number stopped before theoffending digit.

  • Illegal character after '_' in prototype for %s : %s

    (W illegalproto) An illegal character was found in a prototype declaration.Legal characters in prototypes are $, @, %, *, ;, [, ], &, \, and +.

  • Illegal character \%o (carriage return)

    (F) Perl normally treats carriage returns in the program text as itwould any other whitespace, which means you should never see this errorwhen Perl was built using standard options. For some reason, yourversion of Perl appears to have been built without this support. Talkto your Perl administrator.

  • Illegal character in prototype for %s : %s

    (W illegalproto) An illegal character was found in a prototype declaration.Legal characters in prototypes are $, @, %, *, ;, [, ], &, \, and +.

  • Illegal declaration of anonymous subroutine

    (F) When using the sub keyword to construct an anonymous subroutine,you must always specify a block of code. See perlsub.

  • Illegal declaration of subroutine %s

    (F) A subroutine was not declared correctly. See perlsub.

  • Illegal division by zero

    (F) You tried to divide a number by 0. Either something was wrong inyour logic, or you need to put a conditional in to guard againstmeaningless input.

  • Illegal hexadecimal digit %s ignored

    (W digit) You may have tried to use a character other than 0 - 9 orA - F, a - f in a hexadecimal number. Interpretation of the hexadecimalnumber stopped before the illegal character.

  • Illegal modulus zero

    (F) You tried to divide a number by 0 to get the remainder. Mostnumbers don't take to this kindly.

  • Illegal number of bits in vec

    (F) The number of bits in vec() (the third argument) must be a power oftwo from 1 to 32 (or 64, if your platform supports that).

  • Illegal octal digit %s

    (F) You used an 8 or 9 in an octal number.

  • Illegal octal digit %s ignored

    (W digit) You may have tried to use an 8 or 9 in an octal number.Interpretation of the octal number stopped before the 8 or 9.

  • Illegal switch in PERL5OPT: -%c

    (X) The PERL5OPT environment variable may only be used to set thefollowing switches: -[CDIMUdmtw].

  • Ill-formed CRTL environ value "%s"

    (W internal) A warning peculiar to VMS. Perl tried to read the CRTL'sinternal environ array, and encountered an element without the =delimiter used to separate keys from values. The element is ignored.

  • Ill-formed message in prime_env_iter: |%s|

    (W internal) A warning peculiar to VMS. Perl tried to read a logicalname or CLI symbol definition when preparing to iterate over %ENV, anddidn't see the expected delimiter between key and value, so the line wasignored.

  • (in cleanup) %s

    (W misc) This prefix usually indicates that a DESTROY() method raisedthe indicated exception. Since destructors are usually called by thesystem at arbitrary points during execution, and often a vast number oftimes, the warning is issued only once for any number of failures thatwould otherwise result in the same message being repeated.

    Failure of user callbacks dispatched using the G_KEEPERR flag couldalso result in this warning. See G_KEEPERR in perlcall.

  • Inconsistent hierarchy during C3 merge of class '%s': merging failed on parent '%s'

    (F) The method resolution order (MRO) of the given class is notC3-consistent, and you have enabled the C3 MRO for this class. See the C3documentation in mro for more information.

  • In EBCDIC the v-string components cannot exceed 2147483647

    (F) An error peculiar to EBCDIC. Internally, v-strings are stored asUnicode code points, and encoded in EBCDIC as UTF-EBCDIC. The UTF-EBCDICencoding is limited to code points no larger than 2147483647 (0x7FFFFFFF).

  • Infinite recursion in regex; marked by <-- HERE in m/%s/

    (F) You used a pattern that references itself without consuming any inputtext. You should check the pattern to ensure that recursive patternseither consume text or fail.

    The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • Initialization of state variables in list context currently forbidden

    (F) Currently the implementation of "state" only permits theinitialization of scalar variables in scalar context. Re-writestate ($a) = 42 as state $a = 42 to change from list to scalarcontext. Constructions such as state (@a) = foo() will besupported in a future perl release.

  • Insecure dependency in %s

    (F) You tried to do something that the tainting mechanism didn't like.The tainting mechanism is turned on when you're running setuid orsetgid, or when you specify -T to turn it on explicitly. Thetainting mechanism labels all data that's derived directly or indirectlyfrom the user, who is considered to be unworthy of your trust. If anysuch data is used in a "dangerous" operation, you get this error. Seeperlsec for more information.

  • Insecure directory in %s

    (F) You can't use system(), exec(), or a piped open in a setuid orsetgid script if $ENV{PATH} contains a directory that is writable bythe world. Also, the PATH must not contain any relative directory.See perlsec.

  • Insecure $ENV{%s} while running %s

    (F) You can't use system(), exec(), or a piped open in a setuid orsetgid script if any of $ENV{PATH}, $ENV{IFS}, $ENV{CDPATH},$ENV{ENV}, $ENV{BASH_ENV} or $ENV{TERM} are derived from datasupplied (or potentially supplied) by the user. The script must setthe path to a known value, using trustworthy data. See perlsec.

  • Insecure user-defined property %s

    (F) Perl detected tainted data when trying to compile a regularexpression that contains a call to a user-defined character propertyfunction, i.e. \p{IsFoo} or \p{InFoo}.See User-Defined Character Properties in perlunicode and perlsec.

  • Integer overflow in format string for %s

    (F) The indexes and widths specified in the format string of printf()or sprintf() are too large. The numbers must not overflow the size ofintegers for your architecture.

  • Integer overflow in %s number

    (W overflow) The hexadecimal, octal or binary number you have specifiedeither as a literal or as an argument to hex() or oct() is too big foryour architecture, and has been converted to a floating point number.On a 32-bit architecture the largest hexadecimal, octal or binary numberrepresentable without overflow is 0xFFFFFFFF, 037777777777, or0b11111111111111111111111111111111 respectively. Note that Perltransparently promotes all numbers to a floating point representationinternally--subject to loss of precision errors in subsequentoperations.

  • Integer overflow in version

    (F) Some portion of a version initialization is too large for thesize of integers for your architecture. This is not a warningbecause there is no rational reason for a version to try and use aelement larger than typically 2**32. This is usually caused bytrying to use some odd mathematical operation as a version, like100/9.

  • Internal disaster in regex; marked by <-- HERE in m/%s/

    (P) Something went badly wrong in the regular expression parser.The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • Internal inconsistency in tracking vforks

    (S) A warning peculiar to VMS. Perl keeps track of the number of timesyou've called fork and exec, to determine whether the current callto exec should affect the current script or a subprocess (seeexec LIST in perlvms). Somehow, this count has become scrambled, soPerl is making a guess and treating this exec as a request toterminate the Perl script and execute the specified command.

  • Internal urp in regex; marked by <-- HERE in m/%s/

    (P) Something went badly awry in the regular expression parser. The<-- HERE shows in the regular expression about where the problem wasdiscovered.

  • %s (...) interpreted as function

    (W syntax) You've run afoul of the rule that says that any list operatorfollowed by parentheses turns into a function, with all the listoperators arguments found inside the parentheses. SeeTerms and List Operators (Leftward) in perlop.

  • Invalid %s attribute: %s

    (F) The indicated attribute for a subroutine or variable was not recognizedby Perl or by a user-supplied handler. See attributes.

  • Invalid %s attributes: %s

    (F) The indicated attributes for a subroutine or variable were notrecognized by Perl or by a user-supplied handler. See attributes.

  • Invalid conversion in %s: "%s"

    (W printf) Perl does not understand the given format conversion. Seesprintf.

  • Invalid escape in the specified encoding in regex; marked by <-- HERE in m/%s/

    (W regexp) The numeric escape (for example \xHH) of value < 256didn't correspond to a single character through the conversionfrom the encoding specified by the encoding pragma.The escape was replaced with REPLACEMENT CHARACTER (U+FFFD) instead.The <-- HERE shows in the regular expression about where theescape was discovered.

  • Invalid hexadecimal number in \N{U+...}

    (F) The character constant represented by ... is not a valid hexadecimalnumber. Either it is empty, or you tried to use a character other than0 - 9 or A - F, a - f in a hexadecimal number.

  • Invalid module name %s with -%c option: contains single ':'

    (F) The module argument to perl's -m and -M command-line optionscannot contain single colons in the module name, but only in thearguments after "=". In other words, -MFoo::Bar=:baz is ok, but-MFoo:Bar=baz is not.

  • Invalid mro name: '%s'

    (F) You tried to mro::set_mro("classname", "foo") or use mro 'foo',where foo is not a valid method resolution order (MRO). Currently,the only valid ones supported are dfs and c3, unless you have loadeda module that is a MRO plugin. See mro and perlmroapi.

  • invalid option -D%c, use -D'' to see choices

    (F) Perl was called with invalid debugger flags. Call perl withthe -D option with no flags to see the list of acceptable values.See also -Dletters in perlrun.

  • Invalid [] range "%s" in regex; marked by <-- HERE in m/%s/

    (F) The range specified in a character class had a minimum charactergreater than the maximum character. One possibility is that you forgot the{} from your ending \x{} - \x without the curly braces can go onlyup to ff. The <-- HERE shows in the regular expression about where theproblem was discovered. See perlre.

  • Invalid range "%s" in transliteration operator

    (F) The range specified in the tr/// or y/// operator had a minimumcharacter greater than the maximum character. See perlop.

  • Invalid separator character %s in attribute list

    (F) Something other than a colon or whitespace was seen between theelements of an attribute list. If the previous attribute had aparenthesised parameter list, perhaps that list was terminated too soon.See attributes.

  • Invalid separator character %s in PerlIO layer specification %s

    (W layer) When pushing layers onto the Perl I/O system, something otherthan a colon or whitespace was seen between the elements of a layer list.If the previous attribute had a parenthesised parameter list, perhaps thatlist was terminated too soon.

  • Invalid strict version format (%s)

    (F) A version number did not meet the "strict" criteria for versions.A "strict" version number is a positive decimal number (integer ordecimal-fraction) without exponentiation or else a dotted-decimalv-string with a leading 'v' character and at least three components.The parenthesized text indicates which criteria were not met.See the version module for more details on allowed version formats.

  • Invalid type '%s' in %s

    (F) The given character is not a valid pack or unpack type.See pack.

    (W) The given character is not a valid pack or unpack type but used to besilently ignored.

  • Invalid version format (%s)

    (F) A version number did not meet the "lax" criteria for versions.A "lax" version number is a positive decimal number (integer ordecimal-fraction) without exponentiation or else a dotted-decimalv-string. If the v-string has fewer than three components, itmust have a leading 'v' character. Otherwise, the leading 'v' isoptional. Both decimal and dotted-decimal versions may have atrailing "alpha" component separated by an underscore characterafter a fractional or dotted-decimal component. The parenthesizedtext indicates which criteria were not met. See the version modulefor more details on allowed version formats.

  • Invalid version object

    (F) The internal structure of the version object was invalid.Perhaps the internals were modified directly in some way oran arbitrary reference was blessed into the "version" class.

  • ioctl is not implemented

    (F) Your machine apparently doesn't implement ioctl(), which is prettystrange for a machine that supports C.

  • ioctl() on unopened %s

    (W unopened) You tried ioctl() on a filehandle that was never opened.Check your control flow and number of arguments.

  • IO layers (like '%s') unavailable

    (F) Your Perl has not been configured to have PerlIO, and thereforeyou cannot use IO layers. To have PerlIO, Perl must be configuredwith 'useperlio'.

  • IO::Socket::atmark not implemented on this architecture

    (F) Your machine doesn't implement the sockatmark() functionality,neither as a system call nor an ioctl call (SIOCATMARK).

  • $* is no longer supported

    (D deprecated, syntax) The special variable $*, deprecated in olderperls, has been removed as of 5.9.0 and is no longer supported. Inprevious versions of perl the use of $* enabled or disabled multi-linematching within a string.

    Instead of using $* you should use the /m (and maybe /s) regexpmodifiers. You can enable /m for a lexical scope (even a whole file)with use re '/m'. (In older versions: when $* was set to a true valuethen all regular expressions behaved as if they were written using /m.)

  • $# is no longer supported

    (D deprecated, syntax) The special variable $#, deprecated in olderperls, has been removed as of 5.9.3 and is no longer supported. Youshould use the printf/sprintf functions instead.

  • '%s' is not a code reference

    (W overload) The second (fourth, sixth, ...) argument ofoverload::constant needs to be a code reference. Eitheran anonymous subroutine, or a reference to a subroutine.

  • '%s' is not an overloadable type

    (W overload) You tried to overload a constant type the overload package isunaware of.

  • junk on end of regexp

    (P) The regular expression parser is confused.

  • Label not found for "last %s"

    (F) You named a loop to break out of, but you're not currently in a loopof that name, not even if you count where you were called from. Seelast.

  • Label not found for "next %s"

    (F) You named a loop to continue, but you're not currently in a loop ofthat name, not even if you count where you were called from. Seelast.

  • Label not found for "redo %s"

    (F) You named a loop to restart, but you're not currently in a loop ofthat name, not even if you count where you were called from. Seelast.

  • leaving effective %s failed

    (F) While under the use filetest pragma, switching the real andeffective uids or gids failed.

  • length/code after end of string in unpack

    (F) While unpacking, the string buffer was already used up when an unpacklength/code combination tried to obtain more data. This results inan undefined value for the length. See pack.

  • length() used on %s

    (W syntax) You used length() on either an array or a hash when youprobably wanted a count of the items.

    Array size can be obtained by doing:

    1. scalar(@array);

    The number of items in a hash can be obtained by doing:

    1. scalar(keys %hash);
  • Lexing code attempted to stuff non-Latin-1 character into Latin-1 input

    (F) An extension is attempting to insert text into the current parse(using lex_stuff_pvn or similar), but tried to insert a character thatcouldn't be part of the current input. This is an inherent pitfallof the stuffing mechanism, and one of the reasons to avoid it. Whereit is necessary to stuff, stuffing only plain ASCII is recommended.

  • Lexing code internal error (%s)

    (F) Lexing code supplied by an extension violated the lexer's API in adetectable way.

  • listen() on closed socket %s

    (W closed) You tried to do a listen on a closed socket. Did you forgetto check the return value of your socket() call? Seelisten.

  • List form of piped open not implemented

    (F) On some platforms, notably Windows, the three-or-more-argumentsform of open does not support pipes, such as open($pipe, '|-', @args).Use the two-argument open($pipe, '|prog arg1 arg2...') form instead.

  • localtime(%f) too large

    (W overflow) You called localtime with a number that was largerthan it can reliably handle and localtime probably returned thewrong date. This warning is also triggered with NaN (the specialnot-a-number value).

  • localtime(%f) too small

    (W overflow) You called localtime with a number that was smallerthan it can reliably handle and localtime probably returned thewrong date.

  • Lookbehind longer than %d not implemented in regex m/%s/

    (F) There is currently a limit on the length of string which lookbehind canhandle. This restriction may be eased in a future release.

  • Lost precision when %s %f by 1

    (W) The value you attempted to increment or decrement by one is too largefor the underlying floating point representation to store accurately,hence the target of ++ or -- is unchanged. Perl issues this warningbecause it has already switched from integers to floating point when valuesare too large for integers, and now even floating point is insufficient.You may wish to switch to using Math::BigInt explicitly.

  • lstat() on filehandle%s

    (W io) You tried to do an lstat on a filehandle. What did you meanby that? lstat() makes sense only on filenames. (Perl did a fstat()instead on the filehandle.)

  • lvalue attribute %s already-defined subroutine

    (W misc) Although attributes.pm allows this, turning the lvalueattribute on or off on a Perl subroutine that is already defineddoes not always work properly. It may or may not do what youwant, depending on what code is inside the subroutine, with exactdetails subject to change between Perl versions. Only do thisif you really know what you are doing.

  • lvalue attribute ignored after the subroutine has been defined

    (W misc) Using the :lvalue declarative syntax to make a Perlsubroutine an lvalue subroutine after it has been defined isnot permitted. To make the subroutine an lvalue subroutine,add the lvalue attribute to the definition, or put the subfoo :lvalue; declaration before the definition.

    See also attributes.pm.

  • Malformed integer in [] in pack

    (F) Between the brackets enclosing a numeric repeat count only digitsare permitted. See pack.

  • Malformed integer in [] in unpack

    (F) Between the brackets enclosing a numeric repeat count only digitsare permitted. See pack.

  • Malformed PERLLIB_PREFIX

    (F) An error peculiar to OS/2. PERLLIB_PREFIX should be of the form

    1. prefix1;prefix2

    or prefix1 prefix2

    with nonempty prefix1 and prefix2. If prefix1 is indeed a prefix ofa builtin library search path, prefix2 is substituted. The error mayappear if components are not found, or are too long. See"PERLLIB_PREFIX" in perlos2.

  • Malformed prototype for %s: %s

    (F) You tried to use a function with a malformed prototype. Thesyntax of function prototypes is given a brief compile-time check forobvious errors like invalid characters. A more rigorous check is runwhen the function is called.

  • Malformed UTF-8 character (%s)

    (S utf8)(F) Perl detected a string that didn't comply with UTF-8encoding rules, even though it had the UTF8 flag on.

    One possible cause is that you set the UTF8 flag yourself for data thatyou thought to be in UTF-8 but it wasn't (it was for example legacy8-bit data). To guard against this, you can use Encode::decode_utf8.

    If you use the :encoding(UTF-8) PerlIO layer for input, invalid bytesequences are handled gracefully, but if you use :utf8, the flag isset without validating the data, possibly resulting in this errormessage.

    See also Handling Malformed Data in Encode.

  • Malformed UTF-8 returned by \N

    (F) The charnames handler returned malformed UTF-8.

  • Malformed UTF-8 string in '%c' format in unpack

    (F) You tried to unpack something that didn't comply with UTF-8 encodingrules and perl was unable to guess how to make more progress.

  • Malformed UTF-8 string in pack

    (F) You tried to pack something that didn't comply with UTF-8 encodingrules and perl was unable to guess how to make more progress.

  • Malformed UTF-8 string in unpack

    (F) You tried to unpack something that didn't comply with UTF-8 encodingrules and perl was unable to guess how to make more progress.

  • Malformed UTF-16 surrogate

    (F) Perl thought it was reading UTF-16 encoded character data but whiledoing it Perl met a malformed Unicode surrogate.

  • %s matches null string many times in regex; marked by <-- HERE in m/%s/

    (W regexp) The pattern you've specified would be an infinite loop if theregular expression engine didn't specifically check for that. The <-- HEREshows in the regular expression about where the problem was discovered.See perlre.

  • Maximal count of pending signals (%u) exceeded

    (F) Perl aborted due to too high a number of signals pending. Thisusually indicates that your operating system tried to deliver signalstoo fast (with a very high priority), starving the perl process fromresources it would need to reach a point where it can process signalssafely. (See Deferred Signals (Safe Signals) in perlipc.)

  • "%s" may clash with future reserved word

    (W) This warning may be due to running a perl5 script through a perl4interpreter, especially if the word that is being warned about is"use" or "my".

  • '%' may not be used in pack

    (F) You can't pack a string by supplying a checksum, because thechecksumming process loses information, and you can't go the other way.See unpack.

  • Method for operation %s not found in package %s during blessing

    (F) An attempt was made to specify an entry in an overloading table thatdoesn't resolve to a valid subroutine. See overload.

  • Method %s not permitted

    See Server error.

  • Might be a runaway multi-line %s string starting on line %d

    (S) An advisory indicating that the previous error may have been causedby a missing delimiter on a string or pattern, because it eventuallyended earlier on the current line.

  • Misplaced _ in number

    (W syntax) An underscore (underbar) in a numeric constant did notseparate two digits.

  • Missing argument in %s

    (W uninitialized) A printf-type format required more arguments than weresupplied.

  • Missing argument to -%c

    (F) The argument to the indicated command line switch must followimmediately after the switch, without intervening spaces.

  • Missing braces on \N{}

    (F) Wrong syntax of character name literal \N{charname} withindouble-quotish context. This can also happen when there is a space(or comment) between the \N and the { in a regex with the /x modifier.This modifier does not change the requirement that the brace immediatelyfollow the \N.

  • Missing braces on \o{}

    (F) A \o must be followed immediately by a { in double-quotish context.

  • Missing comma after first argument to %s function

    (F) While certain functions allow you to specify a filehandle or an"indirect object" before the argument list, this ain't one of them.

  • Missing command in piped open

    (W pipe) You used the open(FH, "| command") oropen(FH, "command |") construction, but the command was missing orblank.

  • Missing control char name in \c

    (F) A double-quoted string ended with "\c", without the required controlcharacter name.

  • Missing name in "my sub"

    (F) The reserved syntax for lexically scoped subroutines requires thatthey have a name with which they can be found.

  • Missing $ on loop variable

    (F) Apparently you've been programming in csh too much. Variablesare always mentioned with the $ in Perl, unlike in the shells, where itcan vary from one line to the next.

  • (Missing operator before %s?)

    (S syntax) This is an educated guess made in conjunction with the message"%s found where operator expected". Often the missing operator is a comma.

  • Missing right brace on %s

    (F) Missing right brace in \x{...}, \p{...}, \P{...}, or \N{...}.

  • Missing right brace on \N{} or unescaped left brace after \N

    (F) \N has two meanings.

    The traditional one has it followed by a name enclosed in braces,meaning the character (or sequence of characters) given by thatname. Thus \N{ASTERISK} is another way of writing *, valid in bothdouble-quoted strings and regular expression patterns. In patterns,it doesn't have the meaning an unescaped * does.

    Starting in Perl 5.12.0, \N also can have an additional meaning (only)in patterns, namely to match a non-newline character. (This is shortfor [^\n], and like . but is not affected by the /s regex modifier.)

    This can lead to some ambiguities. When \N is not followed immediatelyby a left brace, Perl assumes the [^\n] meaning. Also, if the bracesform a valid quantifier such as \N{3} or \N{5,}, Perl assumes that thismeans to match the given quantity of non-newlines (in these examples,3; and 5 or more, respectively). In all other case, where there is a\N{ and a matching }, Perl assumes that a character name is desired.

    However, if there is no matching }, Perl doesn't know if it wasmistakenly omitted, or if [^\n]{ was desired, and raises this error.If you meant the former, add the right brace; if you meant the latter,escape the brace with a backslash, like so: \N\{

  • Missing right curly or square bracket

    (F) The lexer counted more opening curly or square brackets than closingones. As a general rule, you'll find it's missing near the place youwere last editing.

  • (Missing semicolon on previous line?)

    (S syntax) This is an educated guess made in conjunction with the message"%s found where operator expected". Don't automatically put a semicolon onthe previous line just because you saw this message.

  • Modification of a read-only value attempted

    (F) You tried, directly or indirectly, to change the value of aconstant. You didn't, of course, try "2 = 1", because the compilercatches that. But an easy way to do the same thing is:

    1. sub mod { $_[0] = 1 }
    2. mod(2);

    Another way is to assign to a substr() that's off the end of the string.

    Yet another way is to assign to a foreach loop VAR when VARis aliased to a constant in the look LIST:

    1. $x = 1;
    2. foreach my $n ($x, 2) {
    3. $n *= 2; # modifies the $x, but fails on attempt to
    4. } # modify the 2
  • Modification of non-creatable array value attempted, %s

    (F) You tried to make an array value spring into existence, and thesubscript was probably negative, even counting from end of the arraybackwards.

  • Modification of non-creatable hash value attempted, %s

    (P) You tried to make a hash value spring into existence, and itcouldn't be created for some peculiar reason.

  • Module name must be constant

    (F) Only a bare module name is allowed as the first argument to a "use".

  • Module name required with -%c option

    (F) The -M or -m options say that Perl should load some module, butyou omitted the name of the module. Consult perlrun for full detailsabout -M and -m.

  • More than one argument to '%s' open

    (F) The open function has been asked to open multiple files. Thiscan happen if you are trying to open a pipe to a command that takes alist of arguments, but have forgotten to specify a piped open mode.See open for details.

  • msg%s not implemented

    (F) You don't have System V message IPC on your system.

  • Multidimensional syntax %s not supported

    (W syntax) Multidimensional arrays aren't written like $foo[1,2,3].They're written like $foo[1][2][3], as in C.

  • '/' must follow a numeric type in unpack

    (F) You had an unpack template that contained a '/', but this did notfollow some unpack specification producing a numeric value.See pack.

  • "my sub" not yet implemented

    (F) Lexically scoped subroutines are not yet implemented. Don't trythat yet.

  • "my" variable %s can't be in a package

    (F) Lexically scoped variables aren't in a package, so it doesn't makesense to try to declare one with a package qualifier on the front. Uselocal() if you want to localize a package variable.

  • Name "%s::%s" used only once: possible typo

    (W once) Typographical errors often show up as unique variable names.If you had a good reason for having a unique name, then just mention itagain somehow to suppress the message. The our declaration isprovided for this purpose.

    NOTE: This warning detects symbols that have been used only once so $c, @c,%c, *c, &c, sub c{}, c(), and c (the filehandle or format) are consideredthe same; if a program uses $c only once but also uses any of the others itwill not trigger this warning.

  • \N in a character class must be a named character: \N{...}

    (F) The new (5.12) meaning of \N as [^\n] is not valid in a bracketedcharacter class, for the same reason that . in a character class losesits specialness: it matches almost everything, which is probably notwhat you want.

  • \N{NAME} must be resolved by the lexer

    (F) When compiling a regex pattern, an unresolved named character orsequence was encountered. This can happen in any of several ways thatbypass the lexer, such as using single-quotish context, or an extrabackslash in double-quotish:

    1. $re = '\N{SPACE}';# Wrong!
    2. $re = "\N{SPACE}";# Wrong!
    3. /$re/;

    Instead, use double-quotes with a single backslash:

    1. $re = "\N{SPACE}";# ok
    2. /$re/;

    The lexer can be bypassed as well by creating the pattern from smallercomponents:

    1. $re = '\N';
    2. /${re}{SPACE}/;# Wrong!

    It's not a good idea to split a construct in the middle like this, and itdoesn't work here. Instead use the solution above.

    Finally, the message also can happen under the /x regex modifier when the\N is separated by spaces from the {, in which case, remove the spaces.

    1. /\N {SPACE}/x;# Wrong!
    2. /\N{SPACE}/x;# ok
  • Negative '/' count in unpack

    (F) The length count obtained from a length/code unpack operation wasnegative. See pack.

  • Negative length

    (F) You tried to do a read/write/send/recv operation with a bufferlength that is less than 0. This is difficult to imagine.

  • Negative offset to vec in lvalue context

    (F) When vec is called in an lvalue context, the second argument must begreater than or equal to zero.

  • Nested quantifiers in regex; marked by <-- HERE in m/%s/

    (F) You can't quantify a quantifier without intervening parentheses.So things like ** or +* or ?* are illegal. The <-- HERE shows in theregular expression about where the problem was discovered.

    Note that the minimal matching quantifiers, *?, +?, and?? appear to be nested quantifiers, but aren't. See perlre.

  • %s never introduced

    (S internal) The symbol in question was declared but somehow went out ofscope before it could possibly have been used.

  • next::method/next::can/maybe::next::method cannot find enclosing method

    (F) next::method needs to be called within the context of areal method in a real package, and it could not find such a context.See mro.

  • No %s allowed while running setuid

    (F) Certain operations are deemed to be too insecure for a setuid orsetgid script to even be allowed to attempt. Generally speaking therewill be another way to do what you want that is, if not secure, at leastsecurable. See perlsec.

  • No code specified for -%c

    (F) Perl's -e and -E command-line options require an argument. Ifyou want to run an empty program, pass the empty string as a separateargument or run a program consisting of a single 0 or 1:

    1. perl -e ""
    2. perl -e0
    3. perl -e1
  • No comma allowed after %s

    (F) A list operator that has a filehandle or "indirect object" isnot allowed to have a comma between that and the following arguments.Otherwise it'd be just another one of the arguments.

    One possible cause for this is that you expected to have importeda constant to your name space with use or import while no suchimporting took place, it may for example be that your operatingsystem does not support that particular constant. Hopefully you diduse an explicit import list for the constants you expect to see;please see use and import. While anexplicit import list would probably have caught this error earlierit naturally does not remedy the fact that your operating systemstill does not support that constant. Maybe you have a typo inthe constants of the symbol import list of use or import or in theconstant name at the line where this error was triggered?

  • No command into which to pipe on command line

    (F) An error peculiar to VMS. Perl handles its own command lineredirection, and found a '|' at the end of the command line, so itdoesn't know where you want to pipe the output from this command.

  • No DB::DB routine defined

    (F) The currently executing code was compiled with the -d switch, butfor some reason the current debugger (e.g. perl5db.pl or a Devel::module) didn't define a routine to be called at the beginning of eachstatement.

  • No dbm on this machine

    (P) This is counted as an internal error, because every machine shouldsupply dbm nowadays, because Perl comes with SDBM. See SDBM_File.

  • No DB::sub routine defined

    (F) The currently executing code was compiled with the -d switch, butfor some reason the current debugger (e.g. perl5db.pl or a Devel::module) didn't define a DB::sub routine to be called at the beginningof each ordinary subroutine call.

  • No directory specified for -I

    (F) The -I command-line switch requires a directory name as part of thesame argument. Use -Ilib, for instance. -I lib won't work.

  • No error file after 2> or 2>> on command line

    (F) An error peculiar to VMS. Perl handles its own command lineredirection, and found a '2>' or a '2>>' on the command line, but can'tfind the name of the file to which to write data destined for stderr.

  • No group ending character '%c' found in template

    (F) A pack or unpack template has an opening '(' or '[' without itsmatching counterpart. See pack.

  • No input file after < on command line

    (F) An error peculiar to VMS. Perl handles its own command lineredirection, and found a '<' on the command line, but can't find thename of the file from which to read data for stdin.

  • No next::method '%s' found for %s

    (F) next::method found no further instances of this method namein the remaining packages of the MRO of this class. If you don't wantit throwing an exception, use maybe::next::methodor next::can. See mro.

  • "no" not allowed in expression

    (F) The "no" keyword is recognized and executed at compile time, andreturns no useful value. See perlmod.

  • No output file after > on command line

    (F) An error peculiar to VMS. Perl handles its own command lineredirection, and found a lone '>' at the end of the command line, so itdoesn't know where you wanted to redirect stdout.

  • No output file after > or>> on command line

    (F) An error peculiar to VMS. Perl handles its own command lineredirection, and found a '>' or a '>>' on the command line, but can'tfind the name of the file to which to write data destined for stdout.

  • No package name allowed for variable %s in "our"

    (F) Fully qualified variable names are not allowed in "our"declarations, because that doesn't make much sense under existingsemantics. Such syntax is reserved for future extensions.

  • No Perl script found in input

    (F) You called perl -x, but no line was found in the file beginningwith #! and containing the word "perl".

  • No setregid available

    (F) Configure didn't find anything resembling the setregid() call foryour system.

  • No setreuid available

    (F) Configure didn't find anything resembling the setreuid() call foryour system.

  • No such class field "%s" in variable %s of type %s

    (F) You tried to access a key from a hash through the indicated typedvariable but that key is not allowed by the package of the same type.The indicated package has restricted the set of allowed keys using thefields pragma.

  • No such class %s

    (F) You provided a class qualifier in a "my", "our" or "state"declaration, but this class doesn't exist at this point in your program.

  • No such hook: %s

    (F) You specified a signal hook that was not recognized by Perl.Currently, Perl accepts __DIE__ and __WARN__ as valid signal hooks.

  • No such pipe open

    (P) An error peculiar to VMS. The internal routine my_pclose() tried toclose a pipe which hadn't been opened. This should have been caughtearlier as an attempt to close an unopened filehandle.

  • No such signal: SIG%s

    (W signal) You specified a signal name as a subscript to %SIG that wasnot recognized. Say kill -l in your shell to see the valid signalnames on your system.

  • Not a CODE reference

    (F) Perl was trying to evaluate a reference to a code value (that is, asubroutine), but found a reference to something else instead. You canuse the ref() function to find out what kind of ref it really was. Seealso perlref.

  • Not a format reference

    (F) I'm not sure how you managed to generate a reference to an anonymousformat, but this indicates you did, and that it didn't exist.

  • Not a GLOB reference

    (F) Perl was trying to evaluate a reference to a "typeglob" (that is, asymbol table entry that looks like *foo), but found a reference tosomething else instead. You can use the ref() function to find out whatkind of ref it really was. See perlref.

  • Not a HASH reference

    (F) Perl was trying to evaluate a reference to a hash value, but found areference to something else instead. You can use the ref() function tofind out what kind of ref it really was. See perlref.

  • Not an ARRAY reference

    (F) Perl was trying to evaluate a reference to an array value, but founda reference to something else instead. You can use the ref() functionto find out what kind of ref it really was. See perlref.

  • Not an unblessed ARRAY reference

    (F) You passed a reference to a blessed array to push, shift oranother array function. These only accept unblessed array referencesor arrays beginning explicitly with @.

  • Not a SCALAR reference

    (F) Perl was trying to evaluate a reference to a scalar value, but founda reference to something else instead. You can use the ref() functionto find out what kind of ref it really was. See perlref.

  • Not a subroutine reference

    (F) Perl was trying to evaluate a reference to a code value (that is, asubroutine), but found a reference to something else instead. You canuse the ref() function to find out what kind of ref it really was. Seealso perlref.

  • Not a subroutine reference in overload table

    (F) An attempt was made to specify an entry in an overloading table thatdoesn't somehow point to a valid subroutine. See overload.

  • Not enough arguments for %s

    (F) The function requires more arguments than you specified.

  • Not enough format arguments

    (W syntax) A format specified more picture fields than the next linesupplied. See perlform.

  • %s: not found

    (A) You've accidentally run your script through the Bourne shell insteadof Perl. Check the #! line, or manually feed your script into Perlyourself.

  • no UTC offset information; assuming local time is UTC

    (S) A warning peculiar to VMS. Perl was unable to find the localtimezone offset, so it's assuming that local system time is equivalentto UTC. If it's not, define the logical nameSYS$TIMEZONE_DIFFERENTIAL to translate to the number of seconds whichneed to be added to UTC to get local time.

  • Non-octal character '%c'. Resolved as "%s"

    (W digit) In parsing an octal numeric constant, a character wasunexpectedly encountered that isn't octal. The resulting valueis as indicated.

  • Non-string passed as bitmask

    (W misc) A number has been passed as a bitmask argument to select().Use the vec() function to construct the file descriptor bitmasks forselect. See select.

  • Null filename used

    (F) You can't require the null filename, especially because on manymachines that means the current directory! See require.

  • NULL OP IN RUN

    (S debugging) Some internal routine called run() with a null opcodepointer.

  • Null picture in formline

    (F) The first argument to formline must be a valid format picturespecification. It was found to be empty, which probably means yousupplied it an uninitialized value. See perlform.

  • Null realloc

    (P) An attempt was made to realloc NULL.

  • NULL regexp argument

    (P) The internal pattern matching routines blew it big time.

  • NULL regexp parameter

    (P) The internal pattern matching routines are out of their gourd.

  • Number too long

    (F) Perl limits the representation of decimal numbers in programs toabout 250 characters. You've exceeded that length. Futureversions of Perl are likely to eliminate this arbitrary limitation. Inthe meantime, try using scientific notation (e.g. "1e6" instead of"1_000_000").

  • Number with no digits

    (F) Perl was looking for a number but found nothing that looked likea number. This happens, for example with \o{}, with no number betweenthe braces.

  • Octal number > 037777777777 non-portable

    (W portable) The octal number you specified is larger than 2**32-1(4294967295) and therefore non-portable between systems. Seeperlport for more on portability concerns.

  • Odd number of arguments for overload::constant

    (W overload) The call to overload::constant contained an odd number ofarguments. The arguments should come in pairs.

  • Odd number of elements in anonymous hash

    (W misc) You specified an odd number of elements to initialize a hash,which is odd, because hashes come in key/value pairs.

  • Odd number of elements in hash assignment

    (W misc) You specified an odd number of elements to initialize a hash,which is odd, because hashes come in key/value pairs.

  • Offset outside string

    (F)(W layer) You tried to do a read/write/send/recv/seek operationwith an offset pointing outside the buffer. This is difficult toimagine. The sole exceptions to this are that zero padding willtake place when going past the end of the string when eithersysread()ing a file, or when seeking past the end of a scalar openedfor I/O (in anticipation of future reads and to imitate the behaviourwith real files).

  • %s() on unopened %s

    (W unopened) An I/O operation was attempted on a filehandle that wasnever initialized. You need to do an open(), a sysopen(), or a socket()call, or call a constructor from the FileHandle package.

  • -%s on unopened filehandle %s

    (W unopened) You tried to invoke a file test operator on a filehandlethat isn't open. Check your control flow. See also -X.

  • oops: oopsAV

    (S internal) An internal warning that the grammar is screwed up.

  • oops: oopsHV

    (S internal) An internal warning that the grammar is screwed up.

  • Opening dirhandle %s also as a file

    (W io, deprecated) You used open() to associate a filehandle toa symbol (glob or scalar) that already holds a dirhandle.Although legal, this idiom might render your code confusingand is deprecated.

  • Opening filehandle %s also as a directory

    (W io, deprecated) You used opendir() to associate a dirhandle toa symbol (glob or scalar) that already holds a filehandle.Although legal, this idiom might render your code confusingand is deprecated.

  • Operation "%s": no method found, %s

    (F) An attempt was made to perform an overloaded operation for which nohandler was defined. While some handlers can be autogenerated in termsof other handlers, there is no default handler for any operation, unlessthe fallback overloading key is specified to be true. See overload.

  • Operation "%s" returns its argument for non-Unicode code point 0x%X

    (W utf8, non_unicode) You performed an operation requiring Unicodesemantics on a code point that is not in Unicode, so what it should dois not defined. Perl has chosen to have it do nothing, and warn you.

    If the operation shown is "ToFold", it means that case-insensitivematching in a regular expression was done on the code point.

    If you know what you are doing you can turn off this warning byno warnings 'non_unicode';.

  • Operation "%s" returns its argument for UTF-16 surrogate U+%X

    (W utf8, surrogate) You performed an operation requiring Unicodesemantics on a Unicode surrogate. Unicode frowns upon the use ofsurrogates for anything but storing strings in UTF-16, but semanticsare (reluctantly) defined for the surrogates, and they are to donothing for this operation. Because the use of surrogates can bedangerous, Perl warns.

    If the operation shown is "ToFold", it means that case-insensitivematching in a regular expression was done on the code point.

    If you know what you are doing you can turn off this warning byno warnings 'surrogate';.

  • Operator or semicolon missing before %s

    (S ambiguous) You used a variable or subroutine call where the parserwas expecting an operator. The parser has assumed you really meant touse an operator, but this is highly likely to be incorrect. Forexample, if you say "*foo *foo" it will be interpreted as if you said"*foo * 'foo'".

  • "our" variable %s redeclared

    (W misc) You seem to have already declared the same global once beforein the current lexical scope.

  • Out of memory!

    (X) The malloc() function returned 0, indicating there was insufficientremaining memory (or virtual memory) to satisfy the request. Perl hasno option but to exit immediately.

    At least in Unix you may be able to get past this by increasing yourprocess datasize limits: in csh/tcsh use limit andlimit datasize n (where n is the number of kilobytes) to checkthe current limits and change them, and in ksh/bash/zsh use ulimit -aand ulimit -d n, respectively.

  • Out of memory during %s extend

    (X) An attempt was made to extend an array, a list, or a string beyondthe largest possible memory allocation.

  • Out of memory during "large" request for %s

    (F) The malloc() function returned 0, indicating there was insufficientremaining memory (or virtual memory) to satisfy the request. However,the request was judged large enough (compile-time default is 64K), so apossibility to shut down by trapping this error is granted.

  • Out of memory during request for %s

    (X)(F) The malloc() function returned 0, indicating there wasinsufficient remaining memory (or virtual memory) to satisfy therequest.

    The request was judged to be small, so the possibility to trap itdepends on the way perl was compiled. By default it is not trappable.However, if compiled for this, Perl may use the contents of $^M as anemergency pool after die()ing with this message. In this case the erroris trappable once, and the error message will include the line and filewhere the failed request happened.

  • Out of memory during ridiculously large request

    (F) You can't allocate more than 2^31+"small amount" bytes. This erroris most likely to be caused by a typo in the Perl program. e.g.,$arr[time] instead of $arr[$time].

  • Out of memory for yacc stack

    (F) The yacc parser wanted to grow its stack so it could continueparsing, but realloc() wouldn't give it more memory, virtual orotherwise.

  • '.' outside of string in pack

    (F) The argument to a '.' in your template tried to move the workingposition to before the start of the packed string being built.

  • '@' outside of string in unpack

    (F) You had a template that specified an absolute position outsidethe string being unpacked. See pack.

  • '@' outside of string with malformed UTF-8 in unpack

    (F) You had a template that specified an absolute position outsidethe string being unpacked. The string being unpacked was also invalidUTF-8. See pack.

  • overload arg '%s' is invalid

    (W overload) The overload pragma was passed an argument it did notrecognize. Did you mistype an operator?

  • Overloaded dereference did not return a reference

    (F) An object with an overloaded dereference operator was dereferenced,but the overloaded operation did not return a reference. Seeoverload.

  • Overloaded qr did not return a REGEXP

    (F) An object with a qr overload was used as part of a match, but theoverloaded operation didn't return a compiled regexp. See overload.

  • %s package attribute may clash with future reserved word: %s

    (W reserved) A lowercase attribute name was used that had apackage-specific handler. That name might have a meaning to Perl itselfsome day, even though it doesn't yet. Perhaps you should use amixed-case attribute name, instead. See attributes.

  • pack/unpack repeat count overflow

    (F) You can't specify a repeat count so large that it overflows yoursigned integers. See pack.

  • page overflow

    (W io) A single call to write() produced more lines than can fit on apage. See perlform.

  • panic: %s

    (P) An internal error.

  • panic: attempt to call %s in %s

    (P) One of the file test operators entered a code branch that callsan ACL related-function, but that function is not available on thisplatform. Earlier checks mean that it should not be possible toenter this branch on this platform.

  • panic: ck_grep, type=%u

    (P) Failed an internal consistency check trying to compile a grep.

  • panic: ck_split, type=%u

    (P) Failed an internal consistency check trying to compile a split.

  • panic: corrupt saved stack index %ld

    (P) The savestack was requested to restore more localized values thanthere are in the savestack.

  • panic: del_backref

    (P) Failed an internal consistency check while trying to reset a weakreference.

  • panic: die %s

    (P) We popped the context stack to an eval context, and then discoveredit wasn't an eval context.

  • panic: do_subst

    (P) The internal pp_subst() routine was called with invalid operationaldata.

  • panic: do_trans_%s

    (P) The internal do_trans routines were called with invalid operationaldata.

  • panic: fold_constants JMPENV_PUSH returned %d

    (P) While attempting folding constants an exception other than an evalfailure was caught.

  • panic: frexp

    (P) The library function frexp() failed, making printf("%f") impossible.

  • panic: goto, type=%u, ix=%ld

    (P) We popped the context stack to a context with the specified label,and then discovered it wasn't a context we know how to do a goto in.

  • panic: gp_free failed to free glob pointer

    (P) The internal routine used to clear a typeglob's entries triedrepeatedly, but each time something re-created entries in the glob.Most likely the glob contains an object with a reference back tothe glob and a destructor that adds a new object to the glob.

  • panic: INTERPCASEMOD, %s

    (P) The lexer got into a bad state at a case modifier.

  • panic: INTERPCONCAT, %s

    (P) The lexer got into a bad state parsing a string with brackets.

  • panic: kid popen errno read

    (F) forked child returned an incomprehensible message about its errno.

  • panic: last, type=%u

    (P) We popped the context stack to a block context, and then discoveredit wasn't a block context.

  • panic: leave_scope clearsv

    (P) A writable lexical variable became read-only somehow within thescope.

  • panic: leave_scope inconsistency %u

    (P) The savestack probably got out of sync. At least, there was aninvalid enum on the top of it.

  • panic: magic_killbackrefs

    (P) Failed an internal consistency check while trying to reset all weakreferences to an object.

  • panic: malloc, %s

    (P) Something requested a negative number of bytes of malloc.

  • panic: memory wrap

    (P) Something tried to allocate more memory than possible.

  • panic: pad_alloc, %p!=%p

    (P) The compiler got confused about which scratch pad it was allocatingand freeing temporaries and lexicals from.

  • panic: pad_free curpad, %p!=%p

    (P) The compiler got confused about which scratch pad it was allocatingand freeing temporaries and lexicals from.

  • panic: pad_free po

    (P) An invalid scratch pad offset was detected internally.

  • panic: pad_reset curpad, %p!=%p

    (P) The compiler got confused about which scratch pad it was allocatingand freeing temporaries and lexicals from.

  • panic: pad_sv po

    (P) An invalid scratch pad offset was detected internally.

  • panic: pad_swipe curpad, %p!=%p

    (P) The compiler got confused about which scratch pad it was allocatingand freeing temporaries and lexicals from.

  • panic: pad_swipe po

    (P) An invalid scratch pad offset was detected internally.

  • panic: pp_iter, type=%u

    (P) The foreach iterator got called in a non-loop context frame.

  • panic: pp_match%s

    (P) The internal pp_match() routine was called with invalid operationaldata.

  • panic: pp_split, pm=%p, s=%p

    (P) Something terrible went wrong in setting up for the split.

  • panic: realloc, %s

    (P) Something requested a negative number of bytes of realloc.

  • panic: reference miscount on nsv in sv_replace() (%d != 1)

    (P) The internal sv_replace() function was handed a new SV with areference count other than 1.

  • panic: restartop in %s

    (P) Some internal routine requested a goto (or something like it), anddidn't supply the destination.

  • panic: return, type=%u

    (P) We popped the context stack to a subroutine or eval context, andthen discovered it wasn't a subroutine or eval context.

  • panic: scan_num, %s

    (P) scan_num() got called on something that wasn't a number.

  • panic: sv_chop %s

    (P) The sv_chop() routine was passed a position that is not within thescalar's string buffer.

  • panic: sv_insert, midend=%p, bigend=%p

    (P) The sv_insert() routine was told to remove more string than therewas string.

  • panic: strxfrm() gets absurd - a => %u, ab => %u

    (P) The interpreter's sanity check of the C function strxfrm() failed.In your current locale the returned transformation of the string "ab" isshorter than that of the string "a", which makes no sense.

  • panic: top_env

    (P) The compiler attempted to do a goto, or something weird like that.

  • panic: unimplemented op %s (#%d) called

    (P) The compiler is screwed up and attempted to use an op that isn'tpermitted at run time.

  • panic: utf16_to_utf8: odd bytelen

    (P) Something tried to call utf16_to_utf8 with an odd (as opposedto even) byte length.

  • panic: utf16_to_utf8_reversed: odd bytelen

    (P) Something tried to call utf16_to_utf8_reversed with an odd (as opposedto even) byte length.

  • panic: yylex, %s

    (P) The lexer got into a bad state while processing a case modifier.

  • Parsing code internal error (%s)

    (F) Parsing code supplied by an extension violated the parser's API ina detectable way.

  • Pattern subroutine nesting without pos change exceeded limit in regex; marked by <-- HERE in m/%s/

    (F) You used a pattern that uses too many nested subpattern calls withoutconsuming any text. Restructure the pattern so text is consumed beforethe nesting limit is exceeded.

    The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • Parentheses missing around "%s" list

    (W parenthesis) You said something like

    1. my $foo, $bar = @_;

    when you meant

    1. my ($foo, $bar) = @_;

    Remember that "my", "our", "local" and "state" bind tighter than comma.

  • -p destination: %s

    (F) An error occurred during the implicit output invoked by the -pcommand-line switch. (This output goes to STDOUT unless you'veredirected it with select().)

  • (perhaps you forgot to load "%s"?)

    (F) This is an educated guess made in conjunction with the message"Can't locate object method \"%s\" via package \"%s\"". It often meansthat a method requires a package that has not been loaded.

  • Perl folding rules are not up-to-date for 0x%x; please use the perlbug utility to report

    (W regex, deprecated) You used a regular expression withcase-insensitive matching, and there is a bug in Perl in which thebuilt-in regular expression folding rules are not accurate. This maylead to incorrect results. Please report this as a bug using the"perlbug" utility. (This message is marked deprecated, so that it bydefault will be turned-on.)

  • Perl_my_%s() not available

    (F) Your platform has very uncommon byte-order and integer size,so it was not possible to set up some or all fixed-width byte-orderconversion functions. This is only a problem when you're using the'<' or '>' modifiers in (un)pack templates. See pack.

  • Perl %s required (did you mean %s?)--this is only %s, stopped

    (F) The code you are trying to run has asked for a newer version ofPerl than you are running. Perhaps use 5.10 was written insteadof use 5.010 or use v5.10. Without the leading v, the number isinterpreted as a decimal, with every three digits after thedecimal point representing a part of the version number. So 5.10is equivalent to v5.100.

  • Perl %s required--this is only version %s, stopped

    (F) The module in question uses features of a version of Perl morerecent than the currently running version. How long has it been sinceyou upgraded, anyway? See require.

  • PERL_SH_DIR too long

    (F) An error peculiar to OS/2. PERL_SH_DIR is the directory to find thesh-shell in. See "PERL_SH_DIR" in perlos2.

  • PERL_SIGNALS illegal: "%s"

    See PERL_SIGNALS in perlrun for legal values.

  • Perls since %s too modern--this is %s, stopped

    (F) The code you are trying to run claims it will not runon the version of Perl you are using because it is too new.Maybe the code needs to be updated, or maybe it is simplywrong and the version check should just be removed.

  • perl: warning: Setting locale failed.

    (S) The whole warning message will look something like:

    1. perl: warning: Setting locale failed.
    2. perl: warning: Please check that your locale settings:
    3. LC_ALL = "En_US",
    4. LANG = (unset)
    5. are supported and installed on your system.
    6. perl: warning: Falling back to the standard locale ("C").

    Exactly what were the failed locale settings varies. In the above thesettings were that the LC_ALL was "En_US" and the LANG had no value.This error means that Perl detected that you and/or your operatingsystem supplier and/or system administrator have set up the so-calledlocale system but Perl could not use those settings. This was notdead serious, fortunately: there is a "default locale" called "C" thatPerl can and will use, and the script will be run. Before you reallyfix the problem, however, you will get the same error message eachtime you run Perl. How to really fix the problem can be found inperllocale section LOCALE PROBLEMS.

  • pid %x not a child

    (W exec) A warning peculiar to VMS. Waitpid() was asked to wait for aprocess which isn't a subprocess of the current process. While this isfine from VMS' perspective, it's probably not what you intended.

  • 'P' must have an explicit size in unpack

    (F) The unpack format P must have an explicit size, not "*".

  • POSIX class [:%s:] unknown in regex; marked by <-- HERE in m/%s/

    (F) The class in the character class [: :] syntax is unknown. The <-- HEREshows in the regular expression about where the problem was discovered.Note that the POSIX character classes do not have the is prefixthe corresponding C interfaces have: in other words, it's [[:print:]],not isprint. See perlre.

  • POSIX getpgrp can't take an argument

    (F) Your system has POSIX getpgrp(), which takes no argument, unlikethe BSD version, which takes a pid.

  • POSIX syntax [%s] belongs inside character classes in regex; marked by <-- HERE in m/%s/

    (W regexp) The character class constructs [: :], [= =], and [. .] goinside character classes, the [] are part of the construct, for example:/[012[:alpha:]345]/. Note that [= =] and [. .] are not currentlyimplemented; they are simply placeholders for future extensions and willcause fatal errors. The <-- HERE shows in the regular expression aboutwhere the problem was discovered. See perlre.

  • POSIX syntax [. .] is reserved for future extensions in regex; marked by <-- HERE in m/%s/

    (F regexp) Within regular expression character classes ([]) the syntaxbeginning with "[." and ending with ".]" is reserved for future extensions.If you need to represent those character sequences inside a regularexpression character class, just quote the square brackets with thebackslash: "\[." and ".\]". The <-- HERE shows in the regular expressionabout where the problem was discovered. See perlre.

  • POSIX syntax [= =] is reserved for future extensions in regex; marked by <-- HERE in m/%s/

    (F) Within regular expression character classes ([]) the syntax beginningwith "[=" and ending with "=]" is reserved for future extensions. If youneed to represent those character sequences inside a regular expressioncharacter class, just quote the square brackets with the backslash: "\[="and "=\]". The <-- HERE shows in the regular expression about where theproblem was discovered. See perlre.

  • Possible attempt to put comments in qw() list

    (W qw) qw() lists contain items separated by whitespace; as with literalstrings, comment characters are not ignored, but are instead treated asliteral data. (You may have used different delimiters than theparentheses shown here; braces are also frequently used.)

    You probably wrote something like this:

    1. @list = qw(
    2. a # a comment
    3. b # another comment
    4. );

    when you should have written this:

    1. @list = qw(
    2. a
    3. b
    4. );

    If you really want comments, build your list theold-fashioned way, with quotes and commas:

    1. @list = (
    2. 'a', # a comment
    3. 'b', # another comment
    4. );
  • Possible attempt to separate words with commas

    (W qw) qw() lists contain items separated by whitespace; thereforecommas aren't needed to separate the items. (You may have useddifferent delimiters than the parentheses shown here; braces are alsofrequently used.)

    You probably wrote something like this:

    1. qw! a, b, c !;

    which puts literal commas into some of the list items. Write it withoutcommas if you don't want them to appear in your data:

    1. qw! a b c !;
  • Possible memory corruption: %s overflowed 3rd argument

    (F) An ioctl() or fcntl() returned more than Perl was bargaining for.Perl guesses a reasonable buffer size, but puts a sentinel byte at theend of the buffer just in case. This sentinel byte got clobbered, andPerl assumes that memory is now corrupted. See ioctl.

  • Possible precedence problem on bitwise %c operator

    (W precedence) Your program uses a bitwise logical operator in conjunctionwith a numeric comparison operator, like this :

    1. if ($x & $y == 0) { ... }

    This expression is actually equivalent to $x & ($y == 0), due to thehigher precedence of ==. This is probably not what you want. (If youreally meant to write this, disable the warning, or, better, put theparentheses explicitly and write $x & ($y == 0)).

  • Possible unintended interpolation of $\ in regex

    (W ambiguous) You said something like m/$\/ in a regex.The regex m/foo$\s+bar/m translates to: match the word 'foo', the outputrecord separator (see $\ in perlvar) and the letter 's' (one time or more)followed by the word 'bar'.

    If this is what you intended then you can silence the warning by using m/${\}/ (for example: m/foo${\}s+bar/).

    If instead you intended to match the word 'foo' at the end of the linefollowed by whitespace and the word 'bar' on the next line then you can usem/$(?)\/ (for example: m/foo$(?)\s+bar/).

  • Possible unintended interpolation of %s in string

    (W ambiguous) You said something like '@foo' in a double-quoted stringbut there was no array @foo in scope at the time. If you wanted aliteral @foo, then write it as \@foo; otherwise find out what happenedto the array you apparently lost track of.

  • Precedence problem: open %s should be open(%s)

    (S precedence) The old irregular construct

    1. open FOO || die;

    is now misinterpreted as

    1. open(FOO || die);

    because of the strict regularization of Perl 5's grammar into unary andlist operators. (The old open was a little of both.) You must putparentheses around the filehandle, or use the new "or" operator insteadof "||".

  • Premature end of script headers

    See Server error.

  • printf() on closed filehandle %s

    (W closed) The filehandle you're writing to got itself closed sometimebefore now. Check your control flow.

  • print() on closed filehandle %s

    (W closed) The filehandle you're printing on got itself closed sometimebefore now. Check your control flow.

  • Process terminated by SIG%s

    (W) This is a standard message issued by OS/2 applications, while *nixapplications die in silence. It is considered a feature of the OS/2port. One can easily disable this by appropriate sighandlers, seeSignals in perlipc. See also "Process terminated by SIGTERM/SIGINT"in perlos2.

  • Prototype after '%c' for %s : %s

    (W illegalproto) A character follows % or @ in a prototype. This isuseless, since % and @ gobble the rest of the subroutine arguments.

  • Prototype mismatch: %s vs %s

    (S prototype) The subroutine being declared or defined had previously beendeclared or defined with a different function prototype.

  • Prototype not terminated

    (F) You've omitted the closing parenthesis in a function prototypedefinition.

  • \p{} uses Unicode rules, not locale rules

    (W) You compiled a regular expression that contained a Unicode propertymatch (\p or \P), but the regular expression is also being told touse the run-time locale, not Unicode. Instead, use a POSIX characterclass, which should know about the locale's rules.(See POSIX Character Classes in perlrecharclass.)

    Even if the run-time locale is ISO 8859-1 (Latin1), which is a subset ofUnicode, some properties will give results that are not valid for thatsubset.

    Here are a couple of examples to help you see what's going on. If thelocale is ISO 8859-7, the character at code point 0xD7 is the "GREEKCAPITAL LETTER CHI". But in Unicode that code point means the"MULTIPLICATION SIGN" instead, and \p always uses the Unicodemeaning. That means that \p{Alpha} won't match, but [[:alpha:]]should. Only in the Latin1 locale are all the characters in the samepositions as they are in Unicode. But, even here, some properties giveincorrect results. An example is \p{Changes_When_Uppercased} whichis true for "LATIN SMALL LETTER Y WITH DIAERESIS", but since the uppercase of that character is not in Latin1, in that locale it doesn'tchange when upper cased.

  • Quantifier follows nothing in regex; marked by <-- HERE in m/%s/

    (F) You started a regular expression with a quantifier. Backslash it ifyou meant it literally. The <-- HERE shows in the regular expressionabout where the problem was discovered. See perlre.

  • Quantifier in {,} bigger than %d in regex; marked by <-- HERE in m/%s/

    (F) There is currently a limit to the size of the min and max values ofthe {min,max} construct. The <-- HERE shows in the regular expressionabout where the problem was discovered. See perlre.

  • Quantifier unexpected on zero-length expression; marked by <-- HERE in m/%s/

    (W regexp) You applied a regular expression quantifier in a place whereit makes no sense, such as on a zero-width assertion. Try putting thequantifier inside the assertion instead. For example, the way to match"abc" provided that it is followed by three repetitions of "xyz" is/abc(?=(?:xyz){3})/, not /abc(?=xyz){3}/.

    The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • Range iterator outside integer range

    (F) One (or both) of the numeric arguments to the range operator ".."are outside the range which can be represented by integers internally.One possible workaround is to force Perl to use magical string incrementby prepending "0" to your numbers.

  • readdir() attempted on invalid dirhandle %s

    (W io) The dirhandle you're reading from is either closed or not reallya dirhandle. Check your control flow.

  • readline() on closed filehandle %s

    (W closed) The filehandle you're reading from got itself closed sometimebefore now. Check your control flow.

  • read() on closed filehandle %s

    (W closed) You tried to read from a closed filehandle.

  • read() on unopened filehandle %s

    (W unopened) You tried to read from a filehandle that was never opened.

  • Reallocation too large: %x

    (F) You can't allocate more than 64K on an MS-DOS machine.

  • realloc() of freed memory ignored

    (S malloc) An internal routine called realloc() on something that hadalready been freed.

  • Recompile perl with -DDEBUGGING to use -D switch

    (F debugging) You can't use the -D option unless the code to producethe desired output is compiled into Perl, which entails some overhead,which is why it's currently left out of your copy.

  • Recursive call to Perl_load_module in PerlIO_find_layer

    (P) It is currently not permitted to load modules when creatinga filehandle inside an %INC hook. This can happen with open my$fh, '<', \$scalar, which implicitly loads PerlIO::scalar. Tryloading PerlIO::scalar explicitly first.

  • Recursive inheritance detected in package '%s'

    (F) While calculating the method resolution order (MRO) of a package, Perlbelieves it found an infinite loop in the @ISA hierarchy. This is acrude check that bails out after 100 levels of @ISA depth.

  • refcnt_dec: fd %d%s
  • refcnt: fd %d%s
  • refcnt_inc: fd %d%s

    (P) Perl's I/O implementation failed an internal consistency check. Ifyou see this message, something is very wrong.

  • Reference found where even-sized list expected

    (W misc) You gave a single reference where Perl was expecting a listwith an even number of elements (for assignment to a hash). Thisusually means that you used the anon hash constructor when you meantto use parens. In any case, a hash requires key/value pairs.

    1. %hash = { one => 1, two => 2, };# WRONG
    2. %hash = [ qw/ an anon array / ];# WRONG
    3. %hash = ( one => 1, two => 2, );# right
    4. %hash = qw( one 1 two 2 );# also fine
  • Reference is already weak

    (W misc) You have attempted to weaken a reference that is already weak.Doing so has no effect.

  • Reference to invalid group 0

    (F) You used \g0 or similar in a regular expression. You may referto capturing parentheses only with strictly positive integers(normal backreferences) or with strictly negative integers (relativebackreferences). Using 0 does not make sense.

  • Reference to nonexistent group in regex; marked by <-- HERE in m/%s/

    (F) You used something like \7 in your regular expression, but there arenot at least seven sets of capturing parentheses in the expression. Ifyou wanted to have the character with ordinal 7 inserted into the regularexpression, prepend zeroes to make it three digits long: \007

    The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • Reference to nonexistent named group in regex; marked by <-- HERE in m/%s/

    (F) You used something like \k'NAME' or \k<NAME> in your regularexpression, but there is no corresponding named capturing parenthesessuch as (?'NAME'...) or (?<NAME>...). Check if the name has beenspelled correctly both in the backreference and the declaration.

    The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • Reference to nonexistent or unclosed group in regex; marked by <-- HERE in m/%s/

    (F) You used something like \g{-7} in your regular expression, but thereare not at least seven sets of closed capturing parentheses in theexpression before where the \g{-7} was located.

    The <-- HERE shows in the regular expression about where the problem wasdiscovered.

  • regexp memory corruption

    (P) The regular expression engine got confused by what the regularexpression compiler gave it.

  • Regexp modifier "/%c" may appear a maximum of twice
  • Regexp modifier "/%c" may not appear twice

    (F syntax, regexp) The regular expression pattern had too many occurrencesof the specified modifier. Remove the extraneous ones.

  • Regexp modifier "%c" may not appear after the "-"

    (F regexp) Turning off the given modifier has the side effect of turningon another one. Perl currently doesn't allow this. Reword the regularexpression to use the modifier you want to turn on (and place it beforethe minus), instead of the one you want to turn off.

  • Regexp modifiers "/%c" and "/%c" are mutually exclusive

    (F syntax, regexp) The regular expression pattern had more than one of thesemutually exclusive modifiers. Retain only the modifier that issupposed to be there.

  • Regexp out of space

    (P) A "can't happen" error, because safemalloc() should have caught itearlier.

  • Repeated format line will never terminate (~~ and @# incompatible)

    (F) Your format contains the ~~ repeat-until-blank sequence and anumeric field that will never go blank so that the repetition neverterminates. You might use ^# instead. See perlform.

  • Replacement list is longer than search list

    (W misc) You have used a replacement list that is longer than thesearch list. So the additional elements in the replacement listare meaningless.

  • Reversed %s= operator

    (W syntax) You wrote your assignment operator backwards. The = mustalways come last, to avoid ambiguity with subsequent unary operators.

  • rewinddir() attempted on invalid dirhandle %s

    (W io) The dirhandle you tried to do a rewinddir() on is either closed or notreally a dirhandle. Check your control flow.

  • Scalars leaked: %d

    (P) Something went wrong in Perl's internal bookkeeping of scalars:not all scalar variables were deallocated by the time Perl exited.What this usually indicates is a memory leak, which is of course bad,especially if the Perl program is intended to be long-running.

  • Scalar value @%s[%s] better written as $%s[%s]

    (W syntax) You've used an array slice (indicated by @) to select asingle element of an array. Generally it's better to ask for a scalarvalue (indicated by $). The difference is that $foo[&bar] alwaysbehaves like a scalar, both when assigning to it and when evaluating itsargument, while @foo[&bar] behaves like a list when you assign to it,and provides a list context to its subscript, which can do weird thingsif you're expecting only one subscript.

    On the other hand, if you were actually hoping to treat the arrayelement as a list, you need to look into how references work, becausePerl will not magically convert between scalars and lists for you. Seeperlref.

  • Scalar value @%s{%s} better written as $%s{%s}

    (W syntax) You've used a hash slice (indicated by @) to select a singleelement of a hash. Generally it's better to ask for a scalar value(indicated by $). The difference is that $foo{&bar} always behaveslike a scalar, both when assigning to it and when evaluating itsargument, while @foo{&bar} behaves like a list when you assign to it,and provides a list context to its subscript, which can do weird thingsif you're expecting only one subscript.

    On the other hand, if you were actually hoping to treat the hash elementas a list, you need to look into how references work, because Perl willnot magically convert between scalars and lists for you. Seeperlref.

  • Search pattern not terminated

    (F) The lexer couldn't find the final delimiter of a // or m{}construct. Remember that bracketing delimiters count nesting level.Missing the leading $ from a variable $m may cause this error.

    Note that since Perl 5.9.0 a // can also be the defined-orconstruct, not just the empty search pattern. Therefore code writtenin Perl 5.9.0 or later that uses the // as the defined-or can bemisparsed by pre-5.9.0 Perls as a non-terminated search pattern.

  • Search pattern not terminated or ternary operator parsed as search pattern

    (F) The lexer couldn't find the final delimiter of a ?PATTERN?construct.

    The question mark is also used as part of the ternary operator (as infoo ? 0 : 1) leading to some ambiguous constructions being wronglyparsed. One way to disambiguate the parsing is to put parentheses aroundthe conditional expression, i.e. (foo) ? 0 : 1.

  • seekdir() attempted on invalid dirhandle %s

    (W io) The dirhandle you are doing a seekdir() on is either closed or notreally a dirhandle. Check your control flow.

  • %sseek() on unopened filehandle

    (W unopened) You tried to use the seek() or sysseek() function on afilehandle that was either never opened or has since been closed.

  • select not implemented

    (F) This machine doesn't implement the select() system call.

  • Self-ties of arrays and hashes are not supported

    (F) Self-ties are of arrays and hashes are not supported inthe current implementation.

  • Semicolon seems to be missing

    (W semicolon) A nearby syntax error was probably caused by a missingsemicolon, or possibly some other missing operator, such as a comma.

  • semi-panic: attempt to dup freed string

    (S internal) The internal newSVsv() routine was called to duplicate ascalar that had previously been marked as free.

  • sem%s not implemented

    (F) You don't have System V semaphore IPC on your system.

  • send() on closed socket %s

    (W closed) The socket you're sending to got itself closed sometimebefore now. Check your control flow.

  • Sequence (? incomplete in regex; marked by <-- HERE in m/%s/

    (F) A regular expression ended with an incomplete extension (?. The<-- HERE shows in the regular expression about where the problem wasdiscovered. See perlre.

  • Sequence (?%s...) not implemented in regex; marked by <-- HERE in m/%s/

    (F) A proposed regular expression extension has the character reservedbut has not yet been written. The <-- HERE shows in the regularexpression about where the problem was discovered. See perlre.

  • Sequence (?%s...) not recognized in regex; marked by <-- HERE in m/%s/

    (F) You used a regular expression extension that doesn't make sense. The<-- HERE shows in the regular expression about where the problem wasdiscovered. This happens when using the (?^...) construct to tellPerl to use the default regular expression modifiers, and youredundantly specify a default modifier. For othercauses, see perlre.

  • Sequence \%s... not terminated in regex; marked by <-- HERE in m/%s/

    (F) The regular expression expects a mandatory argument following the escapesequence and this has been omitted or incorrectly written.

  • Sequence (?#... not terminated in regex; marked by <-- HERE in m/%s/

    (F) A regular expression comment must be terminated by a closingparenthesis. Embedded parentheses aren't allowed. The <-- HERE shows inthe regular expression about where the problem was discovered. Seeperlre.

  • Sequence (?{...}) not terminated or not {}-balanced in regex; marked by <-- HERE in m/%s/

    (F) If the contents of a (?{...}) clause contain braces, theymust balance for Perl to detect the end of the clause properly.The <-- HERE shows in the regular expression about where theproblem was discovered. See perlre.

  • 500 Server error

    See Server error.

  • Server error

    (A) This is the error message generally seen in a browser windowwhen trying to run a CGI program (including SSI) over the web. Theactual error text varies widely from server to server. The mostfrequently-seen variants are "500 Server error", "Method (something)not permitted", "Document contains no data", "Premature end of scriptheaders", and "Did not produce a valid header".

    This is a CGI error, not a Perl error.

    You need to make sure your script is executable, is accessible bythe user CGI is running the script under (which is probably not theuser account you tested it under), does not rely on any environmentvariables (like PATH) from the user it isn't running under, and isn'tin a location where the CGI server can't find it, basically, more orless. Please see the following for more information:

    1. http://www.perl.org/CGI_MetaFAQ.html
    2. http://www.htmlhelp.org/faq/cgifaq.html
    3. http://www.w3.org/Security/Faq/

    You should also look at perlfaq9.

  • setegid() not implemented

    (F) You tried to assign to $), and your operating system doesn'tsupport the setegid() system call (or equivalent), or at least Configuredidn't think so.

  • seteuid() not implemented

    (F) You tried to assign to $>, and your operating system doesn'tsupport the seteuid() system call (or equivalent), or at least Configuredidn't think so.

  • setpgrp can't take arguments

    (F) Your system has the setpgrp() from BSD 4.2, which takes noarguments, unlike POSIX setpgid(), which takes a process ID and processgroup ID.

  • setrgid() not implemented

    (F) You tried to assign to $(, and your operating system doesn'tsupport the setrgid() system call (or equivalent), or at least Configuredidn't think so.

  • setruid() not implemented

    (F) You tried to assign to $<, and your operating system doesn'tsupport the setruid() system call (or equivalent), or at least Configuredidn't think so.

  • setsockopt() on closed socket %s

    (W closed) You tried to set a socket option on a closed socket. Did youforget to check the return value of your socket() call? Seesetsockopt.

  • shm%s not implemented

    (F) You don't have System V shared memory IPC on your system.

  • !=~ should be !~

    (W syntax) The non-matching operator is !~, not !=~. !=~ will beinterpreted as the != (numeric not equal) and ~ (1's complement)operators: probably not what you intended.

  • <> should be quotes

    (F) You wrote require <file> when you should have writtenrequire 'file'.

  • /%s/ should probably be written as "%s"

    (W syntax) You have used a pattern where Perl expected to find a string,as in the first argument to join. Perl will treat the true or falseresult of matching the pattern against $_ as the string, which isprobably not what you had in mind.

  • shutdown() on closed socket %s

    (W closed) You tried to do a shutdown on a closed socket. Seems a bitsuperfluous.

  • SIG%s handler "%s" not defined

    (W signal) The signal handler named in %SIG doesn't, in fact, exist.Perhaps you put it into the wrong package?

  • Smart matching a non-overloaded object breaks encapsulation

    (F) You should not use the ~~ operator on an object that does notoverload it: Perl refuses to use the object's underlying structure forthe smart match.

  • sort is now a reserved word

    (F) An ancient error message that almost nobody ever runs into anymore.But before sort was a keyword, people sometimes used it as a filehandle.

  • Sort subroutine didn't return single value

    (F) A sort comparison subroutine may not return a list value with moreor less than one element. See sort.

  • Source filters apply only to byte streams

    (F) You tried to activate a source filter (usually by loading asource filter module) within a string passed to eval. This isnot permitted under the unicode_eval feature. Consider usingevalbytes instead. See feature.

  • splice() offset past end of array

    (W misc) You attempted to specify an offset that was past the end ofthe array passed to splice(). Splicing will instead commence at theend of the array, rather than past it. If this isn't what you want,try explicitly pre-extending the array by assigning $#array = $offset.See splice.

  • Split loop

    (P) The split was looping infinitely. (Obviously, a split shouldn'titerate more times than there are characters of input, which is whathappened.) See split.

  • Statement unlikely to be reached

    (W exec) You did an exec() with some statement after it other than adie(). This is almost always an error, because exec() never returnsunless there was a failure. You probably wanted to use system()instead, which does return. To suppress this warning, put the exec() ina block by itself.

  • "state" variable %s can't be in a package

    (F) Lexically scoped variables aren't in a package, so it doesn't makesense to try to declare one with a package qualifier on the front. Uselocal() if you want to localize a package variable.

  • stat() on unopened filehandle %s

    (W unopened) You tried to use the stat() function on a filehandle thatwas either never opened or has since been closed.

  • Stub found while resolving method "%s" overloading "%s" in package "%s"

    (P) Overloading resolution over @ISA tree may be broken by importationstubs. Stubs should never be implicitly created, but explicit calls tocan may break this.

  • Subroutine %s redefined

    (W redefine) You redefined a subroutine. To suppress this warning, say

    1. {
    2. no warnings 'redefine';
    3. eval "sub name { ... }";
    4. }
  • Substitution loop

    (P) The substitution was looping infinitely. (Obviously, a substitutionshouldn't iterate more times than there are characters of input, whichis what happened.) See the discussion of substitution inRegexp Quote-Like Operators in perlop.

  • Substitution pattern not terminated

    (F) The lexer couldn't find the interior delimiter of an s/// or s{}{}construct. Remember that bracketing delimiters count nesting level.Missing the leading $ from variable $s may cause this error.

  • Substitution replacement not terminated

    (F) The lexer couldn't find the final delimiter of an s/// or s{}{}construct. Remember that bracketing delimiters count nesting level.Missing the leading $ from variable $s may cause this error.

  • substr outside of string

    (W substr)(F) You tried to reference a substr() that pointed outside ofa string. That is, the absolute value of the offset was larger than thelength of the string. See substr. This warning is fatal ifsubstr is used in an lvalue context (as the left hand side of anassignment or as a subroutine argument for example).

  • sv_upgrade from type %d down to type %d

    (P) Perl tried to force the upgrade of an SV to a type which was actuallyinferior to its current type.

  • Switch (?(condition)... contains too many branches in regex; marked by <-- HERE in m/%s/

    (F) A (?(condition)if-clause|else-clause) construct can have at mosttwo branches (the if-clause and the else-clause). If you want one orboth to contain alternation, such as using this|that|other, encloseit in clustering parentheses:

    1. (?(condition)(?:this|that|other)|else-clause)

    The <-- HERE shows in the regular expression about where the problemwas discovered. See perlre.

  • Switch condition not recognized in regex; marked by <-- HERE in m/%s/

    (F) If the argument to the (?(...)if-clause|else-clause) construct isa number, it can be only a number. The <-- HERE shows in the regularexpression about where the problem was discovered. See perlre.

  • switching effective %s is not implemented

    (F) While under the use filetest pragma, we cannot switch the realand effective uids or gids.

  • %s syntax OK

    (F) The final summary message when a perl -c succeeds.

  • syntax error

    (F) Probably means you had a syntax error. Common reasons include:

    1. A keyword is misspelled.
    2. A semicolon is missing.
    3. A comma is missing.
    4. An opening or closing parenthesis is missing.
    5. An opening or closing brace is missing.
    6. A closing quote is missing.

    Often there will be another error message associated with the syntaxerror giving more information. (Sometimes it helps to turn on -w.)The error message itself often tells you where it was in the line whenit decided to give up. Sometimes the actual error is several tokensbefore this, because Perl is good at understanding random input.Occasionally the line number may be misleading, and once in a blue moonthe only way to figure out what's triggering the error is to callperl -c repeatedly, chopping away half the program each time to seeif the error went away. Sort of the cybernetic version of 20 questions.

  • syntax error at line %d: '%s' unexpected

    (A) You've accidentally run your script through the Bourne shell insteadof Perl. Check the #! line, or manually feed your script into Perlyourself.

  • syntax error in file %s at line %d, next 2 tokens "%s"

    (F) This error is likely to occur if you run a perl5 script througha perl4 interpreter, especially if the next 2 tokens are "use strict"or "my $var" or "our $var".

  • sysread() on closed filehandle %s

    (W closed) You tried to read from a closed filehandle.

  • sysread() on unopened filehandle %s

    (W unopened) You tried to read from a filehandle that was never opened.

  • System V %s is not implemented on this machine

    (F) You tried to do something with a function beginning with "sem","shm", or "msg" but that System V IPC is not implemented in yourmachine. In some machines the functionality can exist but beunconfigured. Consult your system support.

  • syswrite() on closed filehandle %s

    (W closed) The filehandle you're writing to got itself closed sometimebefore now. Check your control flow.

  • -T and -B not implemented on filehandles

    (F) Perl can't peek at the stdio buffer of filehandles when it doesn'tknow about your kind of stdio. You'll have to use a filename instead.

  • Target of goto is too deeply nested

    (F) You tried to use goto to reach a label that was too deeply nestedfor Perl to reach. Perl is doing you a favor by refusing.

  • telldir() attempted on invalid dirhandle %s

    (W io) The dirhandle you tried to telldir() is either closed or not reallya dirhandle. Check your control flow.

  • tell() on unopened filehandle

    (W unopened) You tried to use the tell() function on a filehandle thatwas either never opened or has since been closed.

  • That use of $[ is unsupported

    (F) Assignment to $[ is now strictly circumscribed, and interpretedas a compiler directive. You may say only one of

    1. $[ = 0;
    2. $[ = 1;
    3. ...
    4. local $[ = 0;
    5. local $[ = 1;
    6. ...

    This is to prevent the problem of one module changing the array base outfrom under another module inadvertently. See $[ in perlvar and arybase.

  • The crypt() function is unimplemented due to excessive paranoia

    (F) Configure couldn't find the crypt() function on your machine,probably because your vendor didn't supply it, probably because theythink the U.S. Government thinks it's a secret, or at least that theywill continue to pretend that it is. And if you quote me on that, Iwill deny it.

  • The %s function is unimplemented

    (F) The function indicated isn't implemented on this architecture, accordingto the probings of Configure.

  • The stat preceding %s wasn't an lstat

    (F) It makes no sense to test the current stat buffer for symboliclinkhood if the last stat that wrote to the stat buffer already wentpast the symlink to get to the real file. Use an actual filenameinstead.

  • The 'unique' attribute may only be applied to 'our' variables

    (F) This attribute was never supported on my or sub declarations.

  • This Perl can't reset CRTL environ elements (%s)
  • This Perl can't set CRTL environ elements (%s=%s)

    (W internal) Warnings peculiar to VMS. You tried to change or delete anelement of the CRTL's internal environ array, but your copy of Perlwasn't built with a CRTL that contained the setenv() function. You'llneed to rebuild Perl with a CRTL that does, or redefinePERL_ENV_TABLES (see perlvms) so that the environ array isn't thetarget of the change to%ENV which produced the warning.

  • thread failed to start: %s

    (W threads)(S) The entry point function of threads->create() failed for some reason.

  • times not implemented

    (F) Your version of the C library apparently doesn't do times(). Isuspect you're not running on Unix.

  • "-T" is on the #! line, it must also be used on the command line

    (X) The #! line (or local equivalent) in a Perl script containsthe -T option (or the -t option), but Perl was not invoked with-T in its command line. This is an error because, by the timePerl discovers a -T in a script, it's too late to properly tainteverything from the environment. So Perl gives up.

    If the Perl script is being executed as a command using the #!mechanism (or its local equivalent), this error can usually befixed by editing the #! line so that the -%c option is a part ofPerl's first argument: e.g. change perl -n -%c to perl -%c -n.

    If the Perl script is being executed as perl scriptname, then the-%c option must appear on the command line: perl -%c scriptname.

  • To%s: illegal mapping '%s'

    (F) You tried to define a customized To-mapping for lc(), lcfirst,uc(), or ucfirst() (or their string-inlined versions), but youspecified an illegal mapping.See User-Defined Character Properties in perlunicode.

  • Too deeply nested ()-groups

    (F) Your template contains ()-groups with a ridiculously deep nesting level.

  • Too few args to syscall

    (F) There has to be at least one argument to syscall() to specify thesystem call to call, silly dilly.

  • Too late for "-%s" option

    (X) The #! line (or local equivalent) in a Perl script contains the-M, -m or -C option.

    In the case of -M and -m, this is an error because those optionsare not intended for use inside scripts. Use the use pragma instead.

    The -C option only works if it is specified on the command line aswell (with the same sequence of letters or numbers following). Eitherspecify this option on the command line, or, if your system supportsit, make your script executable and run it directly instead of passingit to perl.

  • Too late to run %s block

    (W void) A CHECK or INIT block is being defined during run time proper,when the opportunity to run them has already passed. Perhaps you areloading a file with require or do when you should be using useinstead. Or perhaps you should put the require or do inside aBEGIN block.

  • Too many args to syscall

    (F) Perl supports a maximum of only 14 args to syscall().

  • Too many arguments for %s

    (F) The function requires fewer arguments than you specified.

  • Too many )'s

    (A) You've accidentally run your script through csh instead of Perl.Check the #! line, or manually feed your script into Perl yourself.

  • Too many ('s

    (A) You've accidentally run your script through csh instead of Perl.Check the #! line, or manually feed your script into Perl yourself.

  • Trailing \ in regex m/%s/

    (F) The regular expression ends with an unbackslashed backslash.Backslash it. See perlre.

  • Transliteration pattern not terminated

    (F) The lexer couldn't find the interior delimiter of a tr/// or tr[][]or y/// or y[][] construct. Missing the leading $ from variables$tr or $y may cause this error.

  • Transliteration replacement not terminated

    (F) The lexer couldn't find the final delimiter of a tr///, tr[][],y/// or y[][] construct.

  • '%s' trapped by operation mask

    (F) You tried to use an operator from a Safe compartment in which it'sdisallowed. See Safe.

  • truncate not implemented

    (F) Your machine doesn't implement a file truncation mechanism thatConfigure knows about.

  • Type of arg %d to &CORE::%s must be %s

    (F) The subroutine in question in the CORE package requires its argumentto be a hard reference to data of the specified type. Overloading isignored, so a reference to an object that is not the specified type, butnonetheless has overloading to handle it, will still not be accepted.

  • Type of arg %d to %s must be %s (not %s)

    (F) This function requires the argument in that position to be of acertain type. Arrays must be @NAME or @{EXPR}. Hashes must be%NAME or %{EXPR}. No implicit dereferencing is allowed--use the{EXPR} forms as an explicit dereference. See perlref.

  • Type of argument to %s must be unblessed hashref or arrayref

    (F) You called keys, values or each with a scalar argument thatwas not a reference to an unblessed hash or array.

  • umask not implemented

    (F) Your machine doesn't implement the umask function and you tried touse it to restrict permissions for yourself (EXPR & 0700).

  • Unable to create sub named "%s"

    (F) You attempted to create or access a subroutine with an illegal name.

  • Unbalanced context: %d more PUSHes than POPs

    (W internal) The exit code detected an internal inconsistency in howmany execution contexts were entered and left.

  • Unbalanced saves: %d more saves than restores

    (W internal) The exit code detected an internal inconsistency in howmany values were temporarily localized.

  • Unbalanced scopes: %d more ENTERs than LEAVEs

    (W internal) The exit code detected an internal inconsistency in howmany blocks were entered and left.

  • Unbalanced string table refcount: (%d) for "%s"

    (W internal) On exit, Perl found some strings remaining in the sharedstring table used for copy on write and for hash keys. The entriesshould have been freed, so this indicates a bug somewhere.

  • Unbalanced tmps: %d more allocs than frees

    (W internal) The exit code detected an internal inconsistency in howmany mortal scalars were allocated and freed.

  • Undefined format "%s" called

    (F) The format indicated doesn't seem to exist. Perhaps it's really inanother package? See perlform.

  • Undefined sort subroutine "%s" called

    (F) The sort comparison routine specified doesn't seem to exist.Perhaps it's in a different package? See sort.

  • Undefined subroutine &%s called

    (F) The subroutine indicated hasn't been defined, or if it was, it hassince been undefined.

  • Undefined subroutine called

    (F) The anonymous subroutine you're trying to call hasn't been defined,or if it was, it has since been undefined.

  • Undefined subroutine in sort

    (F) The sort comparison routine specified is declared but doesn't seemto have been defined yet. See sort.

  • Undefined top format "%s" called

    (F) The format indicated doesn't seem to exist. Perhaps it's really inanother package? See perlform.

  • Undefined value assigned to typeglob

    (W misc) An undefined value was assigned to a typeglob, a la*foo = undef. This does nothing. It's possible that you really meanundef *foo.

  • %s: Undefined variable

    (A) You've accidentally run your script through csh instead of Perl.Check the #! line, or manually feed your script into Perl yourself.

  • unexec of %s into %s failed!

    (F) The unexec() routine failed for some reason. See your local FSFrepresentative, who probably put it there in the first place.

  • Unexpected constant lvalue entersub entry via type/targ %d:%d

    (P) When compiling a subroutine call in lvalue context, Perl failed aninternal consistency check. It encountered a malformed op tree.

  • Unicode non-character U+%X is illegal for open interchange

    (W utf8, nonchar) Certain codepoints, such as U+FFFE and U+FFFF, aredefined by the Unicode standard to be non-characters. Those arelegal codepoints, but are reserved for internal use; so, applicationsshouldn't attempt to exchange them. If you know what you are doingyou can turn off this warning by no warnings 'nonchar';.

  • Unicode surrogate U+%X is illegal in UTF-8

    (W utf8, surrogate) You had a UTF-16 surrogate in a context where they arenot considered acceptable. These code points, between U+D800 andU+DFFF (inclusive), are used by Unicode only for UTF-16. However, Perlinternally allows all unsigned integer code points (up to the size limitavailable on your platform), including surrogates. But these can causeproblems when being input or output, which is likely where this messagecame from. If you really really know what you are doing you can turnoff this warning by no warnings 'surrogate';.

  • Unknown BYTEORDER

    (F) There are no byte-swapping functions for a machine with this byteorder.

  • Unknown error

    (P) Perl was about to print an error message in $@, but the $@ variabledid not exist, even after an attempt to create it.

  • Unknown open() mode '%s'

    (F) The second argument of 3-argument open() is not among the listof valid modes: <, >, >>, +<,+>, +>>, -|, |-, <&, >&.

  • Unknown PerlIO layer "%s"

    (W layer) An attempt was made to push an unknown layer onto the Perl I/Osystem. (Layers take care of transforming data between external andinternal representations.) Note that some layers, such as mmap,are not supported in all environments. If your program didn'texplicitly request the failing operation, it may be the result of thevalue of the environment variable PERLIO.

  • Unknown process %x sent message to prime_env_iter: %s

    (P) An error peculiar to VMS. Perl was reading values for %ENV beforeiterating over it, and someone else stuck a message in the stream ofdata Perl expected. Someone's very confused, or perhaps trying tosubvert Perl's population of %ENV for nefarious purposes.

  • Unknown "re" subpragma '%s' (known ones are: %s)

    (W) You tried to use an unknown subpragma of the "re" pragma.

  • Unknown switch condition (?(%s in regex; marked by <-- HERE in m/%s/

    (F) The condition part of a (?(condition)if-clause|else-clause) constructis not known. The condition must be one of the following:

    1. (1) (2) ... true if 1st, 2nd, etc., capture matched
    2. (<NAME>) ('NAME') true if named capture matched
    3. (?=...) (?<=...) true if subpattern matches
    4. (?!...) (?<!...) true if subpattern fails to match
    5. (?{ CODE }) true if code returns a true value
    6. (R) true if evaluating inside recursion
    7. (R1) (R2) ... true if directly inside capture group 1, 2, etc.
    8. (R&NAME) true if directly inside named capture
    9. (DEFINE) always false; for defining named subpatterns

    The <-- HERE shows in the regular expression about where the problem wasdiscovered. See perlre.

  • Unknown Unicode option letter '%c'

    (F) You specified an unknown Unicode option. See perlrun documentationof the -C switch for the list of known options.

  • Unknown Unicode option value %x

    (F) You specified an unknown Unicode option. See perlrun documentationof the -C switch for the list of known options.

  • Unknown verb pattern '%s' in regex; marked by <-- HERE in m/%s/

    (F) You either made a typo or have incorrectly put a * quantifierafter an open brace in your pattern. Check the pattern and reviewperlre for details on legal verb patterns.

  • Unknown warnings category '%s'

    (F) An error issued by the warnings pragma. You specified a warningscategory that is unknown to perl at this point.

    Note that if you want to enable a warnings category registered by amodule (e.g. use warnings 'File::Find'), you must have loaded thismodule first.

  • unmatched [ in regex; marked by <-- HERE in m/%s/

    (F) The brackets around a character class must match. If you wish toinclude a closing bracket in a character class, backslash it or put itfirst. The <-- HERE shows in the regular expression about where theproblem was discovered. See perlre.

  • unmatched ( in regex; marked by <-- HERE in m/%s/

    (F) Unbackslashed parentheses must always be balanced in regularexpressions. If you're a vi user, the % key is valuable for findingthe matching parenthesis. The <-- HERE shows in the regular expressionabout where the problem was discovered. See perlre.

  • Unmatched right %s bracket

    (F) The lexer counted more closing curly or square brackets than openingones, so you're probably missing a matching opening bracket. As ageneral rule, you'll find the missing one (so to speak) near the placeyou were last editing.

  • Unquoted string "%s" may clash with future reserved word

    (W reserved) You used a bareword that might someday be claimed as areserved word. It's best to put such a word in quotes, or capitalize itsomehow, or insert an underbar into it. You might also declare it as asubroutine.

  • Unrecognized character %s; marked by <-- HERE after %s near column %d

    (F) The Perl parser has no idea what to do with the specified characterin your Perl script (or eval) near the specified column. Perhaps you tried to run a compressed script, a binary program, or a directory as a Perl program.

  • Unrecognized escape \%c in character class passed through in regex; marked by <-- HERE in m/%s/

    (W regexp) You used a backslash-character combination which is notrecognized by Perl inside character classes. The character wasunderstood literally, but this may change in a future version of Perl.The <-- HERE shows in the regular expression about where theescape was discovered.

  • Unrecognized escape \%c passed through

    (W misc) You used a backslash-character combination which is notrecognized by Perl. The character was understood literally, but this maychange in a future version of Perl.

  • Unrecognized escape \%s passed through in regex; marked by <-- HERE in m/%s/

    (W regexp) You used a backslash-character combination which is notrecognized by Perl. The character(s) were understood literally, butthis may change in a future version of Perl. The <-- HERE shows inthe regular expression about where the escape was discovered.

  • Unrecognized signal name "%s"

    (F) You specified a signal name to the kill() function that was notrecognized. Say kill -l in your shell to see the valid signal nameson your system.

  • Unrecognized switch: -%s (-h will show valid options)

    (F) You specified an illegal option to Perl. Don't do that. (If youthink you didn't do that, check the #! line to see if it's supplying thebad switch on your behalf.)

  • Unsuccessful %s on filename containing newline

    (W newline) A file operation was attempted on a filename, and thatoperation failed, PROBABLY because the filename contained a newline,PROBABLY because you forgot to chomp() it off. See chomp.

  • Unsupported directory function "%s" called

    (F) Your machine doesn't support opendir() and readdir().

  • Unsupported function %s

    (F) This machine doesn't implement the indicated function, apparently.At least, Configure doesn't think so.

  • Unsupported function fork

    (F) Your version of executable does not support forking.

    Note that under some systems, like OS/2, there may be different flavorsof Perl executables, some of which may support fork, some not. Trychanging the name you call Perl by to perl_, perl__, and so on.

  • Unsupported script encoding %s

    (F) Your program file begins with a Unicode Byte Order Mark (BOM) whichdeclares it to be in a Unicode encoding that Perl cannot read.

  • Unsupported socket function "%s" called

    (F) Your machine doesn't support the Berkeley socket mechanism, or atleast that's what Configure thought.

  • Unterminated attribute list

    (F) The lexer found something other than a simple identifier at thestart of an attribute, and it wasn't a semicolon or the start of ablock. Perhaps you terminated the parameter list of the previousattribute too soon. See attributes.

  • Unterminated attribute parameter in attribute list

    (F) The lexer saw an opening (left) parenthesis character while parsingan attribute list, but the matching closing (right) parenthesischaracter was not found. You may need to add (or remove) a backslashcharacter to get your parentheses to balance. See attributes.

  • Unterminated compressed integer

    (F) An argument to unpack("w",...) was incompatible with the BERcompressed integer format and could not be converted to an integer.See pack.

  • Unterminated \g{...} pattern in regex; marked by <-- HERE in m/%s/

    (F) You missed a close brace on a \g{..} pattern (group reference) ina regular expression. Fix the pattern and retry.

  • Unterminated <> operator

    (F) The lexer saw a left angle bracket in a place where it was expectinga term, so it's looking for the corresponding right angle bracket, andnot finding it. Chances are you left some needed parentheses outearlier in the line, and you really meant a "less than".

  • Unterminated verb pattern argument in regex; marked by <-- HERE in m/%s/

    (F) You used a pattern of the form (*VERB:ARG) but did not terminatethe pattern with a ). Fix the pattern and retry.

  • Unterminated verb pattern in regex; marked by <-- HERE in m/%s/

    (F) You used a pattern of the form (*VERB) but did not terminatethe pattern with a ). Fix the pattern and retry.

  • untie attempted while %d inner references still exist

    (W untie) A copy of the object returned from tie (or tied) wasstill valid when untie was called.

  • Usage: POSIX::%s(%s)

    (F) You called a POSIX function with incorrect arguments.See FUNCTIONS in POSIX for more information.

  • Usage: Win32::%s(%s)

    (F) You called a Win32 function with incorrect arguments.See Win32 for more information.

  • $[ used in %s (did you mean $] ?)

    (W syntax) You used $[ in a comparison, such as:

    1. if ($[ > 5.006) {
    2. ...
    3. }

    You probably meant to use $] instead. $[ is the base for indexingarrays. $] is the Perl version number in decimal.

  • Useless assignment to a temporary

    (W misc) You assigned to an lvalue subroutine, but whatthe subroutine returned was a temporary scalar about tobe discarded, so the assignment had no effect.

  • Useless (?-%s) - don't use /%s modifier in regex; marked by <-- HERE in m/%s/

    (W regexp) You have used an internal modifier such as (?-o) that has nomeaning unless removed from the entire regexp:

    1. if ($string =~ /(?-o)$pattern/o) { ... }

    must be written as

    1. if ($string =~ /$pattern/) { ... }

    The <-- HERE shows in the regular expression aboutwhere the problem was discovered. See perlre.

  • Useless localization of %s

    (W syntax) The localization of lvalues such as local($x=10) is legal,but in fact the local() currently has no effect. This may change atsome point in the future, but in the meantime such code is discouraged.

  • Useless (?%s) - use /%s modifier in regex; marked by <-- HERE in m/%s/

    (W regexp) You have used an internal modifier such as (?o) that has nomeaning unless applied to the entire regexp:

    1. if ($string =~ /(?o)$pattern/) { ... }

    must be written as

    1. if ($string =~ /$pattern/o) { ... }

    The <-- HERE shows in the regular expression aboutwhere the problem was discovered. See perlre.

  • Useless use of /d modifier in transliteration operator

    (W misc) You have used the /d modifier where the searchlist has thesame length as the replacelist. See perlop for more informationabout the /d modifier.

  • Useless use of \E

    (W misc) You have a \E in a double-quotish string without a \U,\L or \Q preceding it.

  • Useless use of %s in void context

    (W void) You did something without a side effect in a context that doesnothing with the return value, such as a statement that doesn't return avalue from a block, or the left side of a scalar comma operator. Veryoften this points not to stupidity on your part, but a failure of Perlto parse your program the way you thought it would. For example, you'dget this if you mixed up your C precedence with Python precedence andsaid

    1. $one, $two = 1, 2;

    when you meant to say

    1. ($one, $two) = (1, 2);

    Another common error is to use ordinary parentheses to construct a listreference when you should be using square or curly brackets, forexample, if you say

    1. $array = (1,2);

    when you should have said

    1. $array = [1,2];

    The square brackets explicitly turn a list value into a scalar value,while parentheses do not. So when a parenthesized list is evaluated ina scalar context, the comma is treated like C's comma operator, whichthrows away the left argument, which is not what you want. Seeperlref for more on this.

    This warning will not be issued for numerical constants equal to 0 or 1since they are often used in statements like

    1. 1 while sub_with_side_effects();

    String constants that would normally evaluate to 0 or 1 are warnedabout.

  • Useless use of "re" pragma

    (W) You did use re; without any arguments. That isn't very useful.

  • Useless use of sort in scalar context

    (W void) You used sort in scalar context, as in :

    1. my $x = sort @y;

    This is not very useful, and perl currently optimizes this away.

  • Useless use of %s with no values

    (W syntax) You used the push() or unshift() function with no argumentsapart from the array, like push(@x) or unshift(@foo). That won'tusually have any effect on the array, so is completely useless. It'spossible in principle that push(@tied_array) could have some effectif the array is tied to a class which implements a PUSH method. If so,you can write it as push(@tied_array,()) to avoid this warning.

  • "use" not allowed in expression

    (F) The "use" keyword is recognized and executed at compile time, andreturns no useful value. See perlmod.

  • Use of assignment to $[ is deprecated

    (D deprecated) The $[ variable (index of the first element in an array)is deprecated. See $[ in perlvar.

  • Use of bare << to mean <<"" is deprecated

    (D deprecated) You are now encouraged to use the explicitly quotedform if you wish to use an empty line as the terminator of the here-document.

  • Use of comma-less variable list is deprecated

    (D deprecated) The values you give to a format should beseparated by commas, not just aligned on a line.

  • Use of chdir('') or chdir(undef) as chdir() deprecated

    (D deprecated) chdir() with no arguments is documented to change to$ENV{HOME} or $ENV{LOGDIR}. chdir(undef) and chdir('') share thisbehavior, but that has been deprecated. In future versions theywill simply fail.

    Be careful to check that what you pass to chdir() is defined and notblank, else you might find yourself in your home directory.

  • Use of /c modifier is meaningless in s///

    (W regexp) You used the /c modifier in a substitution. The /cmodifier is not presently meaningful in substitutions.

  • Use of /c modifier is meaningless without /g

    (W regexp) You used the /c modifier with a regex operand, but didn'tuse the /g modifier. Currently, /c is meaningful only when /g isused. (This may change in the future.)

  • Use of := for an empty attribute list is not allowed

    (F) The construction my $x := 42 used to parse as equivalent tomy $x : = 42 (applying an empty attribute list to $x).This construct was deprecated in 5.12.0, and has now been made a syntaxerror, so := can be reclaimed as a new operator in the future.

    If you need an empty attribute list, for example in a code generator, adda space before the =.

  • Use of freed value in iteration

    (F) Perhaps you modified the iterated array within the loop?This error is typically caused by code like the following:

    1. @a = (3,4);
    2. @a = () for (1,2,@a);

    You are not supposed to modify arrays while they are being iterated over.For speed and efficiency reasons, Perl internally does not do fullreference-counting of iterated items, hence deleting such an item in themiddle of an iteration causes Perl to see a freed value.

  • Use of *glob{FILEHANDLE} is deprecated

    (D deprecated) You are now encouraged to use the shorter *glob{IO} formto access the filehandle slot within a typeglob.

  • Use of /g modifier is meaningless in split

    (W regexp) You used the /g modifier on the pattern for a splitoperator. Since split always tries to match the patternrepeatedly, the /g has no effect.

  • Use of "goto" to jump into a construct is deprecated

    (D deprecated) Using goto to jump from an outer scope into an innerscope is deprecated and should be avoided.

  • Use of inherited AUTOLOAD for non-method %s() is deprecated

    (D deprecated) As an (ahem) accidental feature, AUTOLOADsubroutines are looked up as methods (using the @ISA hierarchy)even when the subroutines to be autoloaded were called as plainfunctions (e.g. Foo::bar()), not as methods (e.g. Foo->bar() or$obj->bar()).

    This bug will be rectified in future by using method lookup only formethods' AUTOLOADs. However, there is a significant base of existingcode that may be using the old behavior. So, as an interim step, Perlcurrently issues an optional warning when non-methods use inheritedAUTOLOADs.

    The simple rule is: Inheritance will not work when autoloadingnon-methods. The simple fix for old code is: In any module that usedto depend on inheriting AUTOLOAD for non-methods from a base classnamed BaseClass, execute *AUTOLOAD = \&BaseClass::AUTOLOAD duringstartup.

    In code that currently says use AutoLoader; @ISA = qw(AutoLoader);you should remove AutoLoader from @ISA and change use AutoLoader; touse AutoLoader 'AUTOLOAD';.

  • Use of %s in printf format not supported

    (F) You attempted to use a feature of printf that is accessible fromonly C. This usually means there's a better way to do it in Perl.

  • Use of %s is deprecated

    (D deprecated) The construct indicated is no longer recommended for use,generally because there's a better way to do it, and also because theold way has bad side effects.

  • Use of -l on filehandle %s

    (W io) A filehandle represents an opened file, and when you opened the fileit already went past any symlink you are presumably trying to look for.The operation returned undef. Use a filename instead.

  • Use of %s on a handle without * is deprecated

    (D deprecated) You used tie, tied or untie on a scalar but that scalarhappens to hold a typeglob, which means its filehandle will be tied. Ifyou mean to tie a handle, use an explicit * as in tie *$handle.

    This was a long-standing bug that was removed in Perl 5.16, as there wasno way to tie the scalar itself when it held a typeglob, and no way tountie a scalar that had had a typeglob assigned to it. If you see thismessage, you must be using an older version.

  • Use of ?PATTERN? without explicit operator is deprecated

    (D deprecated) You have written something like ?\w?, for a regularexpression that matches only once. Starting this term directly withthe question mark delimiter is now deprecated, so that the question markwill be available for use in new operators in the future. Write m?\w?instead, explicitly using the m operator: the question mark delimiterstill invokes match-once behaviour.

  • Use of qw(...) as parentheses is deprecated

    (D deprecated) You have something like foreach $x qw(a b c) {...},using a qw(...) list literal where a parenthesised expression isexpected. Historically the parser fooled itself into thinking thatqw(...) literals were always enclosed in parentheses, and as a resultyou could sometimes omit parentheses around them. (You could never dothe foreach qw(a b c) {...} that you might have expected, though.)The parser no longer lies to itself in this way. Wrap the list literalin parentheses, like foreach $x (qw(a b c)) {...}.

  • Use of reference "%s" as array index

    (W misc) You tried to use a reference as an array index; this probablyisn't what you mean, because references in numerical context tendto be huge numbers, and so usually indicates programmer error.

    If you really do mean it, explicitly numify your reference, like so:$array[0+$ref]. This warning is not given for overloaded objects,however, because you can overload the numification and stringificationoperators and then you presumably know what you are doing.

  • Use of reserved word "%s" is deprecated

    (D deprecated) The indicated bareword is a reserved word. Futureversions of perl may use it as a keyword, so you're better off eitherexplicitly quoting the word in a manner appropriate for its context ofuse, or using a different name altogether. The warning can besuppressed for subroutine names by either adding a & prefix, or usinga package qualifier, e.g. &our(), or Foo::our().

  • Use of tainted arguments in %s is deprecated

    (W taint, deprecated) You have supplied system() or exec() with multiplearguments and at least one of them is tainted. This used to be allowedbut will become a fatal error in a future version of perl. Untaint yourarguments. See perlsec.

  • Use of uninitialized value%s

    (W uninitialized) An undefined value was used as if it were alreadydefined. It was interpreted as a "" or a 0, but maybe it was a mistake.To suppress this warning assign a defined value to your variables.

    To help you figure out what was undefined, perl will try to tell youthe name of the variable (if any) that was undefined. In some casesit cannot do this, so it also tells you what operation you used theundefined value in. Note, however, that perl optimizes your programanid the operation displayed in the warning may not necessarily appearliterally in your program. For example, "that $foo" is usuallyoptimized into "that " . $foo, and the warning will refer to theconcatenation (.) operator, even though there is no . inyour program.

  • Using a hash as a reference is deprecated

    (D deprecated) You tried to use a hash as a reference, as in%foo->{"bar"} or %$ref->{"hello"}. Versions of perl <= 5.6.1used to allow this syntax, but shouldn't have. It is nowdeprecated, and will be removed in a future version.

  • Using an array as a reference is deprecated

    (D deprecated) You tried to use an array as a reference, as in@foo->[23] or @$ref->[99]. Versions of perl <= 5.6.1 used toallow this syntax, but shouldn't have. It is now deprecated,and will be removed in a future version.

  • Using just the first character returned by \N{} in character class

    (W) A charnames handler may return a sequence of more than one character.Currently all but the first one are discarded when used in a regularexpression pattern bracketed character class.

  • Using !~ with %s doesn't make sense

    (F) Using the !~ operator with s///r, tr///r or y///r iscurrently reserved for future use, as the exact behaviour has notbeen decided. (Simply returning the boolean opposite of themodified string is usually not particularly useful.)

  • UTF-16 surrogate U+%X

    (W utf8, surrogate) You had a UTF-16 surrogate in a context where they arenot considered acceptable. These code points, between U+D800 andU+DFFF (inclusive), are used by Unicode only for UTF-16. However, Perlinternally allows all unsigned integer code points (up to the size limitavailable on your platform), including surrogates. But these can causeproblems when being input or output, which is likely where this messagecame from. If you really really know what you are doing you can turnoff this warning by no warnings 'surrogate';.

  • Value of %s can be "0"; test with defined()

    (W misc) In a conditional expression, you used <HANDLE>, <*> (glob),each(), or readdir() as a boolean value. Each of these constructscan return a value of "0"; that would make the conditional expressionfalse, which is probably not what you intended. When using theseconstructs in conditional expressions, test their values with thedefined operator.

  • Value of CLI symbol "%s" too long

    (W misc) A warning peculiar to VMS. Perl tried to read the value of an%ENV element from a CLI symbol table, and found a resultant stringlonger than 1024 characters. The return value has been truncated to1024 characters.

  • Variable "%s" is not available

    (W closure) During compilation, an inner named subroutine or eval isattempting to capture an outer lexical that is not currently available.This can happen for one of two reasons. First, the outer lexical may bedeclared in an outer anonymous subroutine that has not yet been created.(Remember that named subs are created at compile time, while anonymoussubs are created at run-time.) For example,

    1. sub { my $a; sub f { $a } }

    At the time that f is created, it can't capture the current value of $a,since the anonymous subroutine hasn't been created yet. Conversely,the following won't give a warning since the anonymous subroutine has bynow been created and is live:

    1. sub { my $a; eval 'sub f { $a }' }->();

    The second situation is caused by an eval accessing a variable that hasgone out of scope, for example,

    1. sub f {
    2. my $a;
    3. sub { eval '$a' }
    4. }
    5. f()->();

    Here, when the '$a' in the eval is being compiled, f() is not currently beingexecuted, so its $a is not available for capture.

  • Variable "%s" is not imported%s

    (W misc) With "use strict" in effect, you referred to a global variablethat you apparently thought was imported from another module, becausesomething else of the same name (usually a subroutine) is exported bythat module. It usually means you put the wrong funny character on thefront of your variable.

  • Variable length lookbehind not implemented in m/%s/

    (F) Lookbehind is allowed only for subexpressions whose length is fixed andknown at compile time. See perlre.

  • "%s" variable %s masks earlier declaration in same %s

    (W misc) A "my", "our" or "state" variable has been redeclared in thecurrent scope or statement, effectively eliminating all access to theprevious instance. This is almost always a typographical error. Notethat the earlier variable will still exist until the end of the scopeor until all closure referents to it are destroyed.

  • Variable syntax

    (A) You've accidentally run your script through csh insteadof Perl. Check the #! line, or manually feed your script intoPerl yourself.

  • Variable "%s" will not stay shared

    (W closure) An inner (nested) named subroutine is referencing alexical variable defined in an outer named subroutine.

    When the inner subroutine is called, it will see the value ofthe outer subroutine's variable as it was before and during the *first*call to the outer subroutine; in this case, after the first call to theouter subroutine is complete, the inner and outer subroutines will nolonger share a common value for the variable. In other words, thevariable will no longer be shared.

    This problem can usually be solved by making the inner subroutineanonymous, using the sub {} syntax. When inner anonymous subs thatreference variables in outer subroutines are created, theyare automatically rebound to the current values of such variables.

  • vector argument not supported with alpha versions

    (W internal) The %vd (s)printf format does not support version objectswith alpha parts.

  • Verb pattern '%s' has a mandatory argument in regex; marked by <-- HERE in m/%s/

    (F) You used a verb pattern that requires an argument. Supply anargument or check that you are using the right verb.

  • Verb pattern '%s' may not have an argument in regex; marked by <-- HERE in m/%s/

    (F) You used a verb pattern that is not allowed an argument. Remove the argument or check that you are using the right verb.

  • Version number must be a constant number

    (P) The attempt to translate a use Module n.n LIST statement intoits equivalent BEGIN block found an internal inconsistency withthe version number.

  • Version string '%s' contains invalid data; ignoring: '%s'

    (W misc) The version string contains invalid characters at the end, whichare being ignored.

  • Warning: something's wrong

    (W) You passed warn() an empty string (the equivalent of warn "") oryou called it with no args and $@ was empty.

  • Warning: unable to close filehandle %s properly

    (S) The implicit close() done by an open() got an error indication onthe close(). This usually indicates your file system ran out of diskspace.

  • Warning: Use of "%s" without parentheses is ambiguous

    (S ambiguous) You wrote a unary operator followed by something thatlooks like a binary operator that could also have been interpreted as aterm or unary operator. For instance, if you know that the randfunction has a default argument of 1.0, and you write

    1. rand + 5;

    you may THINK you wrote the same thing as

    1. rand() + 5;

    but in actual fact, you got

    1. rand(+5);

    So put in parentheses to say what you really mean.

  • Wide character in %s

    (S utf8) Perl met a wide character (>255) when it wasn't expectingone. This warning is by default on for I/O (like print). The easiestway to quiet this warning is simply to add the :utf8 layer to theoutput, e.g. binmode STDOUT, ':utf8'. Another way to turn off thewarning is to add no warnings 'utf8'; but that is often closer tocheating. In general, you are supposed to explicitly mark thefilehandle with an encoding, see open and binmode.

  • Within []-length '%c' not allowed

    (F) The count in the (un)pack template may be replaced by [TEMPLATE]only if TEMPLATE always matches the same amount of packed bytes thatcan be determined from the template alone. This is not possible ifit contains any of the codes @, /, U, u, w or a *-length. Redesignthe template.

  • write() on closed filehandle %s

    (W closed) The filehandle you're writing to got itself closed sometimebefore now. Check your control flow.

  • %s "\x%X" does not map to Unicode

    (F) When reading in different encodings Perl tries to map everythinginto Unicode characters. The bytes you read in are not legal inthis encoding, for example

    1. utf8 "\xE4" does not map to Unicode

    if you try to read in the a-diaereses Latin-1 as UTF-8.

  • 'X' outside of string

    (F) You had a (un)pack template that specified a relative position beforethe beginning of the string being (un)packed. See pack.

  • 'x' outside of string in unpack

    (F) You had a pack template that specified a relative position afterthe end of the string being unpacked. See pack.

  • YOU HAVEN'T DISABLED SET-ID SCRIPTS IN THE KERNEL YET!

    (F) And you probably never will, because you probably don't have thesources to your kernel, and your vendor probably doesn't give a ripabout what you want. Your best bet is to put a setuid C wrapper aroundyour script.

  • You need to quote "%s"

    (W syntax) You assigned a bareword as a signal handler name.Unfortunately, you already have a subroutine of that name declared,which means that Perl 5 will try to call the subroutine when theassignment is executed, which is probably not what you want. (If it ISwhat you want, put an & in front.)

  • Your random numbers are not that random

    (F) When trying to initialise the random seed for hashes, Perl couldnot get any randomness out of your system. This usually indicatesSomething Very Wrong.

SEE ALSO

warnings, perllexwarn, diagnostics.

 
Source : perldoc.perl.org - Official documentation for the Perl programming language
Site maintained by Jon Allen (JJ)     See the project page for more details
Documentation maintained by the Perl 5 Porters
(Sebelumnya) Perl POD style guideWarning, lexical warnings warning (Berikutnya)