A frequent question from Ruby newcomers is "Okay, I've read the
tutorials - now what?". To that end, I'm putting together a series of
tutorials, each of which leads the student step by step through the
construction of a complete ruby program. There are no answers and no
explanations provided - rather, each question is followed by a hint
containing relevant topics to be looked up in the Pickaxe, on Google,
etc.
The entry-level program is an arithmetic tutor; the reader is assumed
to have worked their way through Chris Pine's tutorial, and have a
copy of the docs handy. (Later programs will assume that the reader
has done the previous ones). Here's the first, tentative draft -
comments and suggestions welcomed.
Good work, but may i point out that 'if' is no method?
^ manveru
···
On Sat, Feb 23, 2008 at 6:44 PM, Martin DeMello <martindemello@gmail.com> wrote:
A frequent question from Ruby newcomers is "Okay, I've read the
tutorials - now what?". To that end, I'm putting together a series of
tutorials, each of which leads the student step by step through the
construction of a complete ruby program. There are no answers and no
explanations provided - rather, each question is followed by a hint
containing relevant topics to be looked up in the Pickaxe, on Google,
etc.
The entry-level program is an arithmetic tutor; the reader is assumed
to have worked their way through Chris Pine's tutorial, and have a
copy of the docs handy. (Later programs will assume that the reader
has done the previous ones). Here's the first, tentative draft -
comments and suggestions welcomed.
Nice work Martin, I suggest however that you do a
gsub("function","method") on your text, there are just no functions in
Ruby.
What do you think?
Cheers
Robert
···
On Sat, Feb 23, 2008 at 10:44 AM, Martin DeMello <martindemello@gmail.com> wrote:
A frequent question from Ruby newcomers is "Okay, I've read the
tutorials - now what?". To that end, I'm putting together a series of
tutorials, each of which leads the student step by step through the
construction of a complete ruby program. There are no answers and no
explanations provided - rather, each question is followed by a hint
containing relevant topics to be looked up in the Pickaxe, on Google,
etc.
The entry-level program is an arithmetic tutor; the reader is assumed
to have worked their way through Chris Pine's tutorial, and have a
copy of the docs handy. (Later programs will assume that the reader
has done the previous ones). Here's the first, tentative draft -
comments and suggestions welcomed.
Thanks for putting in the time and effort for that Martin.
I am very much a new to Ruby and found that Chris uses version 1.8.2
version of Ruby which has given me a few problems as the instructions
in Chris`s book don`t correspond to the latest (186.25?) version I
have and it seems 1.8.2 is not now available. Guys on the forum have
been very helpful with their suggestions but I was a bit concerned at
failing at the very first prog I started ;-(.
I shall persevere. I`ll have to do now I`ve just enrolled on the
online Ruby course run by Satish.
Cheers
Steve
Yeah, right now I'm using # as a placeholder for a css class that will
cover both methods and keywords - basically, things to look up
directly in the documentation/pickaxe index, rather than more general
concepts to google for.
martin
···
On Sat, Feb 23, 2008 at 1:56 AM, Michael Fellinger <m.fellinger@gmail.com> wrote:
I did think about that, and deliberately decided to go with
'function', since from a newbie perspective toplevel methods *are*
functions.
Pros: Clear, conceptually simple to understand, a useful and
for-the-moment accurate model of what's happening
Cons: Technically incorrect, but to explain the difference would delve
into ruby's object model a bit too soon.
martin
···
On Sat, Feb 23, 2008 at 3:44 AM, Robert Dober <robert.dober@gmail.com> wrote:
Nice work Martin, I suggest however that you do a
gsub("function","method") on your text, there are just no functions in
Ruby.
What do you think?
A frequent question from Ruby newcomers is "Okay, I've read the
tutorials - now what?". To that end, I'm putting together a series of
tutorials, each of which leads the student step by step through the
construction of a complete ruby program. There are no answers and no
explanations provided - rather, each question is followed by a hint
containing relevant topics to be looked up in the Pickaxe, on Google,
etc.
The entry-level program is an arithmetic tutor; the reader is assumed
to have worked their way through Chris Pine's tutorial, and have a
copy of the docs handy. (Later programs will assume that the reader
has done the previous ones). Here's the first, tentative draft -
comments and suggestions welcomed.
Nice work Martin, I suggest however that you do a
gsub("function","method") on your text, there are just no functions in
Ruby.
What do you think?
Cheers
Robert
Ok I see, I thought it was more an oversight, sorry for wasting your time
R.
···
On Sat, Feb 23, 2008 at 9:59 PM, Martin DeMello <martindemello@gmail.com> wrote:
On Sat, Feb 23, 2008 at 3:44 AM, Robert Dober <robert.dober@gmail.com> wrote:
>
> Nice work Martin, I suggest however that you do a
> gsub("function","method") on your text, there are just no functions in
> Ruby.
> What do you think?
I did think about that, and deliberately decided to go with
'function', since from a newbie perspective toplevel methods *are*
functions.
Pros: Clear, conceptually simple to understand, a useful and
for-the-moment accurate model of what's happening
Cons: Technically incorrect, but to explain the difference would delve
into ruby's object model a bit too soon.
Worse there is even module_function, I hate it. But I think that the
community uses method almost exclusively.
Strange that I never complained about #module_function, it made it
even into 1.9 brrrr.
Cheers
Robert
···
On Sat, Feb 23, 2008 at 10:24 PM, Joel VanderWerf <vjoel@path.berkeley.edu> wrote:
Robert Dober wrote:
> On Sat, Feb 23, 2008 at 10:44 AM, Martin DeMello > > <martindemello@gmail.com> wrote:
>> A frequent question from Ruby newcomers is "Okay, I've read the
>> tutorials - now what?". To that end, I'm putting together a series of
>> tutorials, each of which leads the student step by step through the
>> construction of a complete ruby program. There are no answers and no
>> explanations provided - rather, each question is followed by a hint
>> containing relevant topics to be looked up in the Pickaxe, on Google,
>> etc.
>>
>> The entry-level program is an arithmetic tutor; the reader is assumed
>> to have worked their way through Chris Pine's tutorial, and have a
>> copy of the docs handy. (Later programs will assume that the reader
>> has done the previous ones). Here's the first, tentative draft -
>> comments and suggestions welcomed.
>>
>> http://zem.novylen.net/ruby/tutorial/arithmetic-quiz/arith.html
>>
>> martin
>>
>>
>
> Nice work Martin, I suggest however that you do a
> gsub("function","method") on your text, there are just no functions in
> Ruby.
> What do you think?
> Cheers
> Robert
>
There's a middle road: Mention briefly that they're called "methods",
even if they fill the same role as "functions" in many other languages,
and leave it at that.
···
On Sun, Feb 24, 2008 at 05:59:46AM +0900, Martin DeMello wrote:
On Sat, Feb 23, 2008 at 3:44 AM, Robert Dober <robert.dober@gmail.com> wrote:
>
> Nice work Martin, I suggest however that you do a
> gsub("function","method") on your text, there are just no functions in
> Ruby.
> What do you think?
I did think about that, and deliberately decided to go with
'function', since from a newbie perspective toplevel methods *are*
functions.
Pros: Clear, conceptually simple to understand, a useful and
for-the-moment accurate model of what's happening
Cons: Technically incorrect, but to explain the difference would delve
into ruby's object model a bit too soon.
--
CCD CopyWrite Chad Perrin [ http://ccd.apotheon.org ]
W. Somerset Maugham: "The ability to quote is a serviceable substitute for
wit."
On Tue, Feb 26, 2008 at 9:38 PM, Chad Perrin <perrin@apotheon.com> wrote:
There's a middle road: Mention briefly that they're called "methods",
even if they fill the same role as "functions" in many other languages,
and leave it at that.
