Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

chaoticset (2105)

  (email not shown publicly)
AOL IM: chaoticset23 (Add Buddy, Send Message)
Yahoo! ID: illuminatus_foil (Add User, Send Message)

JAPH. (That's right -- I'm not Really Inexperienced any more.)

I'm not just here, I'm here [], and here [] too, I ramble randomly in my philosophical blog [] and my other blog []. Soon I'll come in a convenient six-pack.

Journal of chaoticset (2105)

Thursday January 31, 2002
06:55 PM


[ #2569 ]
"Let's system stuff."

...these can be accessed as objects, returning...

"Oh, right. I was going to check that out anyway..."

Every time I try to use something, I'm told it's OO. I need to understand this, but to understand it I must do it.

"Well, let's look for an OOP tutorial in Perl."

And after many minutes of looking at one, I decided that Perl isn't a language one should learn OOP in...but many will attest you shouldn't learn it in C++ or Java.

I may just go try Ruby out and see if I can learn OOP while I learn Ruby. I understand the basics -- I believe -- but if I don't play around with it, I'll never really grok it.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Using objects is easy, if you know the secret: you're just telling something what to do. Think of it like sending a message. You want to tell me to go home? $chromatic->go('home');

    Programming objects is a little more difficult, but if you read perlboot and perltoot, you'll have the basics.

  • I really didn't find perlboot and perltoot all that useful, back when I was trying to learn thins stuff. So I went to the university library and looked at all the books about OOP. That was astonishingly unproductive. However, in some book (I think it was Adele Goldberg [] (an autodidact herself!) and Kenneth Rubin's Succeeding with Objects [] ) there happened to be a two or three page synopsis of basically what object-orientation means. And that explained it all to me. It's nice to occasionally find a speck
    • See, I think I understand the basic concept: Data structure(s) and ways to deal with said data structure(s) shrink-wrapped together in kind of an inseparable package. Said package can be duplicated, duplicated with frills, duplicated without certain things, duplicated just for the sake of having another one, etc.

      The trick now is fiddling around and seeing where my mental model of OO is somehow wrong, then playing around with it and some OO code until it's fixed.


      You are what you think.