From: Gavri Fernandez Date: 2005-02-17T00:56:33+09:00 Subject: Re: Printing why's (poignant) guide to ruby On Wed, 16 Feb 2005 02:13:50 +0900, Mark Hubbart wrote: > No, you don't go paradigm-swapping on them. When it gets to a point > where it makes a difference, let them know that "puts" is the short > form of "STDOUT.puts". Tell them that STDOUT is an object that is > created for you, which can recieve messages that, among other things, > help you write to the screen. Have them write a little code using > STDOUT. Then tell them that the short form is easier, and more > commonly used. But why is this better than just starting with STDOUT.puts and later after object-oriented concepts have been completely understood introduce puts why do you want to go this way? puts -> STDOUT.puts -> puts I really think doing it with hard-core object-orientation in the beginning will help a lot. It's so natural. > > Of course, all of this I say assuming that the goal is to create an > > object-oriented programmer, not a procedural one. > > I suspect the goal is to create a Ruby programmer :) Which means that > there will be some amount of overlapping. Wasn't the goal just to create a programmer out of a non-programmer? That was what this thread was about, right? Read all that i said above with this assumption and you might agree with me :) -- Gavri --------------------------------------------------- I blog here: http://gavri.blogspot.com