unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r117286: Fix last commit.
Date: Mon, 09 Jun 2014 12:19:42 -0400	[thread overview]
Message-ID: <jwv1tuyvz7p.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <5394ABD6.1040100@cs.ucla.edu> (Paul Eggert's message of "Sun, 08 Jun 2014 11:30:46 -0700")

>>> I wish people could refrain from playing around with the
>>> >static/extern declarations.
>> I didn't.  I just fixed something that was already there.

This was not directed at you in particular, indeed.

> I think Stefan was referring to the practice of marking symbols as
> static if they're not used in other modules.

Right.

> Generally speaking this is good practice, as non-expert readers of the
> code needn't consider whether a static symbol might be used by another
> module.  It can help GCC in the same way.

Yes, but for things which are conceptually global (e.g. all the Qfoo
thingies, which by convention share namespace with Elisp's), the fact
they are currently only accessed from a single file doesn't mean it will
(or even should) stay that way, and adding "static" when that changes is
pointless (and just means we'll have to remove that "static" next time
it changes).

> However, I take Stefan's point that the practice gets messy when dealing
> with functions that can be static on typical GNU/Linux builds but must be
> extern on other ports.  So I installed trunk bzr 117290 to make these
> symbols extern.

Yes, that's better.


        Stefan



  parent reply	other threads:[~2014-06-09 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1WtB1v-0003W1-TA@vcs.savannah.gnu.org>
2014-06-08  0:50 ` [Emacs-diffs] trunk r117286: Fix last commit Stefan Monnier
2014-06-08 14:33   ` Eli Zaretskii
2014-06-08 18:30     ` Paul Eggert
2014-06-08 19:14       ` Eli Zaretskii
2014-06-09 16:19       ` Stefan Monnier [this message]
2014-06-09 16:44         ` Paul Eggert

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=jwv1tuyvz7p.fsf-monnier+emacsdiffs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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).