Melvin Smith <[EMAIL PROTECTED]> wrote:
> Another option is to use quotes for symbols with sigils,
And we have to cope with unicode finally. So I'd vote for that
alternative. *But* as code normally comes out of a compiler and there
may be many different compilers, we can't deal with arbitrary symbols,
because, we don't know the scoping rules of these compilers.
We can only deal with mangled symbol names.
my $i;
{ my $i ; }
> (And remember namespaces when considering solutions)
Yes. We need IMHO something like:
- .lexical <type> name
- .lexcial <type> name, '$unmangled_orig_name'
- .global ...
where C<name> is a mangled symbol name like now or even C<$P\d+>. We
have to know, if the symbol is a temporary or not for spilling. Lexical
and globals have their store in the lex pad or in the stash, so for
spilling we don't have to store these variables, we only need to
refetch, where we now fetch from the spill array.
The .lexical and .global directives should use the appropriate lexical
or global opcodes to deal with these symbols.
The unmangled name is just for diagnostics and will be stored in a
different packfile segment.
> -Melvin
leo
