[Exherbo-dev] Some functions die, some don't

Bryan Østergaard bryan.ostergaard at gmail.com
Mon Feb 4 11:01:20 GMT 2008


On Feb 2, 2008 4:48 PM, David Leverton <levertond at googlemail.com> wrote:
> On Saturday 02 February 2008 15:28:06 Ciaran McCreesh wrote:
> > Some functions die on failure, some don't. It's not obvious which is
> > which. Currently, econf will die if it fails, but emake won't, and the
> > do* stuff is anyone's guess.
>
> (emake actually does die in exheres, unlike Gentoo.  I suppose this proves
> your point....)
>
> > 3) econf, emake etc all do die, and try_econf doesn't.
>
> I prefer this one - dying is probably what people want most of the time, so it
> should be the least cluttered.  The only disadvantage that I can see is that
> you don't get to specify a detailed message, and the backtrace is somewhat
> less useful than it could be because it refers to loadsaveenv rather than the
> original source.
>
I'd prefer this as well. I'm using the same message for all the econf
or make die's so far and more detailed messages could still be done
using try_econf || die "blah" and similar.

Regards,
Bryan Østergaard


More information about the Exherbo-dev mailing list