yield

[Corey Konrad]

this works fine:

def printer()
yield "ball"
end

printer {|word_one| puts word_one}


but this does not:

def printer(arg)
yield arg
end

printer("ball")
printer {|word| puts word}

why is that, cant yield be used with arguments?

thanks

 

[Brian Candler]

this works fine:

def printer()
yield "ball"
end

printer {|word_one| puts word_one}


but this does not:

def printer(arg)
yield arg
end

printer("ball")
printer {|word| puts word}

why is that, cant yield be used with arguments?

It can. Your second function 'printer' takes one argument plus one block.
However in the first case you were calling it without a block, and in the
second case you were calling it without an argument.

What you need is:

printer("ball") {|word| puts word}

 

[Matthew Moss]

why is that, cant yield be used with arguments?

It can, but you need to use it correctly:

def printer(arg)
yield arg
end
Good.


printer("ball")
printer {|word| puts word}

Not so good. Try:

printer("ball") { |word| puts word }

 

[Corey Konrad]

It can. Your second function 'printer' takes one argument plus one
block.
However in the first case you were calling it without a block, and in
the
second case you were calling it without an argument.

What you need is:

printer("ball") {|word| puts word}

oh ok, my understanding for some reason was that the method was going to
remmeber that i set arg to "ball" so that when i used printer with the
block that "ball" would still be in arg. So is that why it isnt working,
is because when i call the printer method the second time the value
stored in arg is destroyed?

 

[Chad Perrin]

oh ok, my understanding for some reason was that the method was going to
remmeber that i set arg to "ball" so that when i used printer with the
block that "ball" would still be in arg. So is that why it isnt working,
is because when i call the printer method the second time the value
stored in arg is destroyed?

I'm just guessing here, but . . .

It looks like you're expecting something akin to class behavior from a
method. Perhaps what you want to do is something more like this:

class Printer
def initialize(arg)
@arg = arg
end

def iterator_thingie
yield @arg
end
end

printer = Printer.new("ball")
printer.iterator_thingie {|word| puts word}


Then again, maybe that's not the kind of behavior you want.

 

[Corey Konrad]

I'm just guessing here, but . . .

It looks like you're expecting something akin to class behavior from a
method. Perhaps what you want to do is something more like this:

class Printer
def initialize(arg)
@arg = arg
end

def iterator_thingie
yield @arg
end
end

printer = Printer.new("ball")
printer.iterator_thingie {|word| puts word}


Then again, maybe that's not the kind of behavior you want.

its not that i am looking to get any specific result its that i am
trying to understand what is going on behind the scenes so that i can
understand why what i did, did not work not just that it in fact did not
work.

 

[Corey Konrad]

I'm just guessing here, but . . .

It looks like you're expecting something akin to class behavior from a
method. Perhaps what you want to do is something more like this:

class Printer
def initialize(arg)
@arg = arg
end

def iterator_thingie
yield @arg
end
end

printer = Printer.new("ball")
printer.iterator_thingie {|word| puts word}


Then again, maybe that's not the kind of behavior you want.

what i am basically trying to understand is:

When i do printer("ball") i am putting the string ball in the arg
variable of the printer method.

When i call the printer method with the block afterwards what happened
to my string i stored in arg? Was it destroyed or when i called the
printer method for the second time did ruby create a whole new arg
variable with nothing in it and thats why the way i did it didnt work?
Do you know what i mean i am trying to understand why what i did didnt
work.

 

[Gary Wright]

what i am basically trying to understand is:

When i do printer("ball") i am putting the string ball in the arg
variable of the printer method.

Forget the block for a moment. Your question pertains to method
arguments with or without an associated block.

Next, don't think of a variable as a container ("putting the
string 'ball' in the arg). Variables are not containers in Ruby
they are names. Think of sticking a post-it note on 'ball' and
written on the post-it note is 'arg'.

The post-it note gets created and stuck on 'ball' when you
call the method. The post-it note gets removed from 'ball'
when the method returns. Within the method the identifier
'arg' can be used to identify the string (in this case 'ball').
Outside the method 'arg' is meaningless since the post-it note
labeled 'arg' has been discarded.

When you call a method a second (or third or fourth...) time,
a new post-it note is created and stuck on the object and
'arg' is once again written on the post-it note and can be
used to identify the object you provided.

printer('ball') # within printer, arg refers to 'ball'
# no post-it note 'arg' between calls to printer
printer('baseball') # within printer, arg refers to 'baseball'
# no post-it note 'arg' between calls to printer
printer('football') # within printer, arg refers to 'football'




Gary Wright

 

[Chad Perrin]

what i am basically trying to understand is:

When i do printer("ball") i am putting the string ball in the arg
variable of the printer method.

When i call the printer method with the block afterwards what happened
to my string i stored in arg? Was it destroyed or when i called the
printer method for the second time did ruby create a whole new arg
variable with nothing in it and thats why the way i did it didnt work?
Do you know what i mean i am trying to understand why what i did didnt
work.

Methods are not persistent things -- they are actions taken by objects.
When you call a method that you define outside of any class, it's
actually a method of the Self object (basically, a method of your
program). Because actions do not maintain state (data, variables, what
have you), variables within methods go away when the methods are not in
use. A method is an ephemeral, fleeting thing. It's an occurrence, in
a way, rather than a thing.

A method, in fact, is much like a function in that respect (if you're
familiar with functions from other languages). You put something in,
you get something out.

Blocks can be used to maintain state, but to do so you need to assign
them as objects to some kind of name/variable/thing that is outside of a
method. That, of course, is because a block returned from a method and
stuck in a variable is basically the same as a closure in any other
language (that supports closures).

Hopefully that helps clear things up for you, and give you a glimpse of
other, sorta related topics in the language.

 

[David A. Black]

Hi --

oh ok, my understanding for some reason was that the method was going to
remmeber that i set arg to "ball" so that when i used printer with the
block that "ball" would still be in arg. So is that why it isnt working,
is because when i call the printer method the second time the value
stored in arg is destroyed?

The two calls to printer are unrelated to each other. Each of them
uses a local variable 'arg', but they're two different variables.

The code block is, syntactically, part of the method call. So if
there's no block for a given method call, that's that.


David

--
Q. What is THE Ruby book for Rails developers?
A. RUBY FOR RAILS by David A. Black (http://www.manning.com/black)
(See what readers are saying! http://www.rubypal.com/r4rrevs.pdf)
Q. Where can I get Ruby/Rails on-site training, consulting, coaching?
A. Ruby Power and Light, LLC (http://www.rubypal.com)

 

[Bertram Scharpf]

Am Samstag, 17. M=E4r 2007, 07:10:26 +0900 schrieb Corey Konrad:

def printer(arg)
yield arg
end
=20
printer("ball")
printer {|word| puts word}

How did you get this working? Both `printer' calls will
fail. Please run your code before you post it or at least
include the error message.

Please don't mind,

Bertram


--=20
Bertram Scharpf
Stuttgart, Deutschland/Germany
http://www.bertram-scharpf.de

 

[John Joyce]

Bertram, some code is not supposed to work.
It is hypothetical, or it is a snippet or the whole thing.
This thread is about structural and conceptual examples of "code =20
blocks" in Ruby, not actual working code.

though, some working code might make it more clear for some people, =20
it is in the pickaxe book