From WikiChip
Editing mirc/evaluation brackets
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
This page supports semantic in-text annotations (e.g. "[[Is specified as::World Heritage Site]]") to build structured and queryable content provided by Semantic MediaWiki. For a comprehensive description on how to use annotations or the #ask parser function, please have a look at the getting started, in-text annotation, or inline queries help pages.
Latest revision | Your text | ||
Line 158: | Line 158: | ||
=== Multiple evaluations === | === Multiple evaluations === | ||
− | If we follow the simple rule above, we can easily evaluate a specific code segment multiple | + | If we follow the simple rule above, we can easily evaluate a specific code segment multiple files. Consider the following example: |
<source lang="mIRC">alias exe echo -a I was called! | return Hi! | <source lang="mIRC">alias exe echo -a I was called! | return Hi! | ||
; example: | ; example: | ||
− | alias example echo -a [ [ [ $!!exe ] ] ]</source> | + | alias example echo -a [ [ [ [ [ $!!!!exe ] ] ] ] ]</source> |
The above code prints: | The above code prints: | ||
Line 168: | Line 168: | ||
I was called! | I was called! | ||
Hi! | Hi! | ||
− | |||
− | |||
[[File:Eval6.png]] | [[File:Eval6.png]] | ||
− | |||
Here is a more interesting example of multiple evaluations: | Here is a more interesting example of multiple evaluations: | ||
Line 210: | Line 207: | ||
The rule about [ A $+ B ] is: | The rule about [ A $+ B ] is: | ||
− | The '''[ token_A $+ token_B ]''' arrangement will cause token_A to evaluate once and then be concatenated to token_B (evaluated zero times) | + | The '''[ token_A $+ token_B ]''' arrangement will cause token_A to evaluate once and then be concatenated to token_B (evaluated zero times). I.e.: |
[ A $+ B ] <=> $($(A, 1) $+ $(B, 0), 2) | [ A $+ B ] <=> $($(A, 1) $+ $(B, 0), 2) | ||
Line 282: | Line 279: | ||
The most common form is %var. [ $+ [ $nick ] ] which allow you to retrieve a value from a variable specifically created for $nick. | The most common form is %var. [ $+ [ $nick ] ] which allow you to retrieve a value from a variable specifically created for $nick. | ||
+ | == Escaping Evaluation Brackets == | ||
+ | Evaluation brackets can be escaped by using double brackets ([[) without spaces. For example: | ||
− | = | + | <source lang="mIRC">//echo -a [[ [[ example! ]] ]] </source> |
− | |||
− | + | The code above prints: | |
+ | [ [ example! ] ] | ||
− | + | Note that without a complete pair, a single bracket is not treated as anything special. The following example is also acceptable: | |
− | + | <source lang="mIRC">//echo -a [[ [[ example! ] ]</source> | |
− | + | It's a good time to also note that escaped evaluation brackets are not exactly the same as using $chr(91) and $chr(93). The escaped evaluation brackets happen at the same phase of evaluation as the actual evaluation bracket processing. Consider the following example: | |
− | //echo -a | + | <source lang="mIRC">//echo -a $mid( [[ [[ example! ]] ]] , 1) => $mid( $chr(91) example! $chr(93) , 1)</source> |
− | + | The code above prints: | |
+ | example! => [ example! ] | ||
− | + | == Special behavior inside identifiers == | |
+ | By now you know evaluation brackets happen before the code itself evaluates. It turns out that when an identifier evaluates, it will correctly parse code that is a direct result of the evaluation brackets. Here is some code to demonstrate this behavior: | ||
<source lang="mIRC">//var -s %x = mid(@Example!,2,8, %y = ) | echo -a $ [ $+ [ %x $+ [ %y ] ] ]</source> | <source lang="mIRC">//var -s %x = mid(@Example!,2,8, %y = ) | echo -a $ [ $+ [ %x $+ [ %y ] ] ]</source> | ||
Line 315: | Line 316: | ||
The interpreter is able to handle the commas and braces as part of the code. | The interpreter is able to handle the commas and braces as part of the code. | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Additional Odd Behaviors == | == Additional Odd Behaviors == | ||
Line 387: | Line 337: | ||
The above code prints: | The above code prints: | ||
$!me$me vs. $me$!me | $!me$me vs. $me$!me | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Commands with Special Behavior == | == Commands with Special Behavior == | ||
Line 416: | Line 360: | ||
: | : | ||
− | Note that unlike the reset of the commands, '''{{mIRC|/unset}}''' cannot set variables in the format of %var {{mIRC|$+}} %var. Evaluation brackets are needed to fix this. | + | Note that unlike the reset of the commands, '''{{mIRC|/unset}}''' cannot set variables in the format of %var {{mIRC|$+}} %var. Evaluation brackets are needed to fix this. This is most likely a bug. |
− | |||
− | |||
− | |||
− | |||
− | |||
[[Category:mIRC|evaluation brackets]] | [[Category:mIRC|evaluation brackets]] |