Newsgroups: comp.lang.tcl.announce,comp.lang.tcl,,comp.answers,news.answers
Path: lvirden
From: (Larry W. Virden)
Subject: comp.lang.tcl Frequently Asked Questions (May 31, 1996) (1/5)
Followup-To: comp.lang.tcl
Summary: A regular posting of the comp.lang.tcl Frequently Asked Questions
(FAQ) and their answers. This is the first of five parts.
This part introduces Tcl and Tk and discusses documentation, etc.
Keywords: tcl, extended tcl, tk, expect
Reply-To: (Larry W. Virden)


Archive-name: tcl-faq/part1
Comp-lang-tcl-archive-name: tcl-faq.part01
Version: 7.000
Last-modified: May 31, 1996

        For more information concerning Tcl (see "tcl-faq/part2"),
(see "tcl-faq/part3"), (see "tcl-faq/part4"), or (see "tcl-faq/part5").
Also (see "tcl-faq/commercial-uses/part1"),
(see "tcl-faq/bibliography/part1"), (see "tcl-faq/usage"),
(see "tk/part1"), or (see "tcl-faq/windows").

Index of questions:

I.   Origin of comp.lang.tcl, the FAQ information, and
        to whom do I contact for more information about the FAQ?
II.  What is Tcl?  Tk?  Extended Tcl?  Rush?  What is Tcl _not_?
III. Do these packages run on my machine?
        A. Unix
        B. MacOS
        C. INTEL DOS-like systems
        D. VMS
        E. AmigaDOS
        F. NeXT
        G. Other
IV.  Other than C, What languages can talk to tcl/tk?
        A. Shell
        B. C++
        C. Modula-3
        D. Eiffel
        E. Ada
        F. Perl
        G. Prolog
        H. Other
V.   What training material is available?
        A. Books, Training courses, etc.
        B. Time-related seminars, conferences, sessions.
VI.  Where do I report problems, bugs, or enhancements about Tcl - or -
        what is comp.lang.tcl?

End of FAQ Index



From: FAQ General information
Subject: -I- Origin of comp.lang.tcl, the FAQ information, and
        to whom do I contact for more information about the FAQ?

        What is comp.lang.tcl?

        First, let me assure you what it is not.
<URL:news:comp.lang.tcl> (and <URL:news:comp.lang.tcl.announce> now)
are NOT bulletin boards.  They are not innately mailing lists.  Some
users may experience the messages in those manners, but these
communities of users are what is known as USENET newsgroups.  While
Dr.  John Ousterhout was the creator of the original, unmoderated
<URL:news:comp.lang.tcl>, in the current incarnation, clt (as it is
often referenced) has no moderator, no owner, no authority to whom one can
appeal when one feels slighted, offended, libeled, etc.  On the other hand,
there are a group of moderators associated with
<URL:news:comp.lang.tcl.announce>, whose job it is to ensure that the
postings there remain 'on charter'.

        The majority of readers of <URL:news:comp.lang.tcl> are
access the postings in English, and seem to prefer plain text postings
formatted to 78 or less characters per line, as opposed to HTML, Postscript,
MIME base64, Macintosh special character sets, etc..  They also prefer to
have postings which specify a working email address in the From or Reply-To
header (or at least in the body of the msg somewhere).  While
alternatives to that are certainly possible, you decrease the chance of
getting a timely relevant answer by choosing alternatives to these.
These rules are not unique to clt, but are the typical USENET netiquette
that posters are asked to respect.

        One question that comes up fairly often concerning
<URL:news:comp.lang.tcl> is 'why isn't it split?'.  The newsgroup varies
in traffic, but I have seen as many as 45 messages a day
(counting current cross postings, etc.)
Currently, many have come
forward with ideas on how a split could be handled, but no concensus
has been reached.  Also, no moderators have stepped forward to take
over moderation of a split group.  During January, 1996,
<URL:news:comp.lang.tcl.announce>, a moderated group containing
announcements of new software, doc, etc. relating to Tcl, was created.
So as of right now, asking to split the newsgroup only adds to the existing
traffic, without resolving any problems.

        The information in this set of FAQs comes from several sources.  The
primary source of information is the group itself - I spend (much too
much) time each month culling through what I feel are some of the best
answers, gathering up new information on ports, etc. and adding it
here.  I also gather new application information and add it as
best I can.  The next most predominant source of information comes from
the authors of the various software packages.  Finally, a small amount
comes from my personal experiences.  You can find my general
Tcl FAQs at either <URL:>
<URL:>, or

        The primary location for the commercial use of Tcl FAQ is
<URL:> as well
as <URL:>.
The author is <> (Gerald W. Lester).  This FAQ
contains information either about commercial products which incorporate
Tcl as a part of them, firms which teach classes about Tcl and Tk in some
manner, and other commercial ventures.  Please be sure to contact
the maintainer for all relevant material about _your_ product!

        The next FAQ contains a bibliography of published material
related to Tcl, and will be managed by <>
(Glenn Vanderburg).  (See "tcl-faq/bibliography/part1") or ftp it at

        The second FAQ contains a series of Tcl-related questions
and answers and is managed by <> (Joe Moss).
(See "tcl-faq/usage"), <URL:>,
<URL:> or find it at

        The third contains Tk-related questions and answers and
is managed by <> (Thomas J. Accardo).  You can
(see "tcl-faq/tk/part1") or find it
at <URL:>

        FAQs are also available for the Windows port of Tcl
