Seth Woolley's Man Viewer

constant(3) - constant - Perl pragma to declare constants - man 3 constant

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

constant(3)            Perl Programmers Reference Guide            constant(3)

       constant - Perl pragma to declare constants

           use constant PI    => 4 * atan2(1, 1);
           use constant DEBUG => 0;

           print "Pi equals ", PI, "...\n" if(3,n) DEBUG;

           use constant {
               SEC   => 0,
               MIN   => 1,
               HOUR  => 2,
               MDAY  => 3,
               MON   => 4,
               YEAR  => 5,
               WDAY  => 6,
               YDAY  => 7,
               ISDST => 8,

           use constant WEEKDAYS => qw(
               Sunday Monday Tuesday Wednesday Thursday Friday Saturday

           print "Today is ", (WEEKDAYS)[ (localtime)[WDAY] ], ".\n";

       This will declare a symbol to be a constant with the given value.

       When you declare a constant such as "PI" using the method shown above,
       each machine your script runs upon can have as many digits of accuracy
       as it can use. Also, your program will be easier to read(2,n,1 builtins), more likely
       to be maintained (and maintained correctly), and far less(1,3) likely to
       send(2,n) a space probe to the wrong planet because nobody noticed the one
       equation in(1,8) which you wrote 3.14195.

       When a constant is used in(1,8) an expression, perl replaces it with its
       value at compile time(1,2,n), and may then optimize the expression further.
       In particular, any code in(1,8) an "if(3,n) (CONSTANT)" block will be optimized
       away if(3,n) the constant is false.

       As with all "use" directives, defining a constant happens at compile
       time. Thus, it's probably not correct to put a constant declaration
       inside of a conditional statement (like "if(3,n) ($foo) { use constant ...

       Constants defined using this module cannot be interpolated into strings
       like variables.  However, concatenation works just fine:

           print "Pi equals PI...\n";        # WRONG: does not expand "PI"
           print "Pi equals ".PI."...\n";    # right

       Even though a reference may be declared as a constant, the reference
       may point to data which may be changed, as this code shows.

           use constant ARRAY => [ 1,2,3,4 ];
           print ARRAY->[1];
           ARRAY->[1] = " be changed";
           print ARRAY->[1];

       Dereferencing constant references incorrectly (such as using an array
       subscript on a constant hash reference, or vice versa) will be trapped
       at compile time.

       Constants belong to the package they are defined in.  To refer to a
       constant defined in(1,8) another package, specify the full package name, as
       in(1,8) "Some::Package::CONSTANT".  Constants may be exported by modules,
       and may also be called as either class or instance methods, that is, as
       "Some::Package->CONSTANT" or as "$obj->CONSTANT" where $obj is an
       instance of "Some::Package".  Subclasses may define their own constants
       to override those in(1,8) their base class.

       The use of all caps for constant names is merely a convention, although
       it is recommended in(1,8) order to make constants stand out and to help
       avoid collisions with other barewords, keywords, and subroutine names.
       Constant names must begin with a letter or underscore. Names beginning
       with a double underscore are reserved. Some poor choices for names will
       generate warnings, if(3,n) warnings are enabled at compile time.

       List constants

       Constants may be lists of more (or less(1,3)) than one value.  A constant
       with no values evaluates to "undef" in(1,8) scalar context.  Note that con-
       stants with more than one value do not return their last value in(1,8)
       scalar context as one might expect.  They currently return the number
       of values, but this may change in(1,8) the future.  Do not use constants
       with multiple values in(1,8) scalar context.

       NOTE: This implies that the expression defining the value of a constant
       is evaluated in(1,8) list context.  This may produce surprises:

           use constant TIMESTAMP => localtime;                # WRONG!
           use constant TIMESTAMP => scalar localtime;         # right

       The first line above defines "TIMESTAMP" as a 9-element list, as
       returned by localtime() in(1,8) list context.  To set(7,n,1 builtins) it to the string(3,n)
       returned by localtime() in(1,8) scalar context, an explicit "scalar" keyword
       is required.

       List constants are lists, not arrays.  To index or slice them, they
       must be placed in(1,8) parentheses.

           my @workdays = WEEKDAYS[1 .. 5];            # WRONG!
           my @workdays = (WEEKDAYS)[1 .. 5];          # right

       Defining multiple constants at once

       Instead of writing multiple "use constant" statements, you may define
       multiple constants in(1,8) a single statement by giving, instead of the con-
       stant name, a reference to a hash where the keys are the names of the
       constants to be defined.  Obviously, all constants defined using this
       method must have a single value.

           use constant {
               FOO => "A single value",
               BAR => "This", "won't", "work!",        # Error!

       This is a fundamental limitation of the way hashes are constructed in(1,8)
       Perl.  The error(8,n) messages produced when this happens will often be
       quite cryptic -- in(1,8) the worst case there may be none at all, and you'll
       only later find that something is broken.

       When defining multiple constants, you cannot use the values of other
       constants defined in(1,8) the same declaration.  This is because the calling
       package doesn't know about any constant within that group until after
       the "use" statement is finished.

           use constant {
               BITMASK => 0xAFBAEBA8,
               NEGMASK => ~BITMASK,                    # Error!

       Magic constants

       Magical values and references can be made into constants at compile
       time(1,2,n), allowing for way cool stuff like this.  (These error(8,n) numbers
       aren't totally portable, alas.)

           use constant E2BIG => ($! = 7);
           print   E2BIG, "\n";        # something like "Arg list too long"
           print 0+E2BIG, "\n";        # "7"

       You can't produce a tied constant by giving a tied scalar as the value.
       References to tied variables, however, can be used as constants without
       any problems.

       In the current implementation, scalar constants are actually inlinable
       subroutines. As of version(1,3,5) 5.004 of Perl, the appropriate scalar con-
       stant is inserted directly in(1,8) place of some subroutine calls, thereby
       saving the overhead of a subroutine call. See "Constant Functions" in(1,8)
       perlsub for details about how and when this happens.

       In the rare case in(1,8) which you need to discover(1,3,5) at run time(1,2,n) whether a
       particular constant has been declared via this module, you may use this
       function to examine the hash %constant::declared. If the given constant
       name does not include a package name, the current package is used.

           sub declared ($) {
               use constant 1.01;              # don't omit this!
               my $name = shift;
               $name =~ s/^::/main::/;
               my $pkg = caller;
               my $full_name = $name =~ /::/ ? $name : "${pkg}::$name";

       In the current version(1,3,5) of Perl, list constants are not inlined and some
       symbols may be redefined without generating a warning.

       It is not possible to have a subroutine or a keyword with the same name
       as a constant in(1,8) the same package. This is probably a Good Thing.

       A constant with a name in(1,8) the list "STDIN STDOUT STDERR ARGV ARGVOUT
       ENV INC SIG" is not allowed anywhere but in(1,8) package "main::", for tech-
       nical reasons.

       Unlike constants in(1,8) some languages, these cannot be overridden on the
       command line or via environment variables.

       You can get into trouble if(3,n) you use constants in(1,8) a context which auto-
       matically quotes barewords (as is true for any subroutine call).  For
       example, you can't say $hash{CONSTANT} because "CONSTANT" will be
       interpreted as a string.  Use $hash{CONSTANT()} or $hash{+CONSTANT} to
       prevent the bareword quoting mechanism from kicking in.  Similarly,
       since the "=>" operator quotes a bareword immediately to its left, you
       have to say "CONSTANT() => 'value'" (or simply use a comma in(1,8) place of
       the big arrow) instead of "CONSTANT => 'value'".

       Tom Phoenix, <>, with help from many other folks.

       Multiple constant declarations at once added by Casey West,

       Documentation mostly rewritten by Ilmari Karonen, <>.

       Copyright (C) 1997, 1999 Tom Phoenix

       This module is free software; you can redistribute it or modify it
       under the same terms as Perl itself.

perl v5.8.5                       2001-09-21                       constant(3)

References for this manual (incoming links)