>Just thought of something else. This is a good thing that this is a literal substitution because what if #DEFINE CRLF CHR(10) + CHR(13) was actually an EVAL() type replacement at compile time? That would be a real mess!

My personal take is (and has been) to assign things like this to a variable (especially if there's an iteration structure involved) and go from there. Otherwise, each time the constant is referenced, the functions are evaluated. By assigning a variable, the functions are called only once.