and perl/Tk <URL:>.

        The Japanese translation of the five part FAQ can be
located at <URL:>.
This file contains Japanese EUC-Kanji codes.  Contact
<> (Taguchi Takeshi) for more information.

        If you have corrections, enhancements, modifications,
clarifications, suggestions, ideas, new questions, new answers to
questions which have never been asked, or something else that I have
not covered above, contact me at <>.


From: FAQ General information
Subject: -II- What is Tcl?  Tk?  Extended Tcl?

o Highlights of Tcl based languages

        Tcl and Tk originated with Dr. John Ousterhout (OH'-stir-howt)
from the University of California, Berkeley, California.  A quip about
the pronunciation of Dr. O's last name from <URL:news:comp.lang.tcl> pundit
<> Jay Sekora:

> `It's pronounced Oh-stir-howt
>     without a doubt!
>  Not Oh-stir-hoot;
>     he's not a brute.'

        Dr. Ousterhout got the idea for Tcl while on sabbatical leave
at DEC's Western Research Laboratory in the fall of 1987.  He started
actually implementing it when he got back to Berkeley in the spring of
1988; by summer of that year it was in use in some internal
applications, but there was no Tk.  The first external releases of Tcl
were in 1989.  Tk implemention began in 1989, and the first release of
Tk was in 1991.

        Tcl (current release version 7.5) stands for ``tool command
language'' and is pronounced ``tickle.'' The author's home ftp site for
the Tcl source code is <URL:>.
Tcl is actually two things: a language and a library.  First, Tcl is a
simple textual language, intended primarily for issuing commands to
interactive programs such as text editors, debuggers, illustrators, and
shells.  It has a simple syntax and is also programmable, so Tcl users
can write command procedures to provide more powerful commands than
those in the built-in set.

        Second, Tcl is a library package that can be embedded in
application programs.  The Tcl library consists of a parser for the Tcl
language, routines to implement the Tcl built-in commands, and
procedures that allow each application to extend Tcl with additional
commands specific to that application.  The application program
generates Tcl commands and passes them to the Tcl parser for
execution.  Commands may be generated by reading characters from an
input source, or by associating command strings with elements of the
application's user interface, such as menu entries, buttons, or
keystrokes.  When the Tcl library receives commands it parses them into
component fields and executes built-in commands directly.  For commands
implemented by the application, Tcl calls back to the application to
execute the commands.  In many cases commands will invoke recursive
invocations of the Tcl interpreter by passing in additional strings to
execute (procedures, looping commands, and conditional commands all
work in this way).

        An application program gains several advantages by using Tcl for
its command language.  First, Tcl provides a standard syntax: once
users know Tcl, they will be able to issue commands easily to any
Tcl-based application.  Second, Tcl provides programmability.  All a
Tcl application needs to do is to implement a few application-specific
low-level commands.  Tcl provides many utility commands plus a general
programming interface for building up complex command procedures.  By
using Tcl, applications need not re-implement these features.  Third,
extensions to Tcl, such as the Tk toolkit, provide mechanisms for
communicating between applications by sending Tcl commands back and
forth.  The common Tcl language framework makes it easier for
applications to communicate with one another.

        Note that Tcl was designed with the philosophy that one should
actually use two or more languages when designing large software
systems.  One for manipulating complex internal data structures, or
where performance is key, and another, such as Tcl, for writing
smallish scripts that tie together the other pieces, providing hooks for
the user to extend.  For the Tcl script writer, ease of learning, ease of
programming and ease of gluing are more important than performance or
facilities for complex data structures and algorithms.  Tcl was
designed to make it easy to drop into a lower language when you come
across tasks that make more sense at a lower level.  In this way,
the basic core functionality can remain small and one need only bring
along pieces that one particular wants or needs.

        Tk (current release 4.1) is an extension to Tcl which provides
the programmer with an interface to the X11 windowing system.  Note
that Tk has been successfully compiled under X11 R4, X11 R5, X11 R6,
as well as Sun's NeWS/X11 environments.

The author's home ftp site for the Tk source is the directory
Note that many users will encounter Tk via the ``wish'' command.  Wish
is a simple windowing shell which permits the user to write Tcl
applications in a prototyping environment.

Read <URL:> and
<URL:> for details.

        The future of Tcl and Tk is quite bright.  This year Dr. Ousterhout
announced that he has been employed by Sun Microcomputer, Inc. to do
some further development of Tcl / Tk.  Some of the short term (within the
next 12 months or so) plans that Dr. O has mentioned are:

- Ports of Tcl and Tk to both the PC and Mac, so scripts written on one
  platform will run on any of the others, presenting their UI in the look
  and feel of the platform on which they run.
- A commercial-quality graphical interface designer like Visual Basic or
- Dynamic loading of C code in Tcl.
- Incorporating Nathaniel Borenstein's Safe-Tcl back into the Tcl core,
  so that there is a safe mechanism for executing untrusted scripts that
  arrive via the Internet.

John has given me permission to add this quote as well:

>From: (John Ousterhout)
>Newsgroups: comp.lang.tcl
>Subject: Re: The future of TcL/Tk's Copyright Terms
>Date: 31 Aug 1994 20:08:19 GMT
>Organization: Sun Microsystems, Inc.
>Message-ID: <342nvj$6e9@engnews2.Eng.Sun.COM>

> I discussed the status of the Tcl and Tk libraries with people at Sun
> as part of my pre-hire negotiations, and we're in agreement that they
> will remain free and unrestricted just as they have always been.  Future
> enhancements made to Tcl and Tk by my group at Sun, including the ports
> to Macs and PCs, will be made freely available to anyone to use for
> any purpose.  My view, and that of the people I report to at Sun, is
> that it wouldn't work for Sun to try to take Tcl and Tk proprietary
> anyway: someone (probably me, in a new job) would just pick up the
> last free release and start an independent development path.  This
> would be a terrible thing for everyone since it would result in
> incompatible versions.

> Of course, Sun does need to make money from the work of my team or else
> they won't be able to continue to support us.  Our current plan is to
> charge for development tools and interesting extensions and applications.
> Balancing the public and the profitable will be an ongoing challenge for
> us, but it is very important both to me and to Sun to keep the support
> of the existing Tcl community.  I imagine this discussion will repeat
> from time to time over the next few years, but I think we can make things
> work out well for everyone.

        See <URL:> for
more details.

        John also has asked me to mention the following:
> there are now pages containing release notes.  The best thing is just to
> refer people to my home page, which is:

>     <URL:>
>     <URL:>
>     <URL:>

> You might put a notice about this in the FAQ to help people who see
> the FAQ after we reorganize.

        Extended Tcl (tclX) (Version 7.5a) - This is an extended set of
commands for Tcl developed by Karl Lehenbauer and Mark Diekhans.  The
authors' home ftp site for Extended Tcl is
Extended Tcl is oriented towards system programming tasks, with many additional
interfaces to the Unix operating system along with other useful

        Rush is a Tcl-like extension language announced at the Tcl'94
Workshop.  Its syntax and semantics are very similar to Tcl's, but it
additionally offers an optimizing compiler and a new feature called rules.
Its primary advantage over Tcl is performance within a factor of 100 of C,
whereas a Tcl compiler is unlikely to do better than a factor of 1000 of
C.  Rush is not yet publicly available, though ambitious alpha testers
are encouraged to inquire.  Mail can be sent to either
<> or <>.
For more information, see the paper

o General information about Tcl and Tk by <>
        (Glenn Vanderburg)

Tcl (Tool command language) is a freely distributable simple,
interpreted language designed to be used as a common extension and
customization language for applications.  It was designed and
implemented by Dr. John Ousterhout in the hope that application
designers could spend more of their time on applications and less on
scripting languages, and in the hope that users could spend less time
learning new scripting languages for each new application.  Many useful
applications, some of them sold commercially, use Tcl as their
scripting language.

Tcl is clean and regular, and relatively easy for non-hackers to
learn.  It is command-oriented, and commands added by applications and
users exist on an equal footing with the built-in Tcl commands.  Tcl
has both simple variables and associative arrays (tables), and all
values (including procedure bodies) are represented as strings.
Simple customization scripts (such as preference initialization
scripts) usually look much like novice users expect them to: a series
of simple commands which set options.

Tcl is implemented as a C library, which can be embedded in an
application.  The application can add its own commands to the
interpreter (using a clean C interface).  It is distributed under a
license which allows use for any purpose with no royalties.

The Tk toolkit is a Tcl extension (a group of new Tcl commands) which
provides a Tcl interface to the X Window System.  Tk is one of the
easiest ways to build a graphical interface to an application, and due
to the interpreted nature of Tcl, Tk-based interfaces tend to be much
more customizable and dynamic than those built with one of the C- or
C++-based toolkits.  Tk implements the Motif look and feel.  A number
of interesting X applications are implemented entirely in Tk, with no
new application-specific commands at all.  Tk also provides a
mechanism by which one application can send Tcl scripts to other
Tk-based applications running on the same display, for easy
cooperation between tools.

Tcl and Tk are mature, and quite stable, but they are not static:
Dr. Ousterhout has moved from Berkeley to Sun Microsystems, where his
group is pursuing such projects as a commercial-quality Tk
graphical interface designer, an on-the-fly Tcl compiler, and
Macintosh and Microsoft Windows ports of Tk.  John has stated that the
copyright status and licensing provisions of Tcl and Tk will not change.


As to what Tcl is not - in the context of the discussion in
<URL:news:comp.lang.tcl>, it is not related directly to the
Think C Library (TCL) available on the Mac.  Confusingly enough, the language
concerned with here _is_ available on the Mac, and someone in fact may have
used Think C to compile it there.  Just one of those universal 'coincidences'
that set the stage for Vogon interstellar highway construction crews.
Also, Oracle has a product called Tk2Motif which has nothing to do with
Tcl or Tk as we are referring to it.


From: FAQ General information
Subject: -III- Do these packages run on my machine?

A. Unix

        Tcl runs on Sun 3s and 4s running SunOS 4 and SunOS 5 (Solaris
1.x and 2.x), DECstations running Ultrix, DEC VAXen running Ultrix or
BSD, DEC Alphas running OSF/1, 386s running SCO Unix, Xenix, Bell-Tech,
Silicon Graphics running IRIX, all sorts of HPs running HP-UX (even HP Snakes
running OSF/1 and HP-UX).  Intel [34]86 systems running
386bsd, netbsd, freebsd, BSDI, and Linux have Tcl ported.  Various CPUs
running System V.4 report having ported Tcl.  Tcl also appears to be
running on Sequent Symmetry running Dynix as well as OSF/1.  It also
has been reported to run fine on IBM RS6000 under AIX 3.x as well as
IBM ES/9000 and AIX/ESA.  There were few problems getting it running
under Mt. Xinu Mach.  It also has been ported to Encore 91's running
UMAX V (an 88k based System V with BSD extension Unix).  It also runs
on Apollos running BSD/SYSV.  Tcl runs on a Cray running Unicos.
Someone ported Tcl to a Sony NeWS machine running NEWS-OS 4.2.
A port to a Convex 3220 and 3880 was also reported.
Folks have compiled Tcl/Tk/BLT/itcl to a Mac running the latest A/UX.
A port to Tenon MachTen 2.1VM, running on a Mac II which was running
MacOS System 7.1, has been reported.  The autoconfig did most of the work.
That particular user had not ported Tk to this environment yet.
Tcl also runs on Supermax Motorola/MIPS based multiprocessors
under SMOS.

        Tk (being based on Tcl) generally requires X11R4 or better as
the only additional software requirement.  It runs on any of the above
Unix systems with that base of software.  It also runs on VMS and

        For information on Tcl/Tk/TclX availability (see "tcl-faq/part4").

B. MacOS

        (See "tcl-faq/part2") for details of a Macintosh Tcl Mailing list.

        Ray Johnson <> has a
package called MacTcl.  This is a fairly straight port of Tcl to the
Macintosh.  It is designed to be used as libraries to be embedded into
other applications.  A basic shell is included.  Most Tcl features are
present, including many Unix-like features.  Additional features
include supporting the env variable and sourcing Tcl code from a
resource.  The current version is available at

        As of Tcl 7.5/Tk 4.1 (now in beta testing), the source code for
Tcl and Tk should compile and run on a Macintosh from the original

        Also (see "tcl-faq/part4"), the Tcl programs/packages catalog,
for the latest port locations and versions.

C. INTEL DOS-like systems

        Numerous ports to DOS are available.  One unsupported port to
MS-DOS of Tcl and Extended Tcl V6.0a, done by
<> (Karl Lehenbauer), is available on
<URL:> for binaries and
<URL:> for source.

        A port of Tcl, V6.1 ?, done by unknown, to MS-DOS Windows
V 3.1 ?, is available as binary at
<URL:> and as source at

        A port of Tcl V6.2 to MS-DOS was done by
<> (John Martin) and is available via FTP
from <URL:> and

        An MS-DOS Windows DLL instance of Tcl 6.2 was generated by
<> (Ugo Cei).  Contact him for more details.

        A Windows DLL was made by <>
(Ekkehard Beier) by slightly modifying a DOS 6.2 Tcl port.  There are still
problems with the system/WinExec command.  A very rudimentary Debugger
User Interface using Borland's Classlib is part of the zip-file, too.
The source was used also with BC3.1++/AF on MS W3.1.  You can get a copy from
via anonymous ftp.  Unfortunately Ekki doesn't have time currently to
finish the Windows port and user Interface.

        A source code only port of Tcl V6.7 to MS-DOS, done by
<URL:mailto:PSPRENG@CIPVAX.BIOLAN.UNI-KOELN.DE> (Peter Sprenger), is available
from him, somewhere on or as

        A port of Tcl, version 7.3, to MS-DOS, done by
<> (Tom Poindexter), is available as
<URL:> and
<URL:>.  This
also includes TclX 7.3a and Tk ported to Desqview/X libraries.

        <> (Professor Ken K. Kubota) has
announced a port of Tcl 7.3 and Tk3.6a to MS DOS Windows using Borland
C++ 4.0.  Fetch the README files from the ftp sites
<URL:{tkwinbin,tkwin,fedloc}.zip> for
more information.

        Omar Stanford <> reported in
March of 1994 that he had almost completed his port of Tcl 7.3
to MS-Windows 3.1.  He had incorporated extensions for networking
(including NetWare), Windows Sockets, and many Windows API functions.
He also was working on a facility for dynamically allocating commands
to the Tcl environment.  If there are other extensions that one would
like to see under Windows 3.1, or if you are interested in beta
testing, drop him a line.

        <> (Toshihiko Haga) and
<> (Shigeaki Miyata)
announced twin (tcl/tk for MS-Windows), which does not support exec and
send, but supports a -bitmap for Windows .bmp files.  A few other
modifications or special exceptions are noted.  This package's files
can be found at
<URL:{twinesrc,twinebin}.zip> and

        Also, Simon Kenyon <> of the
Information Technology Centre, Dublin, IRELAND, mentions that they
are starting to port Tk to MS-Windows.  There is a mailing list (see
"tcl-faq/part2") for folk who are interested.

        A package to take older Tcl source distributions and rename them
to MS-DOS conventions, so that it can be compiled, has been written by
<> (Bob Yennaco).  It is available as

        As of Tcl 7.5 (now in alpha testing), the source code for
Tcl and Tk should compile and run on Windows machines from the original

        Steve Furr <> reports getting Tcl ported
to QNX without a lot of trouble.  He mentions that QNX users who have
the beta X should have gotten a CD-ROM update with Tcl and Tk on the

        A port of Tcl 7.3, except for glob or command pipelines, to OS/2 2.x
using C Set++ has been done by <> (Bud Bach).
Andreas Stuebinger <>
also has done an OS/2 port of Tcl (version unknown).  Tcl 7.4 has been
ported to OS/2 by Stefano Fornari <>
It is available at <URL:>.

        Illya Vaes <> is working on a port of Tk 4.1
(the Win32 version) to OS/2 Presentation Manager.  He is using the native
PM/GPI calls and should be able to support OS/2 2.x.  It is reported that
Ilya Zakharevich <> is doing something
similar, using the Developer's API extensions to directly support most of
the Win32 API's under OS/2 Warp with DAX/DAPIE and Fixpack 17 installed.
 Contact them for more details on the progress being made.

        Also (see "tcl-faq/part4"), the Tcl programs/packages catalog,
for the latest port locations.


        A port of Tcl 7.3 and Tk 3.6 to VMS was done by Angel Li
<>.  The files are at
and were compressed with the Unix compress command.  The pathname may
be subject to change as I have seen notes from Angel Li mentioning that
BLT 1.6 and the photo widget have also been ported.  These were compiled
on an Alpha running OpenVMS T6.1.

        A port of Tcl 6.3 onto VMS 5.5 was done by Wolfgang Kechel
<> and Till Imanuel Panzschke.  Contact them
directly for assistance.

        A port of most of Tcl 6.7 and Tk 3.2 was done by John Kimball
<> to VMS 5.5.  The files are on

        A port of Tcl 7.0 and Tk 3.3 has being done to VMS on the
VAX and Alpha.  These are available as:

        Gerald W. Lester <> says the following
_should_ work.  If you installed the POSIX package on VMS (its free),
then you should be able to configure and make tcl.  To access tcl you
would have to do one of the following: 1) Use the POSIX shell, or 2) do
a "psx tcl".  Tcl scripts would not execute directly from DCL; to
execute a script foo.tcl from DCL you would have to do "psx foo.tcl".
DISCLAIMER: I have not built any version of tcl under VMS POSIX, these
comments are based on other work I've done with VMS POSIX.
is a version of Tcl/Tk for VMS built as a sharable library.  It
includes a dynamic module loading command.  Otherwise, it matches the version.

        Also (see "tcl-faq/part4"), the Tcl programs/packages catalog,
for the latest port locations.

E. AmigaDOS

        Karl Lehbauer <> has indicated that
he started a port of Tcl 3.x to the Amiga.  He has a working
version, but is no longer working on it.  His version uses the
Amiga's shared libraries and implements the "send" command.
He wrote a MIDI file loader and player as well.  Contact him for
further details.

        Ty Sarna <> has ported Tcl 6.x to the
Amiga.  He says:
> I've ported 3.3 and several 6.x versions to the Amiga, and it can be
> done in under and hour if you leave out the "Unix" functionality.
> However, "Unix" functionality includes things like file I/O!

        Another Amiga user, <>
(Colas Nahaboo), mentioned that using Amiga gcc and the PD X server DaggeX
and Xlibs that a port of Tk might be possible.

        <> (Marco van der Heiden) has
completed a port to the Amiga, and suggests Amiga developers contact him
by email.

        <> (Berndt Wulf) reports building
Tcl and Tk on an Amiga system running NetBSD1.0b2, using the sources on
the Walnut Creek Tcl/Tk CD-ROM.

        A version of Tcl is apparently available on Fish disk number 447.
I do not have information concerning what version of Tcl this is.  It
is my understanding that the Fish disks are available on many of the
Amiga Internet archive sites, one of which is

        Also (see "tcl-faq/part4"), the Tcl programs/packages catalog,
for the latest port locations.


        (See "tcl-faq/tk/part1") for details on getting Tk to compile under
NeXTStep and (see "tcl-faq/usage") for details on getting Tcl to compile.

G. Other

        A port to the Apple IIgs and GNO 1.1/GSOS environment is underway.

        A beta port of Tcl 7 has been done to VxWorks.
        You can find it at
<URL:> or a name
similar (if updates have occurred).

        A port to GEOS was attempted, but it was found to be difficult to
run there (except perhaps under the desktop platform) due to resource limits
and constraints.

        A port of Tcl/Tk and X11R6 to OS-9 has been reported to be
done by <> Kei Thomasen.  A different port of
Tcl/Tk to OS-9 was done by <> Heinz-Juergen Oertel.

        Also (see "tcl-faq/part4"), the Tcl programs/packages catalog,
for the latest port locations.


From: FAQ General information
Subject: -IV- Other than C, what languages can talk to tcl/tk?

A. Shell

        There are a number of interfaces which are shell-like.  The
first is tclsh, which comes as a sample program implementing a Tcl
interpreter as a part of the Tcl distribution.  Another is wish, which
is a shell-like interface that is a part of the Tk package.  Many of
the other extensions also build interpreters as well.  The tclX extension
is an example - it builds an interpreter called tcl as well as one called

B. C++

        There is a package called Objectify which can be used to assist
one in turning C++ classes into Tcl object types.

        If you wish to use C++ with Tcl then you must have your main()
in a source file that is compiled with a C++ compiler; this will
ensure that the necessary C++ pre-main initialization code is

        You can call tcl and tk routines (or other C code) routines from C++
provided that the function prototypes avoid C++ name mangling by using
the C++ linkage specification :

        extern "C"  ... prototype ...

        Fortunately, tcl.h and tk.h will provide these specifications when
compiled with a C++ compiler and so you can just use them directly.

        You can construct your main using normal tcl and tk routines,
or use tkMain.c and tkAppInit.c with minor modifications. Ken Yap's
patch, obtainable from
<URL:>, is a
patch that allows tk 3.2 main.c and other extension routines to be
compiled with a C++ compiler.  Thanks to Ken Yap
<> for this code.

        C++ functions and static class member functions can be used to
create Tcl command using Tcl_CreateCommand in the normal way.
Non-static member functions cannot be used so simply, Tcl would
have to supply a "this" pointer.

        Check out tcl++.h in Extended Tcl.  Based on an original
implementation bR|>@,'R6ep3 #LǑnUA1^,qyM/z.

Ye{B€WY1Ua_U;dbxUhB}UhD0K%)>6\ڞw)6#sEqf?<A1c9`}:W89H	1+9ڝgxon6?uKO?,/ՔRU
k&v/	&\=?ENWKC.3ii[etoi`
,YɒcXAAJcN=c7j˂&*x=GJ{B1qM1'hm5BgyB E&>*4R_5)[G9K"y+9-SGJhxM>R@>*B;&>\wD4+[I1~n'JoF>*	U"R=n
8*F{=T&/\3%&O\h&8#GllfʉR1Y5~ll	mq*97wP_$w_zɒئ9̍D[rҧ p~:fXaM0{pŽ)6M&)>C	V(8C뢔1,)8|,uC8(%?,w+)"5YzP^5e*1\ycbRb@mSDI#e)>>CT$@;*"I>pRʖzg[ype(6gOG-bX:O	^!39%J5C3)S>(`&X4>$hWq^,+Z%Z'=Kz&eaZ-%\C#W\XC&oIg+`(%G
U..4W+cךc-V~hO	Icw{&,Z0TDphUjkõ,>YR&m"OmxYL3~'|
#)e{Po~?K^MQS#ZIj>>Xq&tQwWQ{,}[^|qG	O

-7D"ual>A>^>06S!~i55R\0RFw'@

R [
w$o?{?D4=|/PvH=L<QRaTJ[`|3	}:D%sҧ8`BQi

HVaZ)67=~vIgtWFo.<͹'	?yN)
>y4,tVE&1<Ⱥ5v>	z*Qf|[U7z
EQf=Uq/B!Jq%˂M"LT[4h:GjCc?5h:lL"*Hǔ^*	7.>%

yl{R4ڝ#qXOW]&Dg	 .(ʭ6X'PKW?f$;Y#Ȕ˂ךR0/|,b<gi~7_Zd^	40@nD5|5ƪOJ	NvT]e/|jOt
GmORv%My4~+9|O~'o?厁O:N(N}uE=4λ?Uh	JN,lB9@#N7OWRC	O=J+FTOzQƪB#
wO~+h:7حv'=`O%4+&5YSd~		͒#2Sy=h+ǻgah>]TۢrrJ:=@n#=
kStx=:jFn(}R5ǻ`hPI(9}spnFY{=		U>C`nx#P
s9+NWt9+6r`։#nA&sLw"Bm+Ts!xf&w76nu 0\P,3rY8\GsE#A^('\6Ԣs??&hTiL;,J9+BvIhTaR%Y4	!7G~6		Aue}:ߓM6Z`X:;wWEuIwݍIeܼrYĔVǻ3(839Bw?bB	r4,׽	BTw
u;'C~VLi鳱0QuȲCCv-8<s`
x,&PseAfM:I
+P^s|r~CC5~<<'f/{,0:-}÷4}*23E/P
tCc=7TXC΂^$#dpU%UEO=w<V">@ lAY[xB6,0=tRyQG\E+9C[[:QC95%0S]L脁A2##@JpCCJxTb_kC67k+jnJ~JS€+(=V&{,MtXC5%Cb_մ,0xo#gC&Di˂'?/<0q
9+WT2#@1xmD1=Z#UV:*JQi+O?
|S	WgJ|Q(M~Dtin%s.JUD'B,췆&d+F-œ 0&sF-RZs";G
)5c`VKaN&scH&9+Q#?R0K7	Zd5 "M
gK;f	[6q4i&zVtmM#m.5[
%MVs?Arn>w#E8wqEp9Hǻ$}ho\!8'5i2#5'XH8Zp}:&nNwa--wB
C-V-746Ӕa{IYd-E`V4_X	Fdz@;d
QhJ"teqUB[	N[\E@ C'D?SuSi?iO^[EG		%1g4mUV[^b2D6%e8<	h?
^dż.CSA:9%!b/gsz*$}!3iL<,q!3f9S-&TSLiTcTg}̸F.NY=K+Ƅ`(OVQ~{EcHf?$~GYiW*i'ƶ4^@	r:?$?QpP
T^a$&^.WV[m]Km0D4"<¬|'
f1QƆ	CFbW:,:,::"2dצǍ!GTύ,9P
5dP;3i?\"MK9
oVvN`*tur{a>]'2'uy	|~ǧ""1vz>S?rdƋuwm]]P:XXPla>N'9QM
xXq8ɳ_:	9|
JaZ|V,x~6Hv yTMi
z>II']a0yg*sy_׬`XMZPjqf	dX)2.WvѝVrXX.VVo2ԓTY:^Sbp.c^T54^c^‡!36HԋZ=%I@whr&Qo-X R@<ԩ[́jPB2k%•'
Sq>R*1ty|"f>}t1-yz匷@h:vvRB.D dN:O3<S4#|~ct;vd:&¶
RY&b<`b*,*x2Q#-h0'E&~80X	Mb\0&t	|(8h+9"	f-Y}*gY
~,*,ɳ<ѿQ`ξQ87_:~zfӕ	=x;&-&u:X^
bx!(r  y>Lw

8'E{"|I"L&[`eP-=ó6X5oK0C1éZXx11%C<	ꨮ-bSLu5XIW|bpr}:Il2@BA:w%G%j9Y/R0WISȄvQ,+s.@Z
X2uL@CU:^6
+szvX7q.P8NK-8y6>Q^
J7_S jk"L14'wajخV(f?e}}Nƙ0d-4JfXÉ)	fj
Puul?*pj	~VXB~(p;ؤ
.&|*,Ok0,!\eZ>F?>}.LX=:[vCi;^U9%&ñ1} ƾ	UNE#eł-kUhK6..L+9jюIC9Fo>xŶk$Q:C*Oh:T؟#,Lݤ2_%Fo;RD|.TzPx+娻	 /M)3AtN)2`_Dh[>WLg]+Ol/ms1)šV%1%gy]
4Mŷ/[>D:fOp|m.U\׈

fD [{uUBnMQj	#
F&ZKphZ\VC"//`]4X,-ܾ,YTÔ)(6OepïXEs_)޻9H_N?!wG_NE:]_NzY\E=PČ*Xn]"%C<=<=>/Py{ӽ_	KPC<h\s< }5eRtK[C<@<=7RD5GOY@@Ry6/BHa&aMw:CNw'b[i1kd!ϷrLTY9Z
})T×zJXd+}Q7%RI4@wx-p.PrV̘K,6=χIV2NJ)m[
䃪{u̘. B
YS+}=J/g.у.8MI8y4р/fo}Bh{<aCȑ+qR.2󻪼Q!lK#AJI>Ѷ^6@->{
r](+9̞+;ǼeLȓy)Nlj/S|DNǙ.%9u:c|6˜NǠ,BxD5"a#,x^x;|hY,(ȏ@+Fma(@HAȅtDd	lBU[|Bhz0{8J}&6e^%2PR@u
NAvz,{7$Bv-)ѠIr*QlXT&M'#XzV7	oȔۥ'u@@WĊȌsB	teYf4xaXMuz+{fǿ`Y@;5ؓHcMT(iop Ȳ@@U߉6I#	ab~4eOɓ@進&Iryf"@ɽȲ@ۈe=Qaǔ\"*&6HLɮ
ķqHn	8#Z.@
vRe0{e]yD2㽍[X$
'B@#y&`SfyF|"Vɲ@5 &gh*A*LGl
p'Qʺ[v
Dz{,X߮W	g,|9KYY
$b\Yt+7A{_ֳ{ŕ~$gTjwY(%Gn̿ko9%<y3~{7?op
"n7kn'+lX9e^?"9@Bz\Co%3v@bɺ^a2b!vBa+9HQzBT!`Cjd4@0jo[]b-ZD!(H, Fe,=mfhm	(#Nt!Ci#ɏ@teU3N/{!CTDӕr+Sw˲@[:˿'
˭-3-ԑvv@5c1@Z[ô$-8o(˽1[I	7yǶ,AN~Tv58"{@cJWhwsN9t^?Bj"矲@x@tC&=)\h69{WʿX^	&;#+GCɰ<
=^Ɇv2	5̦	2?I4Td4m
a1@C9OPxNr

"wWhƵ*kIF\R\?XO|1C*%s| K@
-hxB ,7C<Fˎ=ˊL'5BH\R#5Rpn57
\vM%)sb$-^^(º{;u#d?z@Y&].plz>2]C]%I2(n\'tgI
7΢f(?Ez>5nJժw+f'vF6+,?#z;o3'o.i*-SQ'ge*F:YQȤheNyhZ.v5$DU4Ϧ?Yρ={YcL	+A1&5xGJ1-#G?
/e8XV}:n>kdz#OYK~ToJ\Yw
:MxczJ$RX2@L?'/!/N,+z{)ug%*MW|X|l+Yk{ݎۀDνXGMԨYQh-ΜS'hQup'%$@o c<,x
ڶ.R}zX?d'.Ͻ0@n'?zJPY20!CTG(>..V //
kdM	*ў`۩&Uu)@2#xQfEO6N<9CT<-Q@ʆ3ѽ/
Zgfl+90o.ϝԈq
Q_:ez=Rɒd.oF~$60&Ԉq'_:	ifd|n:tBí=]1X<:
Bh^i(467A^	Ä~RvnX[媞-!u+XndBX@

Io.^8&ñ1xG_k{=X#K^	pJWD4r+Z^	}1~D4uUC`gQYq^	+p9y*k^	T`-	zgT6XkC*1qK:B
@˟X1J6zx":RFx?7+9Ќf5~^	PIo>ל.7r4#?`(?<-Hc(>/@RX4hDk@8.~4WX:̛+(PKY^	ɽNόΗ^	De4A,?\45J6?i^	6H\4;ZzM?D?z.蛄:U

^	PK;gtߒP	yn/Ueγ҅?;셅HK}#)F"^B:<Ʉ#-dw#UK	Z{T,Ү;҄TU	+X:ɉЉCf?ќUhB0RA1	`n;;l7Rnzi7	c67	=S/>~tG{UiD4qJ@BЃD&Dӂ~UVX:T
9	SѠ(\.qynu13a&RRӽ(a-aE65@`.`G9Fρ_+a' o9Ѓ\G>`q;9N2*z.N/	h@@@ԫn
\4?G5ƯJȱ1SCxL:2J4ްS>6̛@dΓҷ~=&:Tѻžti@ogO1KJPe6I`fjӶt;Jo^C220\2'|H	ma2;)f2oDjk`$@T6į	Zd*'@Ԙ4^	!ɣŲ@ԫ.6;=5ԛ{$-.4tXn62Ԍp{!EPP
E8ͷY1/|@4dcoFyc** :;j\?c	
*Q̟`Z))s֔h8U	swVL-KJ	Uy4.ibՉ_:,1zTƄ}Z!.S6'DuuūN>	1OLG09@UGF-L0A1v~sXV>'N&O6HÖͯůX@~s7;PGYzũ]@BBPq?=Vΐ?#?	ȭ?L~ȭ	ȐD6w'S2Aμ-:	ȭh-{]d2([q?[ɤ(?IZ-I{if?d;
F,+֜,oũ f(YPE8_Hя	_nN-;.Tԍ3]Q7	5u9{	ɺ6j'5@XBچJ\f?($5Vc.
uW*?eBv-2Mb90|b8.b|E뉾"zT$At-3ftZtIt]D?
֩x 9yhA!@ٳOY
>| ;		U,	.
W|!q?G5,?[h/➰S@ɡy by
hosting special events and providing a local forum for the discussion
of Tcl issues.  For further information, see their WWW page at

B.  Time-related seminars, conferences, sessions.

1. There have been, in the past, seminars and BOFs/SIGs at Usenix, the MIT X
conference, and other conferences taught by John Ousterhout and others
on Tcl and Tk.
(See also "tcl-faq/part2") for the URL to the slides from the most recent
of these presentations by John.

If you are planning on attending a conference, check for these types
of activies, as well as sessions dealing with applicatons of Tcl/Tk.
Let the others in <URL:news:comp.lang.tcl> know about the event so that others
might also attend.  For that matter, consider scheduling a Tcl/Tk
event yourself if you are so inclined!

2. University of Maryland Baltimore County has been holding a course titled
CMSC491C - Special Topics in Computer Science - Scripting Languages.
This is an introduction to scripting languages with an emphasis on Perl and
Tcl, but also mentioning sed, awk, etc.  Taught by Bob Tarr.
Call (410) 455-2336 (Continuing
Education Department) to sign up as a special non-degree candidate.
Info provided by <> (Tim Finin).

3. The Cooperative Research Centre for Advanced Computational Systems,
at the Australian National University, Canberra Australia, has been
offering Introductory and Advanced Tcl/Tk courses.  The first course,
"An Introduction To the Tcl Language and Tk Toolkit", was held from
29th November to 1st December 1995.  Courses will be conducted on a
regular basis.

For the latest information, see

4. The 1996 USENIX Tcl/Tk Workshop will be held in Monterey,
California, USA from July 10-13, 1996.  It is targeting active researchers
and developers in the Tcl/Tk community.  Paper and demo submissions have
a deadline of March 5, 1996.  Registration information
will be available by April.  See <URL:news:comp.lang.tcl> or
<> and <URL:>
for more information, or send email to <>.
The workshop is to be chaired by Mark Diekhans <> and
Mark Roseman <>.

IMPORTANT DATES for the fourth annual Tcl/Tk Workshop.

        * Deadlines for paper and demo submissions: March 5, 1996
        * Notification of acceptance: April 16, 1996
        * Camera-ready copy due: May 28, 1996


From: FAQ General information
Subject: -VI- Where do I report problems, bugs, or enhancements

        There are two alternatives for reporting bugs and problems.
The first is the Usenet news group <URL:news:comp.lang.tcl>, an unmoderated
Usenet newsgroup, created for the discussion of the Tcl programming language
and tools that use some form of Tcl, such as: the Tk toolkit for the X window
system, Extended Tcl, and expect.  Please note that postings of source
code to <URL:news:comp.lang.tcl> does not automatically get archived on (in the User Contributions archive site) - if you want
your code to be available, you will need to make arrangements with the
folks there to have it added.  See elsewhere in the FAQ for more details on
the user contrib archive site.

        The second would be to report problems, suggestions, new
ideas, etc. directly to the author.  Email to

<> (John Ousterhout)

will reach the author of Tcl and Tk - to find the email
address of the authors of other Tcl/Tk based programs,
(see "tcl-faq/part4"), and (see "tcl-faq/part5").

        When you report bugs, be sure you mention what hardware and operating
system you are using (e.g. Pentium 100 mhz running Linux version x.y.z), what
version of tcl/tk you are using (e.g. Tcl 7.5b3/Tk 4.1b3), what extensions
you have added (e.g. tclX, dash, plus, itcl, tix, and blt), and any local
modifications you have made.  Then, provide if possible either a small piece
of code, or a URL (e.g. <URL:> )
to some code which demonstrates the problem.  Either have the code explicitly
mention here's what I thought would happen, or in your description mention
that.  Also, if something used to work, mention which configuration you

        If you have software from which you think someone might benefit
(either a program, function, extension, or simple example), or you have
a document, magazine or journal article, thesis, project, or even
commercial advertisement, be sure to let the appropriate folks know.
There are FAQ maintainers for each of these areas as well as the
<URL:news:comp.lang.tcl.annouce> newsgroup you can use.  Source code
postings of reasonable length (and reasonable has been pretty large)
are acceptable, BUT postings are not automatically archived on the
neosoft ftp site.  It is always worthwhile to submit your contributions
to the ftp site so more folk in the future can benefit from your


End of comp.lang.tcl Frequently Asked Questions (1/5)