You should consider spreading your code out to multiple
lines. Your current code uses pipes | to separate multiple
commands on one line. That can make code very difficult to
read/alter/debug. Example of difficulty using | pipes:
alias example {
set %ex this is a very long line that goes beyond the edge of the mIRC editor screen. this line could be any code, and this string is just an example. when the text goes beyond the edge of the editor, you have to scroll back and forth to be able to read all the code, and you have to notice all the pipes so that you know where the commands are separated. | unset %ex
msg $me %ex
}
When you look at that code quickly, you would see that a
variable is getting set to some value, and then below it,
the variable is being messaged to yourself. What you may
not notice is that at the end of the variable, there is a
pipe and the variable is unset. This unnoticed code would
cause you all sorts of problems. The /msg command would
give an error because it doesn't have anything to send
(%ex has been unset).
mIRC allows you to put multiple commands on multiple lines if you contain them in { } brackets. Using the same example, but on multiple lines:
alias example {
set %ex this is a very long line that goes beyond the edge of the mIRC editor screen. this line could be any code, and this string is just an example. when the text goes beyond the edge of the editor, you have to scroll back and forth to be able to read all the code, and you have to notice all the pipes so that you know where the commands are separated.
unset %ex
msg $me %ex
}
It becomes incredibly easy to see what the problem is.
Anyway, this is not a rule, it is just a suggestion.
Personally, I hate trying to debug (someone else's) code
when it uses | pipes, and you are more likely to get
(quick) help on this forum if you use pipes as little as
possible.
-genius_at_work
