| Path::Class::Dir - Objects representing directories |
Path::Class::Dir - Objects representing directories
use Path::Class qw(dir); # Export a short constructor
my $dir = dir('foo', 'bar'); # Path::Class::Dir object
my $dir = Path::Class::Dir->new('foo', 'bar'); # Same thing
# Stringifies to 'foo/bar' on Unix, 'foo\bar' on Windows, etc.
print "dir: $dir\n";
if ($dir->is_absolute) { ... }
my $v = $dir->volume; # Could be 'C:' on Windows, empty string
# on Unix, 'Macintosh HD:' on Mac OS
$dir->cleanup; # Perform logical cleanup of pathname
my $file = $dir->file('file.txt'); # A file in this directory
my $subdir = $dir->subdir('george'); # A subdirectory
my $parent = $dir->parent; # The parent directory, 'foo'
my $abs = $dir->absolute; # Transform to absolute path
my $rel = $abs->relative; # Transform to relative path
my $rel = $abs->relative('/foo'); # Relative to /foo
print $dir->as_foreign('Mac'); # :foo:bar:
print $dir->as_foreign('Win32'); # foo\bar
# Iterate with IO::Dir methods:
my $handle = $dir->open;
while (my $file = $handle->read) {
$file = $dir->file($file); # Turn into Path::Class::File object
...
}
# Iterate with Path::Class methods:
while (my $file = $dir->next) {
# $file is a Path::Class::File or Path::Class::Dir object
...
}
The Path::Class::Dir class contains functionality for manipulating
directory names in a cross-platform way.
Path::Class::Dir object and returns it. The
arguments specify names of directories which will be joined to create
a single directory object. A volume may also be specified as the
first argument, or as part of the first argument. You can use
platform-neutral syntax:
my $dir = dir( 'foo', 'bar', 'baz' );
or platform-native syntax:
my $dir = dir( 'foo/bar/baz' );
or a mixture of the two:
my $dir = dir( 'foo/bar', 'baz' );
All three of the above examples create relative paths. To create an absolute path, either use the platform native syntax for doing so:
my $dir = dir( '/var/tmp' );
or use an empty string as the first argument:
my $dir = dir( '', 'var', 'tmp' );
If the second form seems awkward, that's somewhat intentional - paths
like /var/tmp or \Windows aren't cross-platform concepts in the
first place (many non-Unix platforms don't have a notion of a ``root
directory''), so they probably shouldn't appear in your code if you're
trying to be cross-platform. The first form is perfectly natural,
because paths like this may come from config files, user input, or
whatever.
As a special case, since it doesn't otherwise mean anything useful and
it's convenient to define this way, Path::Class::Dir->new() (or
dir()) refers to the current directory (File::Spec->curdir).
To get the current directory as an absolute path, do <
dir()-absolute >>.
Path::Class::Dir object is
used in a string context, so the following are equivalent:
$string = $dir->stringify; $string = "$dir";
C: on Windows, Macintosh HD: on Mac OS,
etc.) of the directory object, if any. Otherwise, returns the empty
string.
Path::Class::File objects always
return false, and Path::Class::Dir objects always return true.
/usr/local or \Windows).
my $dir = dir('/foo//baz/./foo')->cleanup;
# $dir now represents '/foo/baz/foo';
Path::Class::File object representing an entry in $dir
or one of its subdirectories. Internally, this just calls <
Path::Class::File-new( @_ ) >>.
Path::Class::Dir object representing a subdirectory
of $dir.
$dir. Note that this is the
logical parent, not necessarily the physical parent. It really
means we just chop off entries from the end of the directory list
until we cain't chop no more. If the directory is relative, we start
using the relative forms of parent directories.
The following code demonstrates the behavior on absolute and relative directories:
$dir = dir('/foo/bar');
for (1..6) {
print "Absolute: $dir\n";
$dir = $dir->parent;
}
$dir = dir('foo/bar');
for (1..6) {
print "Relative: $dir\n";
$dir = $dir->parent;
}
########### Output on Unix ################
Absolute: /foo/bar
Absolute: /foo
Absolute: /
Absolute: /
Absolute: /
Absolute: /
Relative: foo/bar
Relative: foo
Relative: .
Relative: ..
Relative: ../..
Relative: ../../..
Path::Class::File and/or Path::Class::Dir
objects listed in this directory, or in scalar context the number of
such objects. Obviously, it is necessary for $dir to
exist and be readable in order to find its children.
Note that the children are returned as subdirectories of $dir,
i.e. the children of foo will be foo/bar and foo/baz, not
bar and baz.
Ordinarily children() will not include the self and parent
entries . and .. (or their equivalents on non-Unix systems),
because that's like I'm-my-own-grandpa business. If you do want all
directory entries including these special ones, pass a true value for
the all parameter:
@c = $dir->children(); # Just the children @c = $dir->children(all => 1); # All entries
Path::Class::Dir object representing $dir as an
absolute path. An optional argument, given as either a string or a
Path::Class::Dir object, specifies the directory to use as the base
of relativity - otherwise the current working directory will be used.
Path::Class::Dir object representing $dir as a
relative path. An optional argument, given as either a string or a
Path::Class::Dir object, specifies the directory to use as the base
of relativity - otherwise the current working directory will be used.
subsumes($other)$dir actually contains $other on the
filesystem.
The $other argument may be a Path::Class::Dir object, a
Path::Class::File object, or a string. In the latter case, we
assume it's a directory.
# Examples:
dir('foo/bar' )->subsumes(dir('foo/bar/baz')) # True
dir('/foo/bar')->subsumes(dir('/foo/bar/baz')) # True
dir('foo/bar' )->subsumes(dir('bar/baz')) # False
dir('/foo/bar')->subsumes(dir('foo/bar')) # False
contains($other)$other on the
filesystem. $other doesn't have to be a direct child of $dir,
it just has to be subsumed.
as_foreign($type)Path::Class::Dir object representing $dir as it would
be specified on a system of type $type. Known types include
Unix, Win32, Mac, VMS, and OS2, i.e. anything for which
there is a subclass of File::Spec.
Any generated objects (subdirectories, files, parents, etc.) will also retain this type.
Path::Class::Dir object representing $dir as it would
be specified on a system of type $type. Known types include
Unix, Win32, Mac, VMS, and OS2, i.e. anything for which
there is a subclass of File::Spec.
The arguments in @args are the same as they would be specified in
new().
<
Path::Class-new( $dir->dir_list ) >> should be equivalent to $dir.
The semantics of this method are similar to Perl's splice or
substr functions; they return LENGTH elements starting at
OFFSET. If LENGTH is omitted, returns all the elements starting
at OFFSET up to the end of the list. If LENGTH is negative,
returns the elements from OFFSET onward except for -LENGTH
elements at the end. If OFFSET is negative, it counts backward
OFFSET elements from the end of the list. If OFFSET and
LENGTH are both omitted, the entire list is returned.
In a scalar context, dir_list() with no arguments returns the
number of entries in the directory list; dir_list(OFFSET) returns
the single element at that offset; dir_list(OFFSET, LENGTH) returns
the final element that would have been returned in a list context.
open()$dir to IO::Dir->open and returns the result as an
IO::Dir object. If the opening fails, undef is returned and
$! is set.
$dir, to File::Path::mkpath()
>> and returns the result (a list of all directories created).
$dir, to File::Path::rmtree()
>> and returns the result (the number of files successfully deleted).
remove()Path::Class::File's remove() method.
next()next() is called, it will open() the directory and read the
first item from it, returning the result as a Path::Class::Dir or
Path::Class::File object (depending, of course, on its actual
type). Each subsequent call to next() will simply iterate over the
directory's contents, until there are no more items in the directory,
and then the undefined value is returned. For example, to iterate
over all the regular files in a directory:
while (my $file = $dir->next) {
next unless -f $file;
my $fh = $file->open('r') or die "Can't read $file: $!";
...
}
If an error occurs when opening the directory (for instance, it
doesn't exist or isn't readable), next() will throw an exception
with the value of $!.
callback subroutine for
each entry. This is a lot like what the File::Find module does,
and of course File::Find will work fine on Path::Class objects,
but the advantage of the recurse() method is that it will also feed
your callback routine Path::Class objects rather than just pathname
strings.
The recurse() method requires a callback parameter specifying
the subroutine to invoke for each entry. It will be passed the
Path::Class object as its first argument.
recurse() also accepts two boolean parameters, depthfirst and
preorder that control the order of recursion. The default is a
preorder, breadth-first search, i.e. depthfirst => 0, preorder => 1.
At the time of this writing, all combinations of these two parameters
are supported except depthfirst => 0, preorder => 0.
stat()File::stat::stat() on this directory and returns a
File::stat object representing the result.
lstat()stat(), but if $file is a symbolic link, lstat()
stats the link instead of the directory the link points to.
Ken Williams, ken@mathforum.org
Path::Class, Path::Class::File, File::Spec
| Path::Class::Dir - Objects representing directories |