Yep, that's right. I posted that example just to point out that macro expansion can result in some unexpected results if you're not careful. Although using macro expansions could cause weird stuff to happen, it doesn't mean that it should be avoided altogether -- just used carefully.

Not relating to macros nor the original post, but ampersands often caused weird stuff to happen -- like popup lists in FPW. Sometimes the ampersand would cause the following character to be displayed as a hot key (as would occur in development environments other than FPW), and sometimes not (as typical in FPW). Adding a backslash before the ampersand solves one problem (now the ampersand appears as part of the prompt), but creates another (sometimes the backslash will appear), depending on the state of the control.