|Tim Blechmann||Dec 29, 2004 1:41 pm||.pd, .pd, .pd|
|Krzysztof Czaja||Dec 30, 2004 3:57 am|
|Frank Barknecht||Dec 30, 2004 7:07 am|
|Tim Blechmann||Dec 30, 2004 7:53 am|
|Miller Puckette||Dec 30, 2004 11:02 am|
|Frank Barknecht||Dec 30, 2004 11:14 am|
|Frank Barknecht||Dec 30, 2004 11:35 am|
|Tim Blechmann||Dec 30, 2004 12:43 pm|
|Tim Blechmann||Dec 30, 2004 1:02 pm|
|ix||Dec 30, 2004 2:26 pm|
|Mathieu Bouchard||Dec 31, 2004 10:50 am|
|Mathieu Bouchard||Dec 31, 2004 11:37 am|
|Tim Blechmann||Jan 2, 2005 3:37 am|
|Thomas Grill||Jan 2, 2005 4:02 am|
|Tim Blechmann||Jan 2, 2005 5:14 am||.pd|
|Krzysztof Czaja||Jan 3, 2005 6:28 am|
|Krzysztof Czaja||Jan 3, 2005 6:33 am|
|Frank Barknecht||Jan 3, 2005 6:45 am|
|Subject:||Re: [PD-dev] Re: is namecanvas obsolete or not?|
|From:||Mathieu Bouchard (mat...@sympatico.ca)|
|Date:||Dec 31, 2004 10:50:45 am|
On Thu, 30 Dec 2004, Miller Puckette wrote:
Right, I'm rofgetting, the "pd $0-x" ends up naming the canvas "pd-$0-x" which is hard to generate as a symbol. My problem with "namecanvas" is that one can free or rename the patch (or just free the namecanvas object itself in the patch) and crash Pd. I still haven't found a clean alternative... so for now, I'll have to keep the mis-designed "namecanvas" object around for the forseeable future.
Hey, why not have _local_ variable-tables ? That would be a real cool feature, especially as it would eliminate symbol-table pollution by temporary names when instantiating the same abstraction many many times, especially dynamically. Each patcher would have some kind of variable-table which would be destroyed as the same time as the patcher, just like an object's state is destroyed at the same time as the object, and just like a C function's state is destroyed when that function returns.
The basic idea is to separate the registering of symbols (usually called "gensym" or "intern") from the setting/getting of values of variables. The reason why those two different things were conflated together was to save memory space, since those two tables typically had the same keys.
Historically, many systems have been implementing local variables in terms of a single global symbol-table, but for many reasons, few systems do it like that nowadays. The only remaining such examples I can think of are:
1. PureData 2. MAX 3. EmacsLisp
Most of the other Lisps and Lisp-inspired languages switched to having true local-variables during the 1970's. The only 1990's languages that were designed with an old-skool 1960's Lisp symbol-table are either:
1. Student homework in Compiler Theory courses (but only IF the prof doesn't forbid students from doing it)
2. That visual language called PureData.
_____________________________________________________________________ Mathieu Bouchard -=- Montréal QC Canada -=- http://artengine.ca/matju