Macro with two names

RayLivingston:
Which defines NAME1 to an empty string, THEN defines VALUE to "NAME2". Order of the #defines is important. Unlike c variable assignments, changing the definition of VALUE does NOT update any previous #defines that referenced it.

Well, I was just translating PaulS's words to code...maybe my comprehension is bad or PaulS's words are wrong, or both.

RayLivingston:
One could also reasonably ask why on earth anyone would WANT to create two #defines for the same value, other than as an entry to an obfuscated code contest...

It was just a question that I didn't know what to Google about.