Removed support for Mac OS Classic platform [Patch 918142]

1 files changed, 6 insertions, 62 deletions

diff --git a/doc/filename.n b/doc/filename.n
index 931845a..ef217e6 100644
--- a/doc/filename.n
+++ b/doc/filename.n
@@ -4,7 +4,7 @@
 '\" See the file "license.terms" for information on usage and redistribution
 '\" of this file, and for a DISCLAIMER OF ALL WARRANTIES.
 '\" 
-'\" RCS: @(#) $Id: filename.n,v 1.11 2004/03/09 12:59:04 vincentdarley Exp $
+'\" RCS: @(#) $Id: filename.n,v 1.12 2004/03/17 18:14:12 das Exp $
 '\" 
 .so man.macros
 .TH filename n 7.5 Tcl "Tcl Built-In Commands"
@@ -44,61 +44,6 @@ type of a given path.
 The rules for native names depend on the value reported in the Tcl
 array element \fBtcl_platform(platform)\fR:
 .TP 10
-\fBmac\fR
-On Apple Macintosh Classic systems (i.e. with MacOS 9.x or older), Tcl
-supports two forms of path names.  The normal Mac style names use colons
-as path separators.  Paths may be relative or absolute, and file names
-may contain any character other than colon.  A leading colon causes the
-rest of the path to be interpreted relative to the current directory.
-If a path contains a colon that is not at the beginning, then the path
-is interpreted as an absolute path.  Sequences of two or more colons
-anywhere in the path are used to construct relative paths where \fB::\fR
-refers to the parent of the current directory, \fB:::\fR refers to the
-parent of the parent, and so forth.
-.RS
-.PP
-In addition to Macintosh style names, Tcl also supports a subset of
-Unix-like names.  If a path contains no colons, then it is interpreted
-like a Unix path.  Slash is used as the path separator.  The file name
-\fB\&.\fR refers to the current directory, and \fB\&..\fR refers to the
-parent of the current directory.  However, some names like \fB/\fR or
-\fB/..\fR have no mapping, and are interpreted as Macintosh names.  In
-general, commands that generate file names will return Macintosh style
-names, but commands that accept file names will take both Macintosh
-and Unix-style names.
-.PP
-The following examples illustrate various forms of path names:
-.TP 15
-\fB:\fR
-Relative path to the current folder.
-.TP 15
-\fBMyFile\fR
-Relative path to a file named \fBMyFile\fR in the current folder.
-.TP 15
-\fBMyDisk:MyFile\fR
-Absolute path to a file named \fBMyFile\fR on the device named \fBMyDisk\fR.
-.TP 15
-\fB:MyDir:MyFile\fR
-Relative path to a file name \fBMyFile\fR in a folder named
-\fBMyDir\fR in the current folder.
-.TP 15
-\fB::MyFile\fR
-Relative path to a file named \fBMyFile\fR in the folder above the
-current folder.
-.TP 15
-\fB:::MyFile\fR
-Relative path to a file named \fBMyFile\fR in the folder two levels above the
-current folder. 
-.TP 15
-\fB/MyDisk/MyFile\fR
-Absolute path to a file named \fBMyFile\fR on the device named
-\fBMyDisk\fR.
-.TP 15
-\fB\&../MyFile\fR
-Relative path to a file named \fBMyFile\fR in the folder above the
-current folder.
-.RE
-.TP
 \fBunix\fR
 On Unix and Apple MacOS X platforms, Tcl uses path names where the
 components are separated by slashes.  Path names may be relative or
@@ -185,11 +130,10 @@ the tilde and the next separator are taken as a user name, which is used
 to retrieve the user's home directory for substitution.  This works on
 Unix, MacOS X and Windows (except very old releases).
 .PP
-The Classic Macintosh (OS 9 and older) platform and old Windows
-platforms do not support tilde substitution when a user name follows the
-tilde.  On these platforms, attempts to use a tilde followed by a user
-name will generate an error that the user does not exist when Tcl
-attempts to interpret that part of the path or otherwise access the
+Old Windows platforms do not support tilde substitution when a user name
+follows the tilde.  On these platforms, attempts to use a tilde followed
+by a user name will generate an error that the user does not exist when
+Tcl attempts to interpret that part of the path or otherwise access the
 file.  The behaviour of these paths when not trying to interpret them is
 the same as on Unix.  File names that have a tilde without a user name
 will be correctly substituted using the \fB$HOME\fR environment
@@ -203,7 +147,7 @@ the character sets allowed on different devices may differ, so scripts
 should choose file names that do not contain special characters like:
 \fB<>:?"/\e|\fR.  The safest approach is to use names consisting of
 alphanumeric characters only.  Care should be taken with filenames
-which contain spaces (common on Windows and MacOS systems) and
+which contain spaces (common on Windows systems) and
 filenames where the backslash is the directory separator (Windows
 native path names).  Also Windows 3.1 only supports file
 names with a root of no more than 8 characters and an extension of no