Originaly posted by Daron,
Yes, you allocate memory space for it, but you are also defining it. If you run my three line question on it, the first line sets the variable to nil. The second line (the first append) crashes. The third line runs okay. I stated why I changed a and b to a list, but I'll clarify: They are integer values, or strings, or longs, or whatever, but they are NOT a list. The value of c is nil. What else is it? It works in an append situation without being called as a list, even though there is nothing to append to. So, I ask again, when you define a variable as nil, what is the object (container) of c? What does c become? Not nothing. Not destroyed. Not a flash in the pan.
***********************************************************
Wouldn't c always = nil... not empty, not a flash in the pan, not destroyed