mIRC Home    About    Download    Register    News    Help

Print Thread
#116893 10/04/05 01:14 PM
Joined: Feb 2004
Posts: 714
Z
Hoopy frood
OP Offline
Hoopy frood
Z
Joined: Feb 2004
Posts: 714
hi smile

I've got a userlist with 180 lines here. When I type, for example, //echo -a $ulist(*!*@*[color:Red]hey*).info[/color] it returns the .info of another userlist entry. That happens with any word that uses that mask, not just hey:

- *!*@*hiya*
- *!*@*ppp.123.*
- *!*@*hello*

As long as the mask is *!*@*<something>*, it returns the .info of another userlist entry. Not just another entry, but it's always the same entry.

Is it just me?

Thanks,
Zyzzy smile

#116894 10/04/05 03:28 PM
Joined: Jan 2003
Posts: 2,125
Q
Hoopy frood
Offline
Hoopy frood
Q
Joined: Jan 2003
Posts: 2,125
It's not really a bug, it happens because you don't pass $ulist what it expects. $ulist accepts only full addresses, of the form nick!user@host, as the help file says. Remember that when dealing with wildcards, you usually compare a wildcard string to a non-wildcard one, for example *!*a*@bleh.*. against qwerty!blah@bleh.com. It can be confusing to try to match a wildcard string against another wildcard one, and that's what happens in your case. $ulist accepts your wildcard input, but interprets it as it sees fit. So, *!*@*hello* can match *!*@*hey* because both could theoretically refer to the same address somenick!someuser@hello.hey.com. iswm doesn't work that way, $ulist does. Neither can be considered wrong, since comparing two wildcards isn't what they are designed to do. The fact that $ulist works (and doesn't return $null for example) is part of mirc's general 'kindness' of accepting non-standard input.

Last edited by qwerty; 10/04/05 03:33 PM.
#116895 10/04/05 04:32 PM
Joined: Feb 2004
Posts: 714
Z
Hoopy frood
OP Offline
Hoopy frood
Z
Joined: Feb 2004
Posts: 714
Ahhhh... I see. I tried specifying a Level too, and that I think did the trick. Thanks! smile


Link Copied to Clipboard