Re: Re: odd things with my and our

Getting at the lexical pad is possible, but very difficult.

How? This looks like it could be interesting! Mind sharing? (That isn't sarcasm. I do really want to know).

Code is (almost) always untested.
http://www.justicepoetic.net/

Comment on Re: Re: odd things with my and our

Replies are listed 'Best First'.
Re^3: odd things with my and our by hardburn (Abbot) on Jan 25, 2004 at 14:12 UTC
You can always trawl through `/dev/kmem` . . . PadWalker gives limited access to the pads. I remember there being a way to get at any pads, but I don't remember how exactly (this isn't something I do every day . . . ). It was in reference to a node on how to break lexically-declared variables for private object data. The process was so difficult that the equivilent ammount of work in any other OO language could also break object privacy. Sorry, that's all I remember. ---- I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident. -- Schemer `: () { :\|:& };:` Note: All code is untested, unless otherwise stated	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^3: odd things with my and our
by hardburn (Abbot) on Jan 25, 2004 at 14:12 UTC

You can always trawl through /dev/kmem . . .

PadWalker gives limited access to the pads.

I remember there being a way to get at any pads, but I don't remember how exactly (this isn't something I do every day . . . ). It was in reference to a node on how to break lexically-declared variables for private object data. The process was so difficult that the equivilent ammount of work in any other OO language could also break object privacy. Sorry, that's all I remember.

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

: () { :|:& };:

Note: All code is untested, unless otherwise stated

[reply]
[d/l]
[select]