Re: Variables, Aliasing, and Undefined-ness

2005-12-15 Thread Matt Diephouse
Leopold Toetsch <[EMAIL PROTECTED]> wrote: > Matt Diephouse wrote: > > > $alias = undef > > > > translates to > > > > null $P1 > > $P2 = getinterp > > $P2 = $P2["lexpad"; 1] > > $P2['$alias'] = $P1 > > Given that you are using DynLexPad, you just do: > >delete $P2['alias'] If only it

Re: Variables, Aliasing, and Undefined-ness

2005-12-15 Thread Roger Browne
Matt Diephouse wrote: > So what am I supposed to do? It appears that using `null` to mark > deleted/undefined variables won't work. But it's not clear to me that > using a Null PMC is a good idea... Here's one possibility: you can use one of the PObj_private PMC flags to store the defined/undefin

Re: Variables, Aliasing, and Undefined-ness

2005-12-15 Thread Leopold Toetsch
Matt Diephouse wrote: $alias = undef translates to null $P1 $P2 = getinterp $P2 = $P2["lexpad"; 1] $P2['$alias'] = $P1 Given that you are using DynLexPad, you just do: delete $P2['alias'] HTH leo

Variables, Aliasing, and Undefined-ness

2005-12-15 Thread Matt Diephouse
While working out some bugs in ParTcl I came across something roughly equivalent to the following Perl code (I'm using Perl because I believe more people know Perl than Tcl, at least on this list): #!/usr/bin/perl $var = "Foo"; *alias = *var; $alias = undef; $alias = "Baz"; print $va