last i checked you cant do that in tcl.
You can. You can also do it in Python, Ruby, Lua, Perl or just about any interpreted language since all you need is theinterpreter.exe and some dlls. It would be easier, too, since you wouldn't need to interact with mIRC's UI to do it. The only thing you can't do on a limited account is install programs-- but this is a moot point, since mIRC needs an installer too unless you preinstalled it on a CD or usb key (which you could do with Tcl as well).
do you know of a tcl dll/so for internet control interface? or mci? or using winamp's input/output dlls? i dont.
If by "internet control" you mean sockets, Tcl has plenty of this; so do Python, Perl, Ruby, etc.. In fact, sockets in most of these other languages are significantly easier to use than mIRC. I mean, seriously, compare any mIRC HTTP GET script with:
require 'open-uri'; puts open('http://google.com').readNo comparison. Heck, compare it with full xml processing:
Hpricot(open('http://google.com').read).search("a:link")Returns all the <a> links in your HTML document. This would require many lines of mIRC scripting, and we haven't even done any processing on this data yet.
As far as "winamp input/output dlls" go, this has nothing to do with mIRC. These dlls are specifically made to address a
shortcoming in mIRC. Winamp accepts SendMessage commands the same way mIRC does, but mIRC has no way of *sending* those commands without dlls, so plugins in Winamp need to be made to send the commands to mIRC. Other languages like Python, Tcl, Ruby, all have WINAPI implementations that allow users to use SendMessage from the language to
interact with Winamp directly, so a "winamp plugin for LANGUAGE_X" is completely unnecessary.
In short, and I hate to say it, but most of the need for mIRC script as a standalone language is caused by ignorance of better tools. mIRC is not fast, it's not easier to perform any complex tasks (sockets, xml, large string processing, binary data processing, WINAPI, dialogs all have much better library support in other dynamic languages), it doesn't even have good debugging. The only time mIRC is more convenient than other languages is when dealing with IRC related commands and events because of its event oriented nature and lack of a string construct (respectively). That makes it great for an IRC client, but that's it.
If you're comfortable with mIRC because you only know mIRC, that's one thing, but if you've only used mIRC and are convinced it can solve all of the worlds problems, you need to get out from under your rock and start looking (harder) for more appropriate tools.
