diff options
Diffstat (limited to 'README')
| -rw-r--r-- | README | 49 |
1 files changed, 25 insertions, 24 deletions
@@ -1,14 +1,15 @@ Tcl -SCCS: @(#) README 1.52 97/11/20 12:43:16 +SCCS: %Z% $Id: README,v 1.2 1998/06/29 18:08:34 welch Exp $ 1. Introduction --------------- This directory and its descendants contain the sources and documentation for Tcl, an embeddable scripting language. The information here -corresponds to release 8.0p2, which is the second patch update for Tcl -8.0. Tcl 8.0 is a major new release that replaces the core of the +corresponds to release 8.0.3, which is the third patch update for Tcl +8.0. This patch provides compatibility with [incr Tcl] 3.0. +Tcl 8.0 is a major new release that replaces the core of the interpreter with an on-the-fly bytecode compiler to improve execution speed. It also includes several other new features such as namespaces and binary I/O, plus many bug fixes. The compiler introduces a few @@ -51,7 +52,7 @@ using the normal "man" mechanisms, such as man Tcl There is also an official home for Tcl and Tk on the Web: - http://sunscript.sun.com + http://www.scriptics.com These Web pages include information about the latest releases, products related to Tcl and Tk, reports on bug fixes and porting issues, HTML versions of the manual pages, and pointers to many other Tcl/Tk Web @@ -70,11 +71,10 @@ Before trying to compile Tcl you should do the following things: available now for PCs, Macintoshes, and several flavors of UNIX. Binary releases are much easier to install than source releases. To find out whether a binary release is available for your - platform, check the home page for SunScript - (http://sunscript.sun.com) under "Tech Corner". Also, check in + platform, check the Scriptics Tcl Resource Center + (http://www.scriptics.com/resource). Also, check in the FTP directory from which you retrieved the base - distribution. Some of the binary releases are available freely, - while others are for sale. + distribution. (b) Make sure you have the most recent patch release. Look in the FTP directory from which you retrieved this distribution to see @@ -82,7 +82,7 @@ Before trying to compile Tcl you should do the following things: without changing any features, so you should normally use the latest patch release for the version of Tcl that you want. Patch releases are available in two forms. A file like - tcl8.0p2.tar.Z is a complete release for patch level 2 of Tcl + tcl8.0.3.tar.Z is a complete release for patch level 3 of Tcl version 8.0. If there is a file with a higher patch level than this release, just fetch the file with the highest patch level and use it. @@ -280,19 +280,10 @@ that are commonly encountered by TCL newcomers. A couple of Mailing List have been set up to discuss Macintosh or Windows related Tcl issues. In order to use these Mailing Lists you -must have access to the internet. If you have access to the WWW the -home pages for these mailing lists are located at the following URLs: - - http://www.sunlabs.com/research/tcl/lists/mactcl-list.html - - -and- - - http://www.sunlabs.com/research/tcl/lists/wintcl-list.html - -The home pages contain information about the lists and an HTML archive -of all the past messages on the list. To subscribe send a message to: +must have access to the internet. To subscribe send a message to: - listserv@sunlabs.sun.com + wintcl-request@tclconsortium.org + mactcl-request@tclconsortium.org In the body of the message (the subject will be ignored) put: @@ -312,7 +303,7 @@ in the body instead (or wintcl). We're very interested in receiving bug reports and suggestions for improvements. We prefer that you send this information to the -comp.lang.tcl newsgroup rather than to any of us at Sun. We'll see +comp.lang.tcl newsgroup rather than to any of us at Scriptics. We'll see anything on comp.lang.tcl, and in addition someone else who reads comp.lang.tcl may be able to offer a solution. The normal turn-around time for bugs is 3-6 weeks. Enhancements may take longer and may not @@ -338,12 +329,18 @@ support for users. If you need help we suggest that you post questions to comp.lang.tcl. We read the newsgroup and will attempt to answer esoteric questions for which no-one else is likely to know the answer. In addition, Tcl support and training are available commercially from -NeoSoft (info@neosoft.com), Computerized Processes Unlimited -(gwl@cpu.com), and Data Kinetics (education@dkl.com). +Scriptics (info@scriptics.com), NeoSoft (info@neosoft.com), +Computerized Processes Unlimited (gwl@cpu.com), +and Data Kinetics (education@dkl.com). 9. Tcl version numbers ---------------------- +You can test the current version of Tcl by examining the +tcl_version and tcl_patchLevel variables. The tcl_patchLevel +variable follows the naming rules outlined below (e.g., 8.0.3). +The tcl_version just has the major.minor numbers in it (e.g., 8.0) + Each Tcl release is identified by two numbers separated by a dot, e.g. 6.7 or 7.0. If a new release contains changes that are likely to break existing C code or Tcl scripts then the major release number increments @@ -379,3 +376,7 @@ Patch releases have a suffix such as p1 or p2. These releases contain bug fixes only. A patch release (e.g Tcl 7.6p2) should be completely compatible with the base release from which it is derived (e.g. Tcl 7.6), and you should normally use the highest available patch release. + +As of 8.0.3, the patch releases use a second . instead of 'p'. So, the +8.0 release went to 8.0p1, 8.0p2, and 8.0.3. The alphas and betas will +still use the 'a' and 'b' letters in their tcl_patchLevel. |