DN633053837

Subject: Re: Tcl vs Python - DN [1]

Paul Duffin <pduffin@hursley.ibm.com> - 09 Jun 2000 - comp.lang.tcl

 Kristoffer Lawson wrote:
 >
 > I don't want to prove which is better for what. I gather both are good
 > choices for the particular project (maybe one is better than the other,
 > but that's not the question I'm asking). I want the *differences* in
 > the languages -- in particular Tcl with iTcl or XOTcl. How things
 > are thought of differently. How they have been designed differently.
 > What is the "Tcl way" compared to the "Python way". I assume there are
 > differences or there wouldn't be much point having both languages ;->
 >

 The "Tcl way"

 Syntactically / Semantically
     Everything can be a string (used to be "Everything is a string")

     Everything is done using commands.

     All commands are treated equally.

     A command is a sequence of whitespace seperated words.

     Each word in a command is treated the same (*before* passing
     to the command).

 Conceptually
     No artifical limits.

     Provide simple building blocks.

     Things should be as general as possible.

 Community
     Use the best tool for the job. Often Tcl can be the best tool but not
     always.

 I/O
     Event driven is good.

 GUI
     Event driven is good.

 Threading
     Threads are really little processes inside a big process and
     therefore should be isolated/protected from one another.

     Data shared between threads should be explicitly requested.

 Anyone prepared to add a description of "The Python Way" ????
 Please lets not argue over which way is best though.