People are writing a lot of sucky Tcl for AOLserver. Here's an example from a couple of days ago:proc startworker {name} { nsv_set $name mutex [ns_mutex create] nsv_set $name cond [ns_cond create] nsv_set $name queue {} nsv_set $name tid [ns_thread begindetached [list workermain $name]] } Jumping through hoops with low level mutexes and and variables etc., you see it all the time. Why can't we have code that looks like this? ns_serialize { # Only one copy of this code runs at a time } Which brings us back to nsproxy and handle management... :-)
You just showed that it is not Tcl sucks but a programmer that writes bad code in Tcl without using it properly or not in full. That example of your shows that programmer that wrote it has more experience in C and uses Tcl in pure procedure way, which is not that bad, the code works.
-- Vlad Seryakov 571 262-8608 office [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/
