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

use Perl Log In

Log In

[ Create a new account ]

2shortplanks (968)

2shortplanks
  (email not shown publicly)
http://2shortplanks.com/
AOL IM: trelane2sp (Add Buddy, Send Message)
Yahoo! ID: trelane2sp (Add User, Send Message)
Mark Fowler has never been the same since he was elected leader of the London Perl Mongers. The strain manifests itself mainly in releasing various [cpan.org] modules [cpan.org] to CPAN, giving talks [2shortplanks.com], and use of the Trelane nick on #london.pm for endless procrastination. Doctors are still seeking a cure.

Journal of 2shortplanks (968)

Monday March 25, 2002
04:56 PM

Accessor Test Module in progress, please wait...

[ #3767 ]
Following on from the talk that I gave at the London.pm technical meeting I decided to do some work on developing the module I'd created to demonstrate using Test::Builder and Test::Builder::Tester into a real module. You know. With tests and documentation and even one of those handy dandy Makefile.PL files.

Originally called Test::GetSet and since renamed to Test::Accessor it's a module that checks if an accessor method can be set to a value and return the same value. More importantly, it also checks if your module complains in the correct way when you pass bad values. Sounds simple, eh?

Well no. Considering that I could think of three different ways to signal that a method was passed an incorrect value (return undef, return false, throw an exception) and have various combinations of those to be either acceptable expected failures or unexcepted failures. Now throw in the complication that I can think of five different naming conventions for accessor methods (foo, getfoo, get_foo, foo_get, fooget.)

Darnit, this was meant to be a simple hack. The work continues.

<Trelane> my fun todo?
<dipsy> Trelane, your fun todo is probably install slash on intranet server, gtk wrapper for sudo, Test::GD, GD::TextImage, add things to grubstreet, read the jabber book or patch T::P::XML::DOM documentation, write documentation for TT and XML, write an rsync backup scripts or makepm script or tidy up Test::Accessor and CPAN it


List all Journal entries
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Accessor Test Module in progress, please wait... 5 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • That's without taking into account getFoo, and then all the variants of has which is frequently used (in some circles) for boolean and/or list accessors...

    --

    -- Robin Berjon [berjon.com]

    • Oh I'd forgotten that. I'll add getFoo and fooGet.

      I'm not sure about has. Java peeps might be tempted to call methods is_foo isFoo too (though probably not foo_is or fooIs.)

      That's a bit annoying. I can't think of any way to automatically deal with this as people might be using both has, is and get and set in the same module.

      Maybe I should add a final option "automatic" where I search your namespace for methods (thought repeated calls to "can".) Main trouble with doing that is that it won't work for A

      • Yes, "is" is definitely part of the landscape as well. "has" occurs mostly for list accessors (iow what are seens as lists/arrays in Perl, but are usually array-like objects in other languages). For instance:

          $el->setChildNodes(@kids);
          ...
          if ($el->hasChildNodes) {...}

        Of course, this opens the can of worms of the addFoo setters and friends... not sure you want to go there.

        You might want, instead of can(), to use eval {} and see if the call works. Of course, this wor

        --

        -- Robin Berjon [berjon.com]

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.