From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] flash.h: pull in common.h for types
Date: Tue, 17 Nov 2009 22:00:15 +0100 [thread overview]
Message-ID: <20091117210015.3545CF51B08@gemini.denx.de> (raw)
In-Reply-To: <200911161703.46965.vapier@gentoo.org>
Dear Mike Frysinger,
In message <200911161703.46965.vapier@gentoo.org> you wrote:
>
> > Why would that be needed? Which problem are you trying to solve?
>
> like the subject very briefly says, 'for types'. if your source code includes
> flash.h before anything else, it'll fail to compile as flash.h uses types not
> declared implicitly by the compiler.
I'm not sure if this is needed or even wanted.
We don't attempt to make all header files self-sufficient, or do we?
Does Linux do this?
When looking at man pages for system calls and library funtions it
seems this is not the case; also, I can find wise people argumenting
against self-sufficient headers (and others argumenting in their
favour).
My question: is there a definitive position somewhere (for example
for the Linux kernel; I'm sure we don't have one for U-Boot [yet]),
whether system headers should be self-sufficient?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
One does not thank logic.
-- Sarek, "Journey to Babel", stardate 3842.4
next prev parent reply other threads:[~2009-11-17 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 19:58 [U-Boot] [PATCH] flash.h: pull in common.h for types Mike Frysinger
2009-11-16 21:31 ` Wolfgang Denk
2009-11-16 22:03 ` Mike Frysinger
2009-11-17 21:00 ` Wolfgang Denk [this message]
2009-11-17 21:10 ` Scott Wood
2009-11-17 21:56 ` Wolfgang Denk
2009-11-18 0:01 ` Scott Wood
2009-11-18 0:18 ` Mike Frysinger
2009-11-18 1:34 ` J. William Campbell
2009-11-18 22:28 ` Wolfgang Denk
2009-11-18 23:43 ` Mike Frysinger
2010-01-18 1:52 ` Mike Frysinger
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=20091117210015.3545CF51B08@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox