in reply to Re^3: "require Carp" may be hazardous to your code (assume)
in thread "require Carp" may be hazardous to your code

because I don't like my modules failing in those rare environments when some module that most people presume that everyone has is actually missing.
You mean when core modules are missing?
  • Comment on Re^4: "require Carp" may be hazardous to your code (assume)

Replies are listed 'Best First'.
Re^5: "require Carp" may be hazardous to your code (core)
by tye (Sage) on Dec 06, 2006 at 08:02 UTC

    Yes, even core modules. This Linux box in front of me has 18 top-level core modules while a "better" install has 64 of those. And I actually added a few of those 18 "by hand", which was trickier than some might expect and I abandoned adding some others because it was just too much work. And I've seen more than one Perl installation that had even fewer than that.

    And I got DBI/DBD working on the above Linux box after working around some of many authors' rash assumptions about what modules are always going to be available. Many of those work-arounds were trivial to code (the amount of functionality they were depending on from the module was trivial -- and yet they just die if it isn't there) but finding them all was a big pain.

    Yes, I realize I'm unusual in even acknowledging that such sub-core installations of Perl exist in the world, much less in doing a tiny bit of extra coding in some cases to work around missing modules when it is easy.

    - tye