Newbie switching from TCL

[paulduffin at my-deja.com]

In article <KqCqtKAJDVo5Ewvr at jessikat.fsnet.co.uk>,
  Robin Becker <robin at jessikat.fsnet.co.uk> wrote:
> In article <8nr6en0mh5 at news2.newsguy.com>, Alex Martelli
> <alex at magenta.com> writes

> >(P.S.: Visual Basic does allow threading [reluctantly, and only
> >in recent releases], but event-handling is definitely at its core;
> >considering that it probably has more users than Tcl, Python, and
> >any one other scripting language you can name put together, it
> >might be considered "prominent"...).
> >
> >
> >Alex
> ....
> true, but underneath a lot of the VB events are threads/processes that
> do the event notification. The windows loop itself which you need to
do
> any significant events is often in a separate thread; when it's not
you
> get the awful unresponsive M$ window which can't be moved while the
main
> app is calculating. A nice article by Steve Uhler (DDJ Sep/99) on
Event-
> Based Servers in Tcl is quite honest about when event or threads are
> good/bad. I think he asserts that non-blocking I/O is a requirement
for
> event driven servers and I seem to remember that the tcl
implementation
> uses a separate thread for that.

Tcl only uses a thread for non blocking I/O on platforms which do not
support non blocking I/O. I think that this only applies to Windows
sockets.


Sent via Deja.com http://www.deja.com/
Before you buy.