/usr/lib64/perl5
NameSizeModeActions
asm/-0755rm
asm-generic/-0755rm
auto/-0755rm
B/-0755rm
bits/-0755rm
CORE/-0755rm
Devel/-0755rm
File/-0755rm
gnu/-0755rm
Hash/-0755rm
I18N/-0755rm
IO/-0755rm
IPC/-0755rm
linux/-0755rm
machine/-0755rm
PerlIO/-0755rm
Sys/-0755rm
sys/-0755rm
Tie/-0755rm
Time/-0755rm
vendor_perl/-0755rm
arybase.pm28160644editdlrm
attributes.pm169290644editdlrm
B.pm314570644editdlrm
Config.pm31980644editdlrm
Config.pod2568890644editdlrm
Config_git.pl4090644editdlrm
Config_heavy.pl566550644editdlrm
DynaLoader.pm252220644editdlrm
endian.ph44610644editdlrm
Errno.pm68650644editdlrm
Fcntl.pm40440644editdlrm
features.ph136920644editdlrm
GDBM_File.pm15510644editdlrm
IO.pm14530644editdlrm
lib.pm60060644editdlrm
mro.pm100990644editdlrm
NDBM_File.pm25000644editdlrm
O.pm42080644editdlrm
ODBM_File.pm23830644editdlrm
Opcode.pm158930644editdlrm
ops.pm9970644editdlrm
perllocal.pod70550644editdlrm
POSIX.pm201980644editdlrm
POSIX.pod737050644editdlrm
re.pm226870644editdlrm
SDBM_File.pm35410644editdlrm
signal.ph33810644editdlrm
stdarg.ph28700644editdlrm
stdc-predef.ph8400644editdlrm
stddef.ph123720644editdlrm
syscall.ph860644editdlrm
syslimits.ph4520644editdlrm
syslog.ph850644editdlrm
wait.ph830644editdlrm
_h2ph_pre.ph292560644editdlrm
Edit: /usr/lib64/perl5/arybase.pm (2816B)
package arybase; our $VERSION = "0.12"; require XSLoader; XSLoader::load(); # This returns true, which makes require happy. __END__ =head1 NAME arybase - Set indexing base via $[ =head1 SYNOPSIS $[ = 1; @a = qw(Sun Mon Tue Wed Thu Fri Sat); print $a[3], "\n"; # prints Tue =head1 DESCRIPTION This module implements Perl's C<$[> variable. You should not use it directly. Assigning to C<$[> has the I effect of making the assigned value, converted to an integer, the index of the first element in an array and the first character in a substring, within the enclosing lexical scope. It can be written with or without C: $[ = 1; local $[ = 1; It only works if the assignment can be detected at compile time and the value assigned is constant. It affects the following operations: $array[$element] @array[@slice] $#array (list())[$slice] splice @array, $index, ... each @array keys @array index $string, $substring # return value is affected pos $string substr $string, $offset, ... As with the default base of 0, negative bases count from the end of the array or string, starting with -1. If C<$[> is a positive integer, indices from C<$[-1> to 0 also count from the end. If C<$[> is negative (why would you do that, though?), indices from C<$[> to 0 count from the beginning of the string, but indices below C<$[> count from the end of the string as though the base were 0. Prior to Perl 5.16, indices from 0 to C<$[-1> inclusive, for positive values of C<$[>, behaved differently for different operations; negative indices equal to or greater than a negative C<$[> likewise behaved inconsistently. =head1 HISTORY Before Perl 5, C<$[> was a global variable that affected all array indices and string offsets. Starting with Perl 5, it became a file-scoped compile-time directive, which could be made lexically-scoped with C. "File-scoped" means that the C<$[> assignment could leak out of the block in which occurred: { $[ = 1; # ... array base is 1 here ... } # ... still 1, but not in other files ... In Perl 5.10, it became strictly lexical. The file-scoped behaviour was removed (perhaps inadvertently, but what's done is done). In Perl 5.16, the implementation was moved into this module, and out of the Perl core. The erratic behaviour that occurred with indices between -1 and C<$[> was made consistent between operations, and, for negative bases, indices from C<$[> to -1 inclusive were made consistent between operations. =head1 BUGS Error messages that mention array indices use the 0-based index. C and C do not respect the current value of C<$[>. =head1 SEE ALSO L, L and L. =cut