I agree. IMHO there's one thing that would help this whole situation: there should be a default, modern, easy to use OO framework/library that's recommended for serious work by the majority of "the perl/OO community" (if there is one).
Something that:
- Can subclass any other class that's using bless() the right way with any reference type. (I.e. it should use the inside-out fields technique)
- works with threads (and fork() emulation on windows) - won't use reference addresses to index fields.
- works with threads::shared - allows you to share objects across threads with minimal fuss.
- works with XS extensions and allows for easy mixed perl/XS classes/hierarchies.
The only thing I can think of is Object::InsideOut, though it could use a simple tutorial, some XS helper functions and possibly a less cluttered interface. Other suggestions are welcome.
If the community can decide on some default library like that, it should be put in the core.
I know the tendency is to keep as much as possible out of the core, but a default good OO layer (i.e. not Class::Struct) is just plain needed to be able to write good OO perl. It really is too much work to write reliable OO perl without using external modules.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|