Even if custom operators were possible they would still need a prefix to distinguish them from ordinary text, otherwise you could end up with horrible problems like:
if (hello moo [color:red]newoperator %blah) ...[/color]
becoming
if (hello [color:red]moo newoperator %blah) ...[/color]
if a new script introduced a
moo operator.
So with that in mind, is:
$iif($nick [color:red]$~isowner $chan)[/color]
(assuming
$~ as the operator prefix) really much cleaner than
$iif($isowner($nick, $chan))There are some uses to having custom operators, I just don't think saving a couple of commas is one of them.
Note 1: As RusselB mentioned, mIRC already has an undocumented operator
isowner which works as expected on most networks that support it.
Note 2: If you call an alias in an event then all special identifiers (such as
$nick and
$chan) will be available to the alias too. So if you're really worried about commas you could write a custom identifier like this:
alias isowner {
var %chan = $iif($2,$2,$chan), %nick = $iif($1,$1,$nick)
return $iif($nick(%chan, %nick).pnick == ~, $true, $false)
}and call it as:
inside events.
Other words, i LOVE mIRC, and as sOON as I can muster up $20 ill buy it.