why-tcl-doesnt-scale.html
1.25 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
<!DOCTYPE HTML PUBLIC "-//W3O//DTD WWW HTML 2.0//EN">
<head>
<title>Why Tcl Doesn't Scale</title>
</head>
<body>
<h1>Why Tcl Doesn't Scale</h1>
<address>
Daniel W. Connolly<br>
connolly@hal.com<br>
$Id: why-tcl-doesnt-scale.html,v 1.1 1994/06/20 16:47:53 connolly Exp $
</address>
<p> Tcl has one great big huge namespace. If look at two libraries from
different developers, there is no guarantee or even any helpful
mechanisms to prevent them from using the same name for some functions
or global variables. Look at emacs-lisp, for example, where every use
and definition of a function starts with some presumably word-unique
string.
<p> (1) it's a pain to key in these prefixes all the time, and (2)
considering that these strings are usually only a few characters long,
it is quite likely that they'll collide.
<p> Python has several features to support highly reusable code such that
code from developers who never collaborated can be safely combined
into one program. There language support for breaking the namespace
into modules, and there are some installation techniques for managing
module names.
<p> Also, Tcl code is interpreted multiple times during the execution of
a program. There is no "intermediate form" of the code as there is
in Python and Perl.
</body>