[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Unified name properties
From: |
Keisuke Nishida |
Subject: |
Re: Unified name properties |
Date: |
21 Sep 2000 17:14:56 -0400 |
User-agent: |
T-gnus/6.14.4 (based on Gnus v5.8.6) (revision 02) SEMI/1.13.7 (Awazu) Chao/1.14.0 (Momoyama) Emacs/20.7 (i686-pc-linux-gnu) MULE/4.1 (AOI) |
Dirk Herrmann <address@hidden> writes:
> What is a name of an object anyway? If a name of an object is determined
> by defining that object, we could simply go the other way around and scan
> all top-level environments for bindings to the object and thus avoid the
> need for a name property completely. This would probably be the best
> solution, since it adds no overhead at all, neither memory nor performance
> wise. And, the functions to scan the environments can easily be put into
> a module.
>
> This way, finding the names of an object is somewhat time consuming, but
> for debugging this should be allright (maybe with caching). What this
> wouldn't solve is the problem of objects that have no binding in any
> environment.
Right, right... Probably that is the right way to go. So what about
adding the following procedures?
- Procedure: binding-name OBJ ENV
Find the binding of OBJ in ENV and return its name (associated symbol).
- Procedure: binding-name-list OBJ ENV
Like `binding-name' but return a list of all names.
or
- Procedure: environment-find-name ENV OBJ
Find the binding of OBJ in ENV and return its name (associated symbol).
- Procedure: environment-find-name-list OBJ ENV
Like `environment-find-name' but return a list of all names.
-- Kei
Re: Unified name properties, Marius Vollmer, 2000/09/20
Re: Unified name properties, Marius Vollmer, 2000/09/20