Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA/OBVIOUS?] ui_file_new function missing "extern" in header.
Date: Tue, 18 Dec 2012 08:35:00 -0000	[thread overview]
Message-ID: <001801cddcfa$a93cef10$fbb6cd30$@muller@ics-cnrs.unistra.fr> (raw)

   This is both a RFA
 and a question about:
  should this be considered as an obvious fix?
  
  i.e. shouldn't all functions declared in headers
have the extern modifier?
  Is this mandatory?
  It doesn't see to change anything in practice, but to me,
it seems like good practice...
... but remember that my C programming knowledge is weak...




Pierre Muller
GDB pascal language maintainer


2012-12-18  Pierre Muller  <muller@sourceware.org>

        * ui-file.h (tee_file_new): Add extern modifier in header
declaration.

Index: ui-file.h
===================================================================
RCS file: /cvs/src/src/gdb/ui-file.h,v
retrieving revision 1.19
diff -u -p -r1.19 ui-file.h
--- ui-file.h   18 Dec 2012 07:01:58 -0000      1.19
+++ ui-file.h   18 Dec 2012 08:31:00 -0000
@@ -135,7 +135,7 @@ extern struct ui_file *gdb_fopen (char *
 /* Create a file which writes to both ONE and TWO.  CLOSE_ONE
    and CLOSE_TWO indicate whether the original files should be
    closed when the new file is closed.  */
-struct ui_file *tee_file_new (struct ui_file *one,
+extern struct ui_file *tee_file_new (struct ui_file *one,
                              int close_one,
                              struct ui_file *two,
                              int close_two);


             reply	other threads:[~2012-12-18  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18  8:35 Pierre Muller [this message]
2012-12-18  8:47 ` Jan Kratochvil
2012-12-22 18:57   ` Pierre Muller
2012-12-18  8:54 ` Yao Qi
2012-12-18  9:00   ` Jan Kratochvil
     [not found] <20105.7837847204$1355819774@news.gmane.org>
2012-12-18 16:27 ` Tom Tromey

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='001801cddcfa$a93cef10$fbb6cd30$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --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