comment on

Inspired by previous discussions on using arrays with inside-out objects (inside-out objects using arrays?), I modified Object::InsideOut to allow the use of arrays (as well as hashes) for storing object field data.

I tested the performance of array-based Object::InsideOut objects on several platforms, and was impressed with the results: I got anywhere from 20% (Solaris) to 40% (ActivePerl) performance improvement for basic fetch and store operations over blessed-hash objects!

I hope this may prove to be sufficient incentive for some of my fellow monks to give Object::InsideOut a try. This lastest version is available on CPAN. Enjoy.

Update:
In addition to speed improvements, using arrays consumes less memory because Perl doesn't have to store hash keys for the object field data.

The programming effort for using hash-based inside-out objects and array-based inside-out objects is the same: You just use '@' instead of '%' when declaring your object data fields.

Update 2:
I just uploaded v1.01.00 which adds support for object serialization.

See New Module Announcement: Object::InsideOut for more discussion on Object::InsideOut.

Remember: There's always one more bug.

In reply to Array-based Inside-out Objects with Object::InsideOut by jdhedden

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.


Keep It Simple, Stupid
	PerlMonks