From: David Gibson <david@gibson.dropbear.id.au>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: dtc: Simplify error handling for unparseable input
Date: Wed, 26 Mar 2008 08:21:27 +1100 [thread overview]
Message-ID: <20080325212127.GA8281@localhost.localdomain> (raw)
In-Reply-To: <20080325143619.GB13187@ld0162-tx32.am.freescale.net>
On Tue, Mar 25, 2008 at 09:36:19AM -0500, Scott Wood wrote:
> On Tue, Mar 25, 2008 at 12:28:05PM +1100, David Gibson wrote:
> > On Mon, Mar 24, 2008 at 12:36:41PM -0500, Scott Wood wrote:
> > > If you remove this, there'll be no way to indicate semantic errors other
> > > than die() (the NULL approaches are no good, since they inhibit recovery),
> > > which is suboptimal if the error is not immediately fatal.
> >
> > But everything is immediately fatal. When we have a *real* example of
> > something that's not, we can restore an error code.
>
> Failed binary includes are not immediately fatal.
And is there any advantage to having them not immediately fatal?
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2008-03-25 21:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 3:44 dtc: Simplify error handling for unparseable input David Gibson
2008-03-24 17:36 ` Scott Wood
2008-03-25 1:28 ` David Gibson
2008-03-25 14:36 ` Scott Wood
2008-03-25 21:21 ` David Gibson [this message]
2008-03-25 22:10 ` Scott Wood
2008-03-25 23:52 ` David Gibson
2008-03-26 1:16 ` Scott Wood
2008-03-25 23:59 ` David Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080325212127.GA8281@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.