MSIR.0844 Previous undefined macro variable: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
When the first macro statement was encountered in a request, a possible macro variable (something that begins with < | When the first macro statement was encountered in a request, a possible macro variable (something that begins with <b>?!</b>) had already been bypassed. For backward compatibility with existing applications, a <b>?!</b> is assumed '''not''' to be a macro variable if no macro statements are encountered. Encountering a macro statement after such a variable has been bypassed suggests that assumption might have been incorrect. | ||
If, indeed, the <b>?!</b> was simply meant as a literal, it must be changed if macro statements are to be used. If the <b>?!</b> appears in a comment, it can simply be removed. Otherwise, such a literal must be "disguised," perhaps by breaking it up into two strings that are concatenated using the <var>With</var> operator. | |||
[[Category:Sirius Mods messages]] | [[Category:Sirius Mods messages]] | ||
Revision as of 20:15, 23 April 2014
When the first macro statement was encountered in a request, a possible macro variable (something that begins with ?!) had already been bypassed. For backward compatibility with existing applications, a ?! is assumed not to be a macro variable if no macro statements are encountered. Encountering a macro statement after such a variable has been bypassed suggests that assumption might have been incorrect.
If, indeed, the ?! was simply meant as a literal, it must be changed if macro statements are to be used. If the ?! appears in a comment, it can simply be removed. Otherwise, such a literal must be "disguised," perhaps by breaking it up into two strings that are concatenated using the With operator.