Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Require extern modifier for function prototypes in headers.
Date: Wed, 19 Dec 2012 21:48:00 -0000	[thread overview]
Message-ID: <002201cdde32$8b3379b0$a19a6d10$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <83r4mmnfm7.fsf@gnu.org>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Eli Zaretskii
> Envoyé : mercredi 19 décembre 2012 17:58
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] Require extern modifier for function prototypes in
> headers.
> 
> > From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
> > Date: Wed, 19 Dec 2012 12:24:56 +0100
> >
> >  All external functions should have a declaration in a header file that
> > -callers include, except for @code{_initialize_*} functions, which must
> > +callers include, that declaration should use the @code{extern}
modifier.
> > +The only exception concerns @code{_initialize_*} functions, which must
> >  be external so that @file{init.c} construction works, but shouldn't be
> >  visible to random source files.
> 
> If all declarations must be external, the _initialize_* case is no
> longer special, so the second sentence should go away, IMO.


  I thought that it was still special in the sense that they
are the only non-static functions that are not declared in headers,
but only inside the C source itself.

 
> Otherwise, OK with me.
> 
> Thanks.

Pierre


  reply	other threads:[~2012-12-19 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000001cddddb$7999a0a0$6ccce1e0$%muller@ics-cnrs.unistra.fr>
2012-12-19 16:58 ` Eli Zaretskii
2012-12-19 21:48   ` Pierre Muller [this message]
2012-12-19 11:25     ` Pierre Muller
2012-12-22 12:54       ` Jan Kratochvil
2012-12-22 17:53         ` Pierre Muller

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='002201cdde32$8b3379b0$a19a6d10$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox