atom feed17 messages in at.iem.pd-devRe: [PD-dev] Re: [PD] VASP future
FromSent OnAttachments
Krzysztof CzajaMar 24, 2005 7:50 am 
Mathieu BouchardMar 24, 2005 9:20 am 
Frank BarknechtMar 24, 2005 11:03 am 
Krzysztof CzajaMar 24, 2005 1:54 pm 
Mathieu BouchardMar 24, 2005 2:36 pm 
Tim BlechmannMar 25, 2005 1:37 pm 
Krzysztof CzajaMar 25, 2005 2:13 pm 
Tim BlechmannMar 26, 2005 12:31 am 
Mathieu BouchardMar 26, 2005 12:57 am 
Krzysztof CzajaMar 26, 2005 3:40 am 
Frank BarknechtMar 26, 2005 4:03 am 
ix...@replic.netMar 26, 2005 4:20 am 
Krzysztof CzajaMar 26, 2005 1:26 pm 
Tim BlechmannMar 27, 2005 4:52 am 
Tim BlechmannMar 27, 2005 4:57 am 
Mathieu BouchardMar 27, 2005 9:15 pm 
Krzysztof CzajaMar 28, 2005 7:38 am 
Subject:Re: [PD-dev] Re: [PD] VASP future
From:Mathieu Bouchard (mat@sympatico.ca)
Date:Mar 24, 2005 9:20:10 am
List:at.iem.pd-dev

On Thu, 24 Mar 2005, Krzysztof Czaja wrote:

I have missed that one, I am afraid. Is it about keeping $0-symbols in local hash tables, or about introducing a new special syntax? How a local symbol would be prevented from spilling out of local context?

The global symbol-table would deal with: 1. the unique numbering of symbols based on string comparison 2. the holding of global variables (array names / receive-symbols)

A "local" symbol-table would deal with: 1. the holding of "local" variables 2. that's all

The $-prefixes would really become scope indicators. $0-hello would access the local table $0 using the t_symbol "hello". This would *not* create a t_symbol "1000-hello" anymore.

A "local" symbol-table would belong to an abstraction instance (and so, in OOP vocabulary, would rather be called instance symbol-table, or object symbol-table). It would be destroyed whenever the abstraction instance is destroyed.