From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: lekktu@gmail.com, 12116@debbugs.gnu.org
Subject: bug#12116: merge from gnulib for extern-inline
Date: Thu, 02 Aug 2012 22:49:37 +0300 [thread overview]
Message-ID: <837gthcbvy.fsf@gnu.org> (raw)
In-Reply-To: <501AC0D3.6080300@cs.ucla.edu>
> Date: Thu, 02 Aug 2012 11:02:59 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: 12116@debbugs.gnu.org, lekktu@gmail.com
>
> e x p a n s i o n i n :
> macro C99 older compilers ancient compilers
> INLINE inline static inline static
> EXTERN_INLINE extern inline static inline static
>
> and the Emacs include file charset.h does this:
>
> #ifndef CHARSET_INLINE
> # define CHARSET_INLINE INLINE
> #endif
>
> CHARSET_INLINE void
> set_charset_attr (struct charset *charset, enum charset_attr_index idx,
> Lisp_Object val)
> {
> ASET (CHARSET_ATTRIBUTES (charset), idx, val);
> }
>
> so in C99 most users of charset.h see the function as being
> 'inline void'. charset.c does this before including charset.h:
>
> #define CHARSET_INLINE EXTERN_INLINE
>
> so that when it's compiled, the function is 'extern inline void'.
> In pre-C99 compilers the function is 'static inline' or (if ancient)
> plain 'static'. Similarly for each .h file that uses inline functions.
OK, but what's the story with the addition of stat-time.c,
utimespec.c, and u64.c, which just include the respective headers?
Where and how are these used, and for what purposes?
I understood the extern inline stuff, I just don't get why are these
*.c files introduced.
next prev parent reply other threads:[~2012-08-02 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 22:18 bug#12116: merge from gnulib for extern-inline Paul Eggert
2012-08-02 6:17 ` Paul Eggert
2012-08-02 15:07 ` Eli Zaretskii
2012-08-02 18:02 ` Paul Eggert
2012-08-02 19:49 ` Eli Zaretskii [this message]
2012-08-02 21:20 ` Paul Eggert
2012-08-03 11:09 ` Eli Zaretskii
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=837gthcbvy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12116@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=lekktu@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.