Follow up, two more "use cases" that I've come to appreciate
Util::H2O for simplifying:
- Resulting scrape object via Web::Scraper
- Processing the results retrieved from DBI's selectall_arrayref
In all cases, above, it's pretty clear that the primary benefit of
Util::H2O's
h2o is in providing accessors for
ad hoc hash references and being able to treat them as objects during a program
in flight. One improvement would be to say,
if this key is not defined, return 'undef'. Which is the point of a current feature request on the GH issues list for this module.