Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes: > Ripping out Error.pm for our few internal callers is one thing, trying > to maintain bugwards compatibility with how it throws exceptions for > users expecting Error.pm objects is another. I think at that point it's > easier to just stay with Error.pm. > > Probably easier to stay with it either way, don't poke sleeping dragons > and all that, it's working code, even if we wouldn't write it like that > today the churn probably isn't worth it. OK, I'm inclined to defer to your judgment. THanks.
