Now before you reach for the "my OO response", -- this post on principle that it's sounds like I don't like Perl, or you just get plain bored of this ramble (sic). If someone asked me about Objects in Perl, I'd enthuse but I'm not sure I'd be recommending Perl Object Oriented Coding. So what is your handle on Perl Objects, do you have one way of using them, or do you hack scripts using a tie somedays and develop reusable software the next.

I've being delving into Perl Objects for a while and it's been a real eye-opener. Perl isn't built to do objects the way other languages do. ( I knew it already but the devil is in the detail )

I'm not judging which language is best, it'd be pointless:

• Perl makes objects easy in a way that is bewildering. If I make an object, I can create accessor and mutator methods using AUTOLOAD, which is baaad and you could say "don't do it then!", and yes Perl always expects a modicum of common sense.

• If I want private and public methods, you have to create class methods to enforce this, I guess if I wanted to I could make it an instance method.
• If I want to alter the inheritance at run-time, I'm guessing I'd juggle the contents of @ISA.
• I can write TIE functions to totally obscure my object methods, making dinky code that to the untrained eye makes little sense. ( Not that I disapprove of training users by example, mind ;).

Ok, the bones of the matter, I like Perl and I like the concept of Object Orientation in it's pristine state. I'm beginning to appreciate that Perl has an irreverant view of OO (as it has to most things ;) so this means Perl OO can be coded well, which'll probably involve creating some reflective code, or perhaps just good OO principles, it also means (to me, at least) that Perl has a superset of OO uses, leaning on it's easy attitude to OO and quirky extras.

What I want to discover is: how to do good OO in the Perl idiom (I'm going to say TIMTOADI¹, so you can't!  :^) preferably by following good examples (got any of your own, or can you recommend a good module, so I can read the source?) and how to abuse OO more than I do for my own amusement and my increased productivity. (program performance is rarely an issue for me :o)

1) I want to see different examples of peoples code to understand how, folks restrain Perl to the OO principles, ( or not as the case may be ;0)

--

Brother Frankus.
sub - rosa:

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.