unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r112828: Merge the specpdl	and	backtrace stacks. Make the structure of the
Date: Tue, 18 Jun 2013 22:05:32 +0300	[thread overview]
Message-ID: <83sj0fqlxf.fsf@gnu.org> (raw)
In-Reply-To: <51C0AC0E.2020907@cs.ucla.edu>

> Date: Tue, 18 Jun 2013 11:50:54 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> Cc: emacs-devel@gnu.org
> 
> > how to explain the
> > fact that revision 112828 produced unresolved externals for such
> > functions that were defined in the same file (eval.c)?
> 
> 112828 declared LISP_INLINE functions in eval.c.
> That wasn't right for C99 platforms, because
> in eval.c LISP_INLINE expands to plain 'inline',
> and C99 requires that if any module defines a plain
> inline function FOO (perhaps via a .h file), then
> FOO must be defined as 'extern inline' in exactly one
> other module.

So you are saying that the following is not valid C99, unless another
module defines 'foo' as 'extern inline'?

 inline int foo (void) { return 42; }
 int bar (void) { return foo (); }

That sounds strangely un-C-ish to me.

Thanks.



  reply	other threads:[~2013-06-18 19:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1UjQtA-0006p7-My@vcs.savannah.gnu.org>
2013-06-03 13:59 ` [Emacs-diffs] /srv/bzr/emacs/trunk r112828: Merge the specpdl and backtrace stacks. Make the structure of the Juanma Barranquero
2013-06-03 14:01   ` Juanma Barranquero
2013-06-03 18:25   ` Stefan Monnier
2013-06-03 19:23     ` Eli Zaretskii
2013-06-04  5:55       ` Paul Eggert
2013-06-04 15:13         ` Eli Zaretskii
2013-06-18 18:50           ` Paul Eggert
2013-06-18 19:05             ` Eli Zaretskii [this message]
2013-06-18 20:56               ` 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=83sj0fqlxf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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).