1) While I wouldnt mind longer var's at all, I have a feeling the limit is within some other functionality of mirc, rather than some limit Khaled just thought up one day. So there maybe some difficulties in implementing this at all (and maybe not)
i agree, and thought that might be true as well. that's why i suggested maybe only allowing certain key aliases to be compatible with the new long variables. this would give us a way to use them without having khaled have to rewrite every alias mirc comes with [or, atleast, that's what my goal was]
2) I didnt even understand what you suggested here, maybe an example would have helped.
sorry about the ambiguity. basically, assume 32 in this example represents the number which was specified with the tokenize command. $1(text goes here) would return text. $2(text goes here) would return goes $2-3(text goes here) would return goes here, you get the idea. the token delimiter, as i stated before, uses either the default of 32, or whatever the person specified in the last /tokenize command.
3) Sounds good, currently i just call a second alias that calls the first one, a bit sucky but hey what can ya do.
yea, same. it's not all that bad, but i did recently run into a situation where that proved to be unsuccessful for me (i can't remember the specifics, but basically it had to do with a timer needing to call recursion, so i couldn't use $!alias to be called in the second alias being called by the timer because the timer re-evaluated aliases with $!)
4) This sounds good, but again, im not sure how workable it might be, From what i have seen there are some limitations of reentry of code in mirc, such as how you cant use $input in an event, even using it in a timer has problems as it seems to halt the execution of other timers untill the one the input is in completes, i have resorted to signals to solve this. Now I assume doing a /Sleep may have the same problematic results (again tho who knows)
i do kindof agree, but with the script snippets that have been made that do this fairly successfully through dll's and such, it seems this might be possible in mirc without too much work *shrugs*
6) nice idea but i think it would take a fundermential rewrite of the scripting engine some how
if that's true, it would still be nice to see a couple of new aliases/props to handle strings in this way (like $gettok,$numtok,$right,$left etc basically aliases that deal specifically with string manipulation.)