On Wed, Sep 12, 2007 at 11:59:12AM -0700, [EMAIL PROTECTED] wrote:
> Modified:
>    trunk/DEPRECATED.pod
> 
> +=item B<find_name>
>  
>  There are several variants of some of the above ops; all are deprecated,
>  and are replaced by the ops {set,get}_[hll,root]_global. See also
>  http://www.parrotcode.org/docs/ops/var.html.

I just noticed this -- I understand why find_global and store_global
are being deprecated in favor of the get/set global ops.  But do
we really want to deprecate find_name ?  It seems to have semantics
not directly available through the other ops.

In particular, a PIR instruction like

    'foo'()

uses the find_name opcode to locate the symbol foo in various 
namespaces (lexical, current, global, builtin).  If we eliminate 
the find_name opcode, it seems we'd need something to replace it.

I vote to keep the find_name opcode.

Pm

Reply via email to