Ken Farmer wrote: > > Wiggins d'Anconia <[EMAIL PROTECTED]> wrote: > > See the other posters responses as well, but I think it might help if > you read through some docs on OOP programming, check out: > > perldoc perlboot > perldoc perltoot > perldoc perltooc > > And issuing, > > perldoc perl > > Thanks for the response, and the other responders as well. Believe me, I > have not only read the above many times, but killed several trees and printed > them out so I could refer to them. > > I agree that I need a perl object book. I am using standard perl books, all > of which have a chapter on poop but obviously don't go into detail. In fact, > part of the problem is the stuff that is left out is different in each book > so some of the info "appears" to contradict the others. Plus, a non-perl > object book will really lead a newbie out of the promised land - fast. > > I have ordered both of the available books on perl objects and am > impatiently waiting for the delivery. > > The problem, I think, is that I have done procedural - based programming > (as a hobby) for decades and in learning OOP I just haven't managed to make > that mental shift yet. I had the same problem back in the '90's when I got > my first event-based suite (VB or the like) and it bothered me for weeks that > I didn't know what my program was "doing" when it wasn't executing my code. > Suddenly it clicked and off I went. Same thing should happen with oop, > eventually. > > CptKrf >
Yep and good luck. Stick to it, it will click and once it does should open another world to you. Like many types of programming at first you are going to write some pretty crappy code, and it is going to use a small subset of the features of OOP, but start there and then build. You won't be writing 100% elegant applications overnight, but you should see good results fairly quickly. http://danconia.org -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
