Newsgroups: gnu.misc.discuss,comp.lang.tcl,comp.lang.scheme
Path: cantaloupe.srv.cs.cmu.edu!das-news.harvard.edu!news2.near.net!MathWorks.Com!yeshua.marcam.com!usc!math.ohio-state.edu!uwm.edu!msuinfo!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!mama.research.canon.oz.au!andy
From: andy@research.canon.oz.au (Andy Newman)
Subject: Re: Why you should not use Tcl
Message-ID: <Cwptw3.1ns@research.canon.oz.au>
Sender: news@research.canon.oz.au
Nntp-Posting-Host: jaco
Organization: Canon Information Systems Research Australia
References: <9409232314.AA29957@mole.gnu.ai.mit.edu> <361goe$bfu@news.bridge.com>
Date: Mon, 26 Sep 1994 02:36:02 GMT
Lines: 20
Xref: glinda.oz.cs.cmu.edu gnu.misc.discuss:18260 comp.lang.tcl:19249 comp.lang.scheme:9879

james@bridge.com (James Montebello) writes:
>Tcl also wasn't designed to be used in a vacuum, but to be embedded
>into a larger application. The ease with which this can be done is its
>primary strength.

I'd say that the Tcl's C interface is its only strength. Tcl may be okay
for writing ten liners but rms is really correct in stating that it is
not really suitable for some of the larger things that it is being applied
to.

>If the language lacks features you desire, add them.This, too, is relatively
>easy to do. 

Why spend effort fixing broken things when there are better solutions out
there? (See the catalog of freely available compilers/interpreters for a
full list).

-- 
Andy Newman (andy@research.canon.oz.au) (Not a Canon spokesperson)
"If business is war, the computer business is thermonuclear war". Ted Lewis.
