Server : Apache/2.4.41 (Ubuntu) System : Linux absol.cf 5.4.0-198-generic #218-Ubuntu SMP Fri Sep 27 20:18:53 UTC 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.33 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, Directory : /usr/share/doc/gnustep-base-doc/Base/Reference/
Upload File :
Current File : //usr/share/doc/gnustep-base-doc/Base/Reference/NSFileManager.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>NSFileManager class reference</title>
</head>
<body>
<font face="serif">
<a href="Base.html">Up</a>
<br />
<h1><a name="title$NSFileManager">NSFileManager class reference</a></h1>
<h3>Authors</h3>
<dl>
<dt>Mircea Oancea (<a href="mailto:mircea@jupiter.elcom.pub.ro"><code>mircea@jupiter.elcom.pub.ro</code></a>)</dt>
<dd>
</dd>
<dt>Ovidiu Predescu (<a href="mailto:ovidiu@net-community.com"><code>ovidiu@net-community.com</code></a>)</dt>
<dd>
</dd>
<dt>Nicola Pero (<a href="mailto:n.pero@mi.flashnet.it"><code>n.pero@mi.flashnet.it</code></a>)</dt>
<dd>
</dd>
<dt>Richard Frith-Macdonald (<a href="mailto:rfm@gnu.org"><code>rfm@gnu.org</code></a>)</dt>
<dd>
</dd>
</dl>
<p><b>Copyright:</b> (C) 1997,1999-2005 Free Software Foundation, Inc.</p>
<div>
<hr width="50%" align="left" />
<h3>Contents -</h3>
<ol>
<li>
<a href="#001000000000">File management</a>
</li>
<li>
<a href="#001001000000">Path handling</a>
<li>
<a href="#001001001000">unix</a>
<ol>
<li>
<a href="#001001002000">windows</a>
</li>
<li>
<a href="#001001003000">gnustep</a>
</li>
<li>
<a href="#001001004000">Portability</a>
</li>
<li>
<a href="#001001005000">Tilde substitution</a>
</li>
</ol>
</li>
</ol>
</li>
<li>
<a href="#002000000000">Software documentation for the NSDirectoryEnumerator
class</a>
</li>
<li>
<a href="#003000000000">Software documentation for the NSFileManager class</a>
</li>
</ol>
<hr width="50%" align="left" />
</div>
<h1><a name="001000000000">File management</a></h1>
<h2><a name="001001000000">Path handling</a></h2>
<p>
The rules for path handling depend on the value in the
<code>GNUSTEP_PATH_HANDLING</code> environment
variable and, to some extent, on the platform on
which the program is running. <br /> The understood
values of GNUSTEP_PATH_HANDLING are <em>unix</em> and
<em>windows</em>. If GNUSTEP_PATH_HANDLING is any other
value (or has not been set), GNUstep interprets this as
meaning it should try to <em>do-the-right-thing</em>
<br /> In the default mode of operation the system is
very tolerant of paths and allows you to work with both
unix and windows style paths. The consequences of this
are apparent in the path handling methods of
<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>
rather than in
<a rel="gsdoc" href="#class$NSFileManager">NSFileManager</a>
.
</p>
<h3><a name="001001001000">unix</a></h3>
<p>
On all Unix platforms, Path components are separated
by slashes and file names may contain any character
other than slash. <br /> The file names. and..
are special cases meaning current directory and the
parent of the current directory respectively.
<br /> Multiple adjacent slash characters are
treated as a single separator.
</p>
<dl>
<dt>/</dt>
<dd>
An absolute path to the root directory.
</dd>
<dt>/etc/motd</dt>
<dd>
An absolute path to the file named <em>motd</em>
in the subdirectory <em>etc</em> of the root
directory.
</dd>
<dt>..</dt>
<dd>
A relative path to the parent of the current
directory.
</dd>
<dt>program.m</dt>
<dd>
A relative path to the file <em>program.m</em> in
the current directory.
</dd>
<dt>Source/program.m</dt>
<dd>
A relative path to the file <em>program.m</em> in
the subdirectory <em>Source</em> of the current
directory.
</dd>
<dt>../GNUmakefile</dt>
<dd>
A relative path to the file <em>GNUmakefile</em> in
the directory above the current directory.
</dd>
</dl>
<h3><a name="001001002000">windows</a></h3>
<p>
On Microsoft Windows the native paths may be either
UNC or drive-relative, so GNUstep supports both.
<br /> Either or both slash (/) and backslash
(\) may be used as separators for path components
in either type of name. <br /> UNC paths follow the
general form //host/share/path/file, but must
at least contain the host and share parts, i.e.
//host/share is a UNC path, but //host is
<em>not</em> <br /> Drive-relative names consist
of an optional drive specifier (consisting of a
single letter followed by a single colon)
followed by an absolute or relative path.
<br /> In both forms, the names. and.. are refer
to the current directory and the parent directory as
in unix paths.
</p>
<dl>
<dt>//host/share/file</dt>
<dd>
An absolute UNC path to a file called
<em>file</em> in the top directory of the export
point share on host.
</dd>
<dt>C:</dt>
<dd>
A relative path to the current directory on drive
C.
</dd>
<dt>C:program.m</dt>
<dd>
A relative path to the file <em>program.m</em> on
drive C.
</dd>
<dt>C:\program.m</dt>
<dd>
An absolute path to the file <em>program.m</em> in
the top level directory on drive C.
</dd>
<dt>/Source\program.m</dt>
<dd>
A drive-relative path to <em>program.m</em> in the
directory <em>Source</em> on the current
drive.
</dd>
<dt>\\name</dt>
<dd>
A drive-relative path to <em>name</em> in the top
level directory on the current drive. The '\\'
is treated as a single backslash as this is not a
UNC name (there must be both a host and a share
part in a UNC name).
</dd>
</dl>
<h3><a name="001001003000">gnustep</a></h3>
<p>
In the default mode, GNUstep handles both unix and
windows paths so it treats both slash (/) and
backslash (\) as separators and understands
the windows UNC and drive relative path roots.
<br /> However, it treats any path beginning
with a slash (/) as an absolute path
<em>if running on a unix system</em>.
</p>
<h3><a name="001001004000">Portability</a></h3>
<p>
Attempting to pass absolute paths between
applications working on different systems
is fraught with difficulty... just don't do it.
<br /> Where paths need to be passed around (eg.
in property lists or archives) you should pass
relative paths and use a standard mechanism to
construct an absolute path in the receiving
application, for instance, appending the
relative path to the home directory of a user.
</p>
<ul>
<li>
Use only the slash (/) as a path separator, not
backslash (\).
</li>
<li>
Never use a backslash (\) in a file name.
</li>
<li>
Avoid colons in file names.
</li>
<li>
Use no more than three letters in a path
extension.
</li>
</ul>
<h3><a name="001001005000">Tilde substitution</a></h3>
<p>
GNUstep handles substitution of tilde (~) as
follows: <br /> If a path is just ~ or begins
~/ then the value returned by
<a rel="gsdoc" href="Functions.html#function$NSHomeDirectory">
NSHomeDirectory()
</a>
is substituted for the tilde. <br /> If a path is of
the form ~name or begins with a string like ~name/
then name is used as the argument to
<a rel="gsdoc" href="Functions.html#function$NSHomeDirectoryForUser">
NSHomeDirectoryForUser()
</a>
and the return value from that method (if non-nil)
is used to replace the tilde.
</p>
<h1><a name="002000000000">
Software documentation for the NSDirectoryEnumerator
class
</a></h1>
<h2><a name="class$NSDirectoryEnumerator">NSDirectoryEnumerator</a> : <a rel="gsdoc" href="NSEnumerator.html#class$NSEnumerator">NSEnumerator</a></h2>
<blockquote class="declared">
<dl>
<dt><b>Declared in:</b></dt>
<dd>Foundation/NSFileManager.h</dd>
</dl>
</blockquote>
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
</p>
<p>
This is a subclass of <code>NSEnumerator</code> which
provides a full listing of all the files beneath a
directory and its subdirectories. Instances can
be obtained through
[NSFileManager -enumeratorAtPath:]
.
</p>
<p>
</p>
<p>
This implementation is optimized and performance
should be comparable to the speed of standard Unix
tools for large directories.
</p>
<p>
</p>
<p>
The order in which directory contents are enumerated is
undefined, and in the current implementation the
natural order of the underlying filesystem is used.
</p>
<p>
</div>
<b>Method summary</b>
<ul>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSDirectoryEnumerator-directoryAttributes">-directoryAttributes</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSDirectoryEnumerator-fileAttributes">-fileAttributes</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSDirectoryEnumerator-skipDescendents">-skipDescendents</a></li>
</ul>
<hr width="50%" align="left" />
<div class="method">
<h3><a name="method$NSDirectoryEnumerator-directoryAttributes">directoryAttributes </a></h3>
- (<a rel="gsdoc" href="NSDictionary.html#class$NSDictionary">NSDictionary</a>*) <b>directoryAttributes</b>;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Returns a dictionary containing the attributes of
the directory at which enumeration started. <br /> The
contents of this dictionary are as produced by
[NSFileManager -fileAttributesAtPath:traverseLink:]
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSDirectoryEnumerator-fileAttributes">fileAttributes </a></h3>
- (<a rel="gsdoc" href="NSDictionary.html#class$NSDictionary">NSDictionary</a>*) <b>fileAttributes</b>;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Returns a dictionary containing the attributes of
the file currently being enumerated. <br /> The
contents of this dictionary are as produced by
[NSFileManager -fileAttributesAtPath:traverseLink:]
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSDirectoryEnumerator-skipDescendents">skipDescendents </a></h3>
- (void) <b>skipDescendents</b>;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Informs the receiver that any descendents of the
current directory should be skipped rather than
enumerated. Use this to avoid enumerating the
contents of directories you are not interested in.
</div>
<hr width="25%" align="left" />
</div>
<h1><a name="003000000000">
Software documentation for the NSFileManager class
</a></h1>
<h2><a name="class$NSFileManager">NSFileManager</a> : <a rel="gsdoc" href="NSObject.html#class$NSObject">NSObject</a></h2>
<blockquote class="declared">
<dl>
<dt><b>Declared in:</b></dt>
<dd>Foundation/NSFileManager.h</dd>
</dl>
</blockquote>
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
This is the main class for platform-independent
management of the local filesystem, which allows
you to read and save files, create/list directories, and
move or delete files and directories. In addition to
simply listing directories, you may obtain an
<a rel="gsdoc" href="#class$NSDirectoryEnumerator">NSDirectoryEnumerator</a>
instance for recursive directory contents
enumeration.
</div>
<b>Method summary</b>
<ul>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager+defaultManager">+defaultManager</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-attributesOfFileSystemForPath$error$">-attributesOfFileSystemForPath:error:</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-attributesOfItemAtPath$error$">-attributesOfItemAtPath:error:</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-changeCurrentDirectoryPath$">-changeCurrentDirectoryPath:</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-changeFileAttributes$atPath$">-changeFileAttributes:atPath:</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-componentsToDisplayForPath$">-componentsToDisplayForPath:</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-contentsAtPath$">-contentsAtPath:</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-contentsEqualAtPath$andPath$">-contentsEqualAtPath:andPath:</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-contentsOfDirectoryAtPath$error$">-contentsOfDirectoryAtPath:error:</a></li>
<li><a rel="gsdoc" href="NSFileManager.html#method$NSFileManager-contentsOfDirectoryAtURL$includingPropertiesForKeys$options$error$">-contentsOfDirectoryAtURL:includingPropertiesForKeys:options:error:</a></li>
</ul>
<hr width="50%" align="left" />
<div class="method">
<h3><a name="method$NSFileManager+defaultManager">defaultManager </a></h3>
+ (<a rel="gsdoc" href="#class$NSFileManager">NSFileManager</a>*) <b>defaultManager</b>;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Returns a shared default file manager which may be
used throughout an application.
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-attributesOfFileSystemForPath$error$">attributesOfFileSystemForPath: error: </a></h3>
- (<a rel="gsdoc" href="NSDictionary.html#class$NSDictionary">NSDictionary</a>*) <b>attributesOfFileSystemForPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path<b> error:</b> (<a rel="gsdoc" href="NSError.html#class$NSError">NSError</a>**)error;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.5.0</div>
<br />
<div class="desc">
<em>Description forthcoming.</em>
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-attributesOfItemAtPath$error$">attributesOfItemAtPath: error: </a></h3>
- (<a rel="gsdoc" href="NSDictionary.html#class$NSDictionary">NSDictionary</a>*) <b>attributesOfItemAtPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path<b> error:</b> (<a rel="gsdoc" href="NSError.html#class$NSError">NSError</a>**)error;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.5.0</div>
<br />
<div class="desc">
If a file (or directory etc) exists at the specified
<var>path</var>, and can be queried for its
attributes, this method returns a dictionary
containing the various attributes of that file.
Otherwise <code>nil</code> is returned. <br /> If
an <var>error</var> occurs, <var>error</var> describes
the problem. Pass NULL if you do not want
<var>error</var> information.
</p>
<p>
The dictionary keys for attributes are -
</p>
<p>
<dl>
<dt><code>NSFileAppendOnly</code></dt>
<dd>
NSNumber... boolean
</dd>
<dt><code>NSFileCreationDate</code></dt>
<dd>
NSDate when the file was created (if supported)
</dd>
<dt><code>NSFileDeviceIdentifier</code></dt>
<dd>
NSNumber (identifies the device on which the
file is stored)
</dd>
<dt><code>NSFileExtensionHidden</code></dt>
<dd>
NSNumber... boolean
</dd>
<dt>
<code>NSFileGroupOwnerAccountName</code>
</dt>
<dd>
NSString name of the file group
</dd>
<dt>
<code>NSFileGroupOwnerAccountID</code>
</dt>
<dd>
NSNumber ID of the file group
</dd>
<dt><code>NSFileHFSCreatorCode</code></dt>
<dd>
NSNumber not used
</dd>
<dt><code>NSFileHFSTypeCode</code></dt>
<dd>
NSNumber not used
</dd>
<dt><code>NSFileImmutable</code></dt>
<dd>
NSNumber... boolean
</dd>
<dt><code>NSFileModificationDate</code></dt>
<dd>
NSDate when the file was last modified
</dd>
<dt><code>NSFileOwnerAccountName</code></dt>
<dd>
NSString name of the file owner
</dd>
<dt><code>NSFileOwnerAccountID</code></dt>
<dd>
NSNumber ID of the file owner
</dd>
<dt><code>NSFilePosixPermissions</code></dt>
<dd>
NSNumber posix access permissions mask
</dd>
<dt><code>NSFileReferenceCount</code></dt>
<dd>
NSNumber number of links to this file
</dd>
<dt><code>NSFileSize</code></dt>
<dd>
NSNumber size of the file in bytes
</dd>
<dt><code>NSFileSystemFileNumber</code></dt>
<dd>
NSNumber the identifier for the file on the
filesystem
</dd>
<dt><code>NSFileSystemNumber</code></dt>
<dd>
NSNumber the filesystem on which the file is
stored
</dd>
<dt><code>NSFileType</code></dt>
<dd>
NSString the type of file
</dd>
</dl>
</p>
<p>
The
<a rel="gsdoc" href="NSDictionary.html#class$NSDictionary">NSDictionary</a>
class also has a set of convenience accessor
methods which enable you to get at file
attribute information more efficiently than
using the keys above to extract it. You should
generally use the accessor methods where they
are available.
</p>
<p>
<ul>
<li>
[NSDictionary(NSFileAttributes) -fileCreationDate]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileExtensionHidden]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileHFSCreatorCode]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileHFSTypeCode]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileIsAppendOnly]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileIsImmutable]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileSize]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileType]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileOwnerAccountName]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileOwnerAccountID]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileGroupOwnerAccountName]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileGroupOwnerAccountID]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileModificationDate]
</li>
<li>
[NSDictionary(NSFileAttributes) -filePosixPermissions]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileSystemNumber]
</li>
<li>
[NSDictionary(NSFileAttributes) -fileSystemFileNumber]
</li>
</ul>
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-changeCurrentDirectoryPath$">changeCurrentDirectoryPath: </a></h3>
- (BOOL) <b>changeCurrentDirectoryPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Changes the current directory used for all
subsequent operations. <br /> All non-absolute
paths are interpreted relative to this directory.
<br /> The current directory is set on a per-task
basis, so the current directory for other file
manager instances will also be changed by this
method.
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-changeFileAttributes$atPath$">changeFileAttributes: atPath: </a></h3>
- (BOOL) <b>changeFileAttributes:</b> (<a rel="gsdoc" href="NSDictionary.html#class$NSDictionary">NSDictionary</a>*)attributes<b> atPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Change the <var>attributes</var> of the file at
<var>path</var> to those specified. <br /> Returns
<code>YES</code> if all requested changes were made
(or if the dictionary was <code>nil</code> or empty, so
no changes were requested), <code>NO</code> otherwise.
<br /> On failure, some of the requested changes may
have taken place. <br />
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-componentsToDisplayForPath$">componentsToDisplayForPath: </a></h3>
- (<a rel="gsdoc" href="NSArray.html#class$NSArray">NSArray</a>*) <b>componentsToDisplayForPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Returns an array of <var>path</var> components
suitably modified for display to the end user.
This modification may render the returned strings
unusable for <var>path</var> manipulation, so you
should work with two arrays... one returned by this
method (for display to the user), and a parallel one
returned by
<a rel="gsdoc" href="NSString.html#method$NSString-pathComponents">
[NSString -pathComponents]
</a>
(for <var>path</var> manipulation).
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-contentsAtPath$">contentsAtPath: </a></h3>
- (<a rel="gsdoc" href="NSData.html#class$NSData">NSData</a>*) <b>contentsAtPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Reads the file at <var>path</var> an returns its
contents as an NSData object. <br /> If an error
occurs or if <var>path</var> specifies a directory
etc then <code>nil</code> is returned.
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-contentsEqualAtPath$andPath$">contentsEqualAtPath: andPath: </a></h3>
- (BOOL) <b>contentsEqualAtPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path1<b> andPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path2;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.0.0</div>
<br />
<div class="desc">
Returns <code>YES</code> if the contents of the
file or directory at <var>path1</var> are the same as
those at <var>path2</var>. <br /> If <var>path1</var>
and <var>path2</var> are files, this is a simple
comparison. If they are directories, the
contents of the files in those subdirectories are
compared recursively. <br /> Symbolic links are
not followed. <br /> A comparison checks first file
identity, then size, then content.
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-contentsOfDirectoryAtPath$error$">contentsOfDirectoryAtPath: error: </a></h3>
- (<a rel="gsdoc" href="NSArray.html#class$NSArray">NSArray</a>*) <b>contentsOfDirectoryAtPath:</b> (<a rel="gsdoc" href="NSString.html#class$NSString">NSString</a>*)path<b> error:</b> (<a rel="gsdoc" href="NSError.html#class$NSError">NSError</a>**)error;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.5.0</div>
<br />
<div class="desc">
Returns an array of NSStrings of the contents of
the specified directory. <br /> The listing does
<strong>not</strong> recursively list
subdirectories. <br /> The special files
'.' and '..' are not listed. <br /> Indicates an
<var>error</var> by returning <code>nil</code> (eg.
if <var>path</var> is not a directory or it can't be
read for some reason).
</div>
<hr width="25%" align="left" />
</div>
<div class="method">
<h3><a name="method$NSFileManager-contentsOfDirectoryAtURL$includingPropertiesForKeys$options$error$">contentsOfDirectoryAtURL: includingPropertiesForKeys: options: error: </a></h3>
- (<a rel="gsdoc" href="NSArray.html#class$NSArray">NSArray</a>*) <b>contentsOfDirectoryAtURL:</b> (<a rel="gsdoc" href="NSURL.html#class$NSURL">NSURL</a>*)url<b> includingPropertiesForKeys:</b> (<a rel="gsdoc" href="NSArray.html#class$NSArray">NSArray</a>*)keys<b> options:</b> (<a rel="gsdoc" href="TypesAndConstants.html#type$NSDirectoryEnumerationOptions">NSDirectoryEnumerationOptions</a>)mask<b> error:</b> (<a rel="gsdoc" href="NSError.html#class$NSError">NSError</a>**)error;<br />
<div class="availability">
<b>Availability:</b> MacOS-X 10.6.0</div>
<br />
<div class="desc">
Returns an array of NSURL of the contents of the
specified directory.
<br />
</div>
<hr width="25%" align="left" />
</div>
<br />
<a href="Base.html">Up</a>
</font>
</body>
</html>
Server : Apache/2.4.41 (Ubuntu)