Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • \$\begingroup\$ This answer is invalid, as the user code never gets executed. \$\endgroup\$ Commented Oct 19, 2015 at 20:11
  • \$\begingroup\$ @ppperry: Sure it does: the macro can be written as part of the user code, and it's executed inside of the compiler. \$\endgroup\$ Commented Oct 19, 2015 at 20:13
  • \$\begingroup\$ You would have to define such a macro for a character of set of characters that needs to be typed in every single program or set of programs that makes boo fit the criteria. \$\endgroup\$ Commented Oct 19, 2015 at 20:18
  • \$\begingroup\$ @ppperry: yes, invoking the macro (anywhere in the code) is what causes the compiler to break, fulfilling the criteria. If you're trying to say something deeper than that, you'll have to be a bit more clear, because I don't see what the problem is. \$\endgroup\$ Commented Oct 19, 2015 at 20:24
  • 3
    \$\begingroup\$ @slebetman: And when you have a REPL, or macros where user code is executed at compile time, the distinction between the two gets very blurry. \$\endgroup\$ Commented Oct 20, 2015 at 10:00