Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'm disheartened to hear that you're having trouble with another programmer's code, and laying the blame solely on OIO. If you need help, OIO's POD references both the module's discussion forum [cpanforum.com] and the author's email: jdhedden AT cpan DOT org.

    While OIO's POD does discuss some of the advantages of using the inside-out object model, it also lists several more involved discussions on the matter including Damian Conway's book Perl Best Practices.

    OIO does provide methods for maintaining persistent data, bu

    • I was having problems with O:IO because of it's frankly bizarre idea of requiring a user to provide regexen to match method/attributes, not to mention it's abuse of attributes syntax (yummy - whitespace sensitive code for no good reason).

      The number of places where it was needlessly complex and required copy and pasting where any sensible Class framework allows you to just specify the columns and have it DTRT.

      "OIO does provide methods for maintaining persistent data, but not directly to a database. However,
      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • "requiring a user to provide regexen to match method/attributes"

        It's not a requirement - it's optional. Cut out the regexes, and your preformance will go up (probably significantly). The regex option is there to provide greater programming flexibility if that is desired. As with any feature, if it's not needed, then don't use it.

        "There is a great deal more to useful object persistence than a couple of SQL statements..."

        The requirement to tie your objects to a database was evidently something the original coder failed to properly take into account. As OIO does not support this sort of thing, then obviously it was not the right tool for the job. It's senseless to condemn the screwdriver for not being a very good hammer.

        "O::IO and it's ilk are interesting illustrations of some concepts but have no place in production code."

        In your humble opinion, of course. OIO is being used quite a bit in production code (based on the correspondences I have had with users). So it's down do agreeing to disagree.

        'Nuff said. Good luck with your rewrite. Sorry I couldn't be of any help.

        • Great :) I'd love to get rid of the regexen, but now they are there I don't know where they are used and would need to check - it looks to me that the original author cargo culted because the documentation wasn't clear enough - I certainly didn't find a nice simple example in the documentation.

          Class::Accessor and it's like allow me to specify my attributes in a single line, even Moose is less bizarre in how you specify attributes.

          I'm surprised people would choose to use O::IO in production code, I certainl
          --

          @JAPH = qw(Hacker Perl Another Just);
          print reverse @JAPH;