Comments

APtrackz
Comments: 5
 

I'm very late on this, but perhaps have it ignore the invalid param using /continue? It'd be great to implement this VS. stopping the entire process. Otherwise, fantastic work.

brinxy
Comments: 30
 

I think I'm going to stick with this method. But thanks for your suggestions. ^_^

Lindrian
Comments: 755
 

Max lenght of a variable is usually around 900 ($len() wise).
So you could simply limit it to 900, and if it reaches 900 ull add a message that its full or so. OR!
You can use a hash table (Dont know what the limit is, but obviously easier to deal with when it comes to several ID's).
If none of thats good enough, you can use dyanmic variables, which you'll loop twice.

First you add the items in variable, if it reaches 900, u use variable.1, and so on, and add the id's in another variable
so in the end u might have

%variable.1
%variable.2
%variable.3

%variable.all 3

That way you'll know, "aha, there's 3 dyanmic vars" and then echo the info.

Ill let u figure it out urself ;)

brinxy
Comments: 30
 

Found out that doesn't work either. For now, I decided to put the original back up until further notice. If you receive any errors with this please let me know.

brinxy
Comments: 30
 

Mmm. I forgot about large channels. Heheh. I'll look into binvars, as I do not know much about them. Just curious, if I completely removed $addtok and just used %ret = %ret etc, would that remove the error?

Lindrian
Comments: 755
 

Hehe,
* /set: line too long (line 8, test.mrc)
Knew that would happend. There's a way to fix it, but you'll have to recode or use binvars.

brinxy
Comments: 30
 

lol.

jaytea
Comments: 13
 

you're right, this is where we post comments! :P

jaytea
Comments: 13
 

you're right, this is where we post comments! :P

brinxy
Comments: 30
 

Comments?

Wasabi
Comments: 2
 

Very good. Tried out the samples you put and got no errors. Nice job!

brinxy
Comments: 30
 

Thanks spitfire3292.

spitfire3292
Comments: 36
 

Very well done. It took me a second to figure out why you used regex until I looked back up at all the params that can be used. What I really like is how you can "ignore" a param with a certain specific phrase. Very clever and very well thought out to create very little room for error alphanumeric-param wise :P

brinxy
Comments: 30
 

Thanks, it's quite simple if you're fluent in token identifiers:
Let's say I had the string "this is my string of tokens"...
Now if we typed up //echo -a $multiremtok(this is my string of tokens,1,2,32) would return "my string of tokens" Because it removed the first token, this, and the second token, is.

Any more questions you have feel free to ask and I'll be glad to help. Although this should have been covered in the comments I put into the snippet.

SpotRedDog
Comments: 81
 

Nice although I don't understand how to use it but it looks nice. WTG!!!

brinxy
Comments: 30
 

Most certainly. But I won't change the way I make my comments, used to it by now. And I prefer that way.

mountaindew
Comments: 1,645
 

u can do this for lines and lines of comments in a script

Code:

/* A Lot Of Comments W/O ;'s */

:)

brinxy
Comments: 30
 

Oh I see.

xDaeMoN
Comments: 696
 

Yeah, I noticed those features which is why I said not bad. ;)

brinxy
Comments: 30
 

Thanks xDaeMoN. But I do believe that mIRC's built-in $matchtok will only return one token. Meaning if I used: $matchtok(this is a string,s,1-,32) would only return this. (That's what I got when I tested it.) On the contrary, my snippet uses $gettok when retrieving data so you can use things such as 1-. I guess this is just an enhancement to $matchtok.