unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan D." <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: Re: GTK patches part 2
Date: Tue, 10 Dec 2002 21:44:24 +0100 (MET)	[thread overview]
Message-ID: <200212102040.gBAKe116016464@stubby.bodenonline.com> (raw)
In-Reply-To: <15982.1039550899@remus.pretzelnet.org> from "Eric Gillespie" at dec 10, 2002 03:08:19

> 
> "Jan D." <jan.h.d@swipnet.se> writes:
> 
> > Well, I don't usually add include:s unless needed.  For example,
> > xterm.h includes X11 headers who in turn includes a lot of standard
> > headers.  If what is needed gets included that way, I'm fine with it.
> 
> You can't rely on that.  If *you* make reference to symbols or
> macros, *you* need to include the appropriate header file,
> regardless of whether or not some other header you include also
> needs that header file.  Sometimes people just dump all their

There is no such requrement in the C standard, even if it makes
sense for some people.

> includes into one local header file and just include that.  It
> gets the job done, but then each file isn't explicitly declaring
> what it needs.

For example, stdlib.h is included by config.h, so it is clearly
redundant to do so elsewhere.  I can put in stdio.h just for the
sake of portability.

	Jan D.

  reply	other threads:[~2002-12-10 20:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08 22:33 GTK patches part 2 Jan D.
2002-12-09 21:25 ` Eric Gillespie
2002-12-10 18:28   ` Jan D.
2002-12-10 19:06     ` Eric Gillespie
2002-12-10 19:33       ` Jan D.
2002-12-10 20:08         ` Eric Gillespie
2002-12-10 20:44           ` Jan D. [this message]
2002-12-10 21:23             ` Eric Gillespie
2002-12-11 17:45               ` Richard Stallman
2002-12-11 20:04                 ` Eric Gillespie
2002-12-12  6:05                   ` Eli Zaretskii
2002-12-11 17:48               ` Jan D.

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200212102040.gBAKe116016464@stubby.bodenonline.com \
    --to=jan.h.d@swipnet.se \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).