currently just used for compile time constants like $?LINE allright so
far so good.
but why not use that for all constants like
my $?constant = 5;
so it's compiletime (even late compiletime like in eval blocks) fix
binding to a value.
Because that variable comes from a different place
Even if we were to have a constant twigil, I dont much like $? for
it. No mnemomic value. For the builtins, it's not the constancy but
the fact that they let you quey the config...
The case distinction wyou suggest orks just as well on the user side.
Make your constants capitalized and your
[EMAIL PROTECTED] wrote:
currently just used for compile time constants like $?LINE allright so
far so good.
but why not use that for all constants like
my $?constant = 5;
Because then you'd have to change existing code if you find out that
constant was not so constant at all, and you'd
On Fri, Mar 14, 2008 at 7:18 AM, Mark J. Reed [EMAIL PROTECTED] wrote:
Even if we were to have a constant twigil, I dont much like $? for it.
No mnemomic value. For the builtins, it's not the constancy but the fact
that they let you quey the config...
The case distinction wyou suggest orks
currently just used for compile time constants like $?LINE allright so
far so good.
but why not use that for all constants like
my $?constant = 5;
Because then you'd have to change existing code if you find out that
constant was not so constant at all, and you'd like to have a variable
In article [EMAIL PROTECTED], herbert breunung
[EMAIL PROTECTED] wrote:
currently just used for compile time constants like $?LINE allright so
far so good.
but why not use that for all constants like
my $?constant = 5;
The $? is telling us where the value came from, not that it's a
currently just used for compile time constants like $?LINE allright so
far so good.
but why not use that for all constants like
my $?constant = 5;
so it's compiletime (even late compiletime like in eval blocks) fix
binding to a value.
i know i know we have
my const $var = 5;
my ithink my
