>> // 'bar' is some type> #define foo bar>> // as part of definition...> ...foo/bar>

No space should be included...

> var/list/test_list>

You're not following - 'baz' was intentional in the last example, as a stand-in for the variable name. Your 'fix' is the equivalent of this:

var/list/list

which is clearly wrong.

I'm aware no space should be included. My point is that when a macro is expanded a space appears to be appended in the preprocessed code, causing these issues. My guess is this is because Dream Maker has likely repurposed a C++ preprocessor, and C/C++ are distinctly friendlier to having random whitespace in statements than DM is.

My example with the space in it is there because it triggers similar error messages to the case with the macro.

If you don't know what we're talking about, read the reference page on the #define directive.