Faint Italics=Joe Whitehurst
A macro variable can be thought of as a name pointing at a value.
A named scl list item can be thought of as a name pointing at a value.
So a name can point at a name that can point at a value, etc.
So a named scl list item can be thought of as a named scl list item that can
point at a named scl list item that can point at a named scl list item that
can point at a value which can continue to whatever level of abstraction you
wish without ever using any concatenated ampersands.
Let's look at the problem by analogy. Suppose you go to a party and they
decide to play the pointing game. The question arises how many people
(including Bill) does it take for John to point at Bill. You might think
just John and Bill.
And you would be correct if you understood SAS Component Language
But I haven't told you all rules yet.
And this is the crux of the issue. SAS Component Language dispenses with
these rules as a completely unnecessary restrain on creativity when it comes
to solving problems using the SAS Macro Language.
A man can only point at his wife.
So much for the natural structure of problems. It seems to me that men
point to anyone _but_ their wives.