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.

All about App::Info 5 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Currently, if App::Info can't find the data it needs, it issues warnings. But this isn't the best approach, I think. Sometimes, you might want such errors to trigger exceptions. Other times, you might want them totally silent. So I was planning to add a flag to the API such that you can specify the behavior for such errors. Something like DBI's RaiseError or PrintError options. But then, it's just another step to add a prompting option. Such an option can be changed to prompt for new data at every step of t

    • Actually, that's more or less exactly what I was thinking of doing. The various subclasses would know what to do with a throw() depending on how the verbosity flag (for lack of a better word) was set.

  • The iconv checks look like they won't work very well across multiple platforms. A lot of platforms support iconv (the library) but don't have iconv the binary installed.

    It's this reason why AxKit's installer actually tries to compile a small XS module in order to test for the presence of iconv. You also need to know whether iconv is in -liconv, -llibiconv, or -lc.

    Yes, it's all horribly complicated, and pretty much the only way to be sure is to compile something and see if it runs.

    • I'm not surprised. It's just something I threw together as an example. Some versions of iconv.h don't appear to have the version number in them, either. However, I didn't get into this to have horribly complicated things to do (only PostgreSQL is easy to interrogate). Rather, I wanted to create a uniform interface for this sort of thing, and people who know more about the various packages than I do could contribute them and keep them up-to-date.

      IOW, patches welcome!

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