From: Julian Leviston Date: 2013-04-12T08:18:46+09:00 Subject: Re: confusion with Struct class That's a very worthy cause! :) Okay, in that case might I suggest for you to build it up yourself with your own self reliance rather than asking questions. Use IRB *a LOT*, and inspect the hell out of your variables and try to understand things really well. Before you do this process you're undertaking, you might want to read up about Ruby metaprogramming and understand it quite thoroughly at a low and deep level, because the level of questions you're asking are quite clearly outstripping your capability (otherwise you wouldn't have so many questions). Perhaps that's just exacerbated by the Struct class, I'm not sure. A better way to do this *might* be to *write* some Ruby Koans for yourself and the community, and in the process, you'll be forced to clearly and cleanly understand why and how things do what they do. I guess you're trying to understand the intent without truly understanding the language at a deep level. The alternative is you could get and consume (thoroughly) the following books which I think are absolutely excellent. The Ruby Programming Language, The Ruby Way and The Well-Grounded Rubyist. The reason I suggested real working code is that you need to engage your feelings in the process otherwise things just won't stick in your memory, and stories are more emotive than examples. Stories have more feeling, and real working code involves a story, whereas an example doesn't. The other thing I'd suggest is to look at the ruby spec. This will give you an unfathomably deep understanding of ruby. IMHO. Julian On 12/04/2013, at 3:12 AM, Love U Ruby wrote: > Julian Leviston wrote in post #1105279: >> An alternative way to learn ruby would be to go and do the ruby koans. >> >> Julian > > Yes,you are right. Thanks for the suggestions. But I am making myself > educated on each class and the methods of that class. Otherwise I have > seen sometimes I write a complex code to get something,but ruby has a > built function to do that. Thus I think it is good to touch all the > methods at-least. So that wright things can be used at wright time. > > -- > Posted via http://www.ruby-forum.com/. >