In a message dated 6/12/99 2:27:19 AM, [EMAIL PROTECTED] writes:
>> A container is an area to put data. It can be a variable, property, global,
>
>> or chunk thereof.
>
>That's the traditional xTalk definition, but if that's what you're
>supporting, why add the term to the language?
> Regards,
> Scott
>
Because it proved impossible to simply let the user stick a container into a
variable. There were too many syntax issues. So now they declare a parameter
or a variable 'container' before storing containers in it. Otherwise it's a
plain vanilla xtalk variable.
set var to the title of me -- means something
container var
set var to the title of me -- means something different
Dan
