mirror of
https://github.com/gnustep/libs-base.git
synced 2025-04-23 00:41:02 +00:00
Fix a few typo/spelling errors in comments
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk@21961 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
parent
0a7feb53a1
commit
11b4799893
2 changed files with 11 additions and 11 deletions
|
@ -86,7 +86,7 @@
|
|||
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 curtrent
|
||||
In both forms, the names . and .. are refer to the current
|
||||
directory and the parent directory as in unix paths.
|
||||
</p>
|
||||
Here are various examples:
|
||||
|
@ -152,10 +152,10 @@
|
|||
</subsect>
|
||||
<subsect>
|
||||
<heading>Tilde substitution</heading>
|
||||
<p>GNUstep handles substitution of tilde (~) as foillows:<br />
|
||||
<p>GNUstep handles substitution of tilde (~) as follows:<br />
|
||||
If a path is just ~ or begins ~/ then the value returned by
|
||||
NSHomeDirectory() is substituted for the tilde.<br />
|
||||
If a path is of the form ~name or begins wityh a string like ~name/
|
||||
If a path is of the form ~name or begins with a string like ~name/
|
||||
then name is used as the argument to NSHomeDirectoryForUser() and
|
||||
the return value from that method (if non-nil) is used to replace
|
||||
the tilde.
|
||||
|
@ -318,7 +318,7 @@
|
|||
* </item>
|
||||
* <item><strong>"Path"</strong>
|
||||
* contains the path that is being processed when
|
||||
* an error occured. If an error occurs during an
|
||||
* an error occurred. If an error occurs during an
|
||||
* operation involving two files, like copying, and
|
||||
* it is not clear which file triggers the error it
|
||||
* will default to the source file.
|
||||
|
|
|
@ -12,7 +12,7 @@
|
|||
Date: Apr 2001
|
||||
Rewritten NSDirectoryEnumerator
|
||||
|
||||
Author: Richard frith-Macdonald <rfm@gnu.org>
|
||||
Author: Richard Frith-Macdonald <rfm@gnu.org>
|
||||
Date: Sep 2002
|
||||
Rewritten attribute handling code
|
||||
|
||||
|
@ -278,7 +278,7 @@
|
|||
- (BOOL) _proceedAccordingToHandler: (id) handler
|
||||
forError: (NSString*) error
|
||||
inPath: (NSString*) path
|
||||
fromPath: (NSString*) frompath
|
||||
fromPath: (NSString*) fromPath
|
||||
toPath: (NSString*) toPath;
|
||||
|
||||
|
||||
|
@ -360,7 +360,7 @@ static NSStringEncoding defaultEncoding;
|
|||
* Change the attributes of the file at path to those specified.<br />
|
||||
* Returns YES if all requested changes were made (or if the dictionary
|
||||
* was nil or empty, so no changes were requested), NO otherwise.<br />
|
||||
* On failure, some fo the requested changes may have taken place.<br />
|
||||
* On failure, some of the requested changes may have taken place.<br />
|
||||
*/
|
||||
- (BOOL) changeFileAttributes: (NSDictionary*)attributes atPath: (NSString*)path
|
||||
{
|
||||
|
@ -515,7 +515,7 @@ static NSStringEncoding defaultEncoding;
|
|||
* Returns an array of path components suitably modified for display
|
||||
* to the end user. This modification may render the returned strings
|
||||
* unusable for path manipulation, so you should work with two arrays ...
|
||||
* one returned by this method (for display tio the user), and a
|
||||
* one returned by this method (for display to the user), and a
|
||||
* parallel one returned by [NSString-pathComponents] (for path
|
||||
* manipulation).
|
||||
*/
|
||||
|
@ -791,7 +791,7 @@ static NSStringEncoding defaultEncoding;
|
|||
int written;
|
||||
#endif
|
||||
|
||||
/* This is consitent with MacOSX - just return NO for an invalid path. */
|
||||
/* This is consistent with MacOSX - just return NO for an invalid path. */
|
||||
if ([path length] == 0)
|
||||
return NO;
|
||||
|
||||
|
@ -1465,7 +1465,7 @@ static NSStringEncoding defaultEncoding;
|
|||
{
|
||||
return YES;
|
||||
}
|
||||
/* FIXME: On unix, directory accessable == executable, so we simulate that
|
||||
/* FIXME: On unix, directory accessible == executable, so we simulate that
|
||||
here for Windows. Is there a better check for directory access? */
|
||||
if (res & FILE_ATTRIBUTE_DIRECTORY)
|
||||
{
|
||||
|
@ -1744,7 +1744,7 @@ static NSStringEncoding defaultEncoding;
|
|||
/* We initialize the directory enumerator with justContents == YES,
|
||||
which tells the NSDirectoryEnumerator code that we only enumerate
|
||||
the contents non-recursively once, and exit. NSDirectoryEnumerator
|
||||
can perform some optms using this assumption. */
|
||||
can perform some optimisations using this assumption. */
|
||||
direnum = [[NSDirectoryEnumerator alloc] initWithDirectoryPath: path
|
||||
recurseIntoSubdirectories: NO
|
||||
followSymlinks: NO
|
||||
|
|
Loading…
Reference in a new issue