Re: [stack] What does "concatenative" actually mean?

On Mar 7, 2009, at 3:51 AM, spir wrote:

> I find this a pity. One should be able to recall definitions.

Why? It would be a useless duplication of the functionality provided  
by quotation.

> [Side note: The point is similar for me to variables in applicative  
> languages. Many allow or require first declaration/definition/ 
> initialization of a new name. In other languages (eg python), there  
> is no way in
> 	n = 1
> to know whether:
> * the programmer's *intention* is to introduce a new name:value pair  
> or rebind an existing name to a new value
> * the interpreter will create a new entry in the local namespace's  
> dict, and give it an initial value, or update the value of an  
> existing key:value pair.]

Aye. This is why you should not use the same syntax for introducing a  
new variable and updating a variable. I'm not quite sure though what  
Python's design misfeatures have to do with quotation.

- John