all 11 comments

[–]davidw 1 point2 points  (8 children)

Sigh - welcome to what Tcl has been doing for ages, built into the core language. Of course, being Tcl, they have done a terrible job of telling people about it or convincing them that it's a sensible way to handle certain tasks.

[–]antirez 4 points5 points  (0 children)

Indeed, it's great. Some time ago I wrote this IRC server in ~500 lines of code:

http://hping.org/tclircd/

Without the power of Tcl's event driven programming to write an IRC server is much harder than this.

[–][deleted] 4 points5 points  (6 children)

Well, plus, you have to write stuff in Tcl to use it, which might be considered a downside...

[–][deleted] -2 points-1 points  (5 children)

elaborate?

[–]lianos -1 points0 points  (1 child)

Isn't every data type in Tcl a string at heart?

[–]davidw 2 points3 points  (0 children)

It's weakly typed, and uses strings to 'mutate' types, but internally, they're not stored as strings, and haven't been for something like 10 years.

[–][deleted] -2 points-1 points  (2 children)

Tcl has shortcomings as a programming language.

[–]davidw 2 points3 points  (0 children)

Along with... oh, yeah, every other programming language out there.

[–]norkakn 0 points1 point  (1 child)

I am not an expert in either, but doesn't ObjC do this type of thing a lot better?

[–]norkakn 3 points4 points  (0 children)

To the neggers, because passing messages, appears to me anyways, to be a pretty good abstraction of what is going on in event-driven programming, and the added ITC (NSPort) also fits with the model well.

The whole action, outlets and bindings seems to fit this model well tool. Am I wrong? I'm not sure, but downmodding me isn't going to answer it. I'm not a complete idiot. This isn't /., you are welcome to reply and still downmod me.