use constant UPPER_LIMIT => 10; | [reply] [d/l] |
if you are defining "UPPER_LIMIT" for a single script then
use constant UPPER_LIMIT => 10;
as suggested by lidden will be fine.If you want to scale up and use the same constant in multiple scripts then you can define the constant (and all common VARS that you scripts) in a file and require that file in you scripts!
To illustrate this type the following
$UPPER_LIMIT=10;
1;
in a file called "ENV.pl"(Please note the 1 thats returned in last line), then in you scripts use
require "ENV.pl";
This will import the contents of ENV.pl
The world is so big for any individual to conquer
| [reply] [d/l] [select] |
| [reply] [d/l] [select] |
A couple other ways to do this (depending on your goals and needs) would be to use Readonly instead of use constant, which is less prone to problems like having your constants considered "bare words" in string interpolation, hash keys and the like. So, you might use:
use Readonly;
Readonly my $UPPERLIMIT => 10;
...
And, though I think I'm the only one who's ever used this feature, perl has the -P option which will actually pass your script through the C preprocessor before interpreting and running. In that case, you could just use #define for constants just like in C and C++. But, that wouldn't be very 'perlish', would it.
These may not be what you need (especially the -P option), but I do like Readonly a little better than use constant.
---
echo S 1 [ Y V U | perl -ane 'print reverse map { $_ = chr(ord($_)-1) } @F;'
| [reply] [d/l] |