Slash Boxes
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 ]

Theory (10)

  (email not shown publicly)
AOL IM: dwTheory (Add Buddy, Send Message)
Yahoo! ID: dew7e (Add User, Send Message)

Perl, PostgreSQL hacker; US politics junkie; Webapp developer; Portvangelist; profane iconoclast.


Journal of Theory (10)

Wednesday June 05, 2002
11:34 PM

More App::Info

[ #5453 ]

Yes, I put out a new version of App::Info today. Well, a couple of versions, actually.

First of all, all the problems with the unit tests should be fixed. They actually aren't all that comprehensive, but since the values returned form the various methods can vary, it didn't make sense for them to be super precise. I have internal unit tests that are more precise, and they don't execute when folks download App::Info from the CPAN.

But the major change in version 0.10 is the addition of error levels. Now when you construct an App::Info object, you can specify an error level that corresponds to a Carp function. Subclass writers (currently just your truly) then just have to use the error() method to record errors (although serious problems should probably just croak. Client code can specify how it wants to handle errors. The default is "carp", but the CPAN unit tests, for example, use "silent".

This functionality makes App::Info much more customizable for creating installation utilities, as the problems the subclasses run into -- such as not being able to find a files they need, or not being able to parse a value from a file -- can be set to be as verbose as necessary.

Next up, Matt Seargent suggests that I borrow from the AxKit Makefile.PL to make interrogating libiconv much more robust. Maybe in a couple of weeks. I've been back-burnering work that I really need to get done in order to work on this!

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.