Re^5: Dumping variables but DRY and simple

Sorry IMHO that's wrong, I can get the realname for my and our declarations with the help of PadWalker which is core!

I think PadWalker *does* interfere with the compiler (otherwise I don't see how it could get the names of the lexicals). Since when is it in Core? I can't see it in Perl 5.10.0 (in the ActiveState distribution).

--
Ronald Fischer <ynnor@mm.st>

Comment on Re^5: Dumping variables but DRY and simple Download Code

Replies are listed 'Best First'.
Re^6: Dumping variables but DRY and simple by ikegami (Patriarch) on Mar 27, 2010 at 17:00 UTC
I haven't looked at the code recently, but I don't think so. The name of a lexical IS available. `>perl -MO=Concise,-exec -e"my $x; print $x" 1 <0> enter 2 <;> nextstate(main 1 -e:1) v:{ 3 <0> padsv[$x:1,2] vM/LVINTRO <---- 4 <;> nextstate(main 2 -e:1) v:{ 5 <0> pushmark s 6 <0> padsv[$x:1,2] l <---- 7 <@> print vK 8 <@> leave[1 ref] vKP/REFC -e syntax OK` [download] And yes, PadWalker is not distributed with Perl.	[reply] [d/l]
Re^6: Dumping variables but DRY and simple by LanX (Saint) on Mar 27, 2010 at 16:19 UTC
> Since when is it in Core? very strange I never saw an installation without PadWalker but it's indeed not listed. UPDATE: `corelist -a PadWalker<P> PadWalker was not in CORE (or so I think)` [download] urgh ... well ... hard to understand ... anyway I always need to install it when debugging and it's all about debugging. Cheers Rolf	[reply] [d/l]
Re^7: Dumping variables but DRY and simple by Anonymous Monk on Mar 27, 2010 at 16:33 UTC
LanX just what are you doing that you rely so much on PadWalker?	[reply]
Re^8: Dumping variables but DRY and simple by LanX (Saint) on Mar 27, 2010 at 18:53 UTC
I'm glad that you finally found a way to log in... xD Cheers Rolf	[reply]
Re^9: Dumping variables but DRY and simple by Anonymous Monk on Mar 27, 2010 at 21:17 UTC