scsh-users
[Top] [All Lists]

Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)

To: scsh@martigny.ai.mit.edu
Subject: Re: Reply to Ousterhout's reply (was Re: Ousterhout and Tcl ...)
From: mkagalen@lynx.dac.neu.edu (Michael Kagalenko)
Date: 10 Apr 1997 00:31:59 -0400
Organization: Northeastern University, Boston, MA. 02115, USA
Paul Wilson (wilson@cs.utexas.edu) wrote in article 
<5iafs1$fh4@roar.cs.utexas.edu> <pre><blink>
]
]The main benefits that the Tcl hackers I know get form Tcl are an
]interactive command loop, and a standard way of gluing together code
]in other languages, and a standard, fairly functional graphics toolkit.
]Those are great things, and you're to be applauded for realizing they're
]crucial for writing glue code before most other people did!  (It certainly
]should embarrass the hell out of the programming languages community, of
]which I'm a part.)
]
]An interactive command loop is incredibly valuable for increasing
]productivity over the usual compile-link-run-crash cycle.  What's
]sad is how many Tcl programmers there are now who've never used
]any other interactive language, and think Tcl is great because it
]has that huge advantage over C++.

 I think you'll excuse me for another mention of NeXT programming 
 environment, based on dynamically-typed language. Interface
 builder allows you to create, change and test interface without
 compiling it. I do not know of any analog of this tool.



<Prev in Thread] Current Thread [Next in Thread>