in reply to *a=*[; bug?

I have to say that according to the output of the following test script, the value of $[ is definitely not read-only at run-time. You can keep assigning a new number to $[ and change the subscript behaviour at run-time. However the use of $[ = $a is not supported. The Perl documentation clearly states that $[ is treated as a compiler directive and its use is discouraged. I suspect that Perl handles this special variable differently because of efficiency reasons (or because the whole idea of $[ was a hack in the first place afterall).
my @elements = qw/ 0 1 2 3 4 5 6 7 8 9 /;

$[ = 0;
print $elements[1], "\n";

$[ = 1;
print $elements[1], "\n";

if ($[ == 1) {
  $[ = 0;
  print $elements[1], "\n";
}

# The following will fail at compile time
#   $a = 0;
#   $[ = $a;  # reset
#   print $elements[1], "\n";

[download]

And the output is -
1
0
1

[download]

Replies are listed 'Best First'.
Re^2: *a=*[; bug?
by Aristotle (Chancellor) on Jan 11, 2004 at 01:29 UTC
    It may look like runtime, but it's not. Just change $[ to $a see what happens to the optree by running the source through B::Concise. You'll notice that the $a version has real assignments like 
    k     <2> sassign vKS/2 ->l
i        <$> const(IV 0) s ->j
-        <1> ex-rv2sv sKRM*/1 ->k
j           <$> gvsv(*a) s ->k

    [download]
    where in the $[ version all you get is a mere 
    i     <;> nextstate(main 2 x.pl:4) v ->j

    [download]

    The effect of changing the array base index is achieved through virtual machine state, which is actually independent from the runtime value of $[. The value accessible through $[ is kept synched to the internal state but not vice versa.

    Full B::Concise output follows:

    Read more... (6 kB)

    Makeshifts last the longest.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom