Easy way to use "self" in Proc

[Leon Bogaert]

Hi all,

I have this piece of code: http://pastie.caboo.se/198524
I'm trying to use the "self" context of the instanciated class in the
Proc. I've got it working now, but isn't there a nicer way to use the
Proc.new() without having to use the "|obj|" part?

So instead of:

t.code = Proc.new { |obj| obj.instance_test() }

I want to use something like:
t.code = Proc.new { self.instance_test() }

I've tried some stuff but I can't / don't think I can get it working the
second way. Does anyone have some bright ideas about solving this
problem?

Thanks in advance!
Leon

 

[Daniel Finnie]

[Note: parts of this message were removed to make it a legal post.]

Hi,

It is possible. You need to tell the object to evaluate the proc with self
as that object like so:the proc as a block.
=> 11

[1, 2, 3].instance_eval &t

=> 3

Because self is an implicit receiver (that is, if no other reciever is
specified, self is the receiver), you can leave off self entirely:

t = Proc.new { length }

[1, 2, 3].instance_eval &t => 3
"Furry bunny".instance_eval &t

=> 11

Dan

 

[Joel VanderWerf]

Hi all,

I have this piece of code: http://pastie.caboo.se/198524
I'm trying to use the "self" context of the instanciated class in the
Proc. I've got it working now, but isn't there a nicer way to use the
Proc.new() without having to use the "|obj|" part?

So instead of:

t.code = Proc.new { |obj| obj.instance_test() }

I want to use something like:
t.code = Proc.new { self.instance_test() }

I've tried some stuff but I can't / don't think I can get it working the
second way. Does anyone have some bright ideas about solving this
problem?

Fortunately, it's easy:

t.code = Proc.new { self.instance_test() }

and instead of

t.code.call(obj)

you just do this

obj.instance_eval(&t.code)

 

[Leon Bogaert]

Wow, dudes! Thanks!

That's simple... I'll read your posts some more times to really
understand what's hapening
'Cause this is like magic to me.

After googling on the solution I also found this blog:
http://www.bofh.org.uk/articles/2007/08/16/a-cunning-evil-trick-with-ruby

 

[Leon Bogaert]

I thought I understood the block/proc thing. Guess not...

I thought when I proc is converted to a block, the code gets evaluated.
So (I thought) when Proc.call() is, euhm, called, the proc gets
converted to a block and is getting evaluated in that context.

 

[Joel VanderWerf]

I thought I understood the block/proc thing. Guess not...

I thought when I proc is converted to a block, the code gets evaluated.
So (I thought) when Proc.call() is, euhm, called, the proc gets
converted to a block and is getting evaluated in that context.

The block keeps the original context ("lexical scoping"), including
local vars, self, and constants:

class C
class D; end
def foo
local = 1
proc { [local, self, D] }
end
end

class D; end
local = 2
p [local, self, D]

p C.new.foo.call