From: Doug Evans <xdje42@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Identifying what's usable in installed headers [was Re: RFC: Foreign objects facility]
Date: Fri, 2 May 2014 11:34:58 -0700 [thread overview]
Message-ID: <CAP9bCMR0VEHsEFxxpM1ztpTUnm6Sd6s-Xpwg+qW0mZ+A9NTR9Q@mail.gmail.com> (raw)
In-Reply-To: <87mwf09zhg.fsf@gnu.org>
On Fri, May 2, 2014 at 4:44 AM, Ludovic Courtès <ludo@gnu.org> wrote:
> Doug Evans <xdje42@gmail.com> skribis:
>
>> While function declarations are markable as being internal/external in
>> published headers (SCM_INTERNAL vs SCM_API), macros are not.
>
> Internal macros are marked by a naming convention: they are prefixed by
> ‘SCM_I’.
Hi. Sorry, catching up on mail.
So this means that struct.h:SCM_STRUCT_* are ok to use by apps, right?
next prev parent reply other threads:[~2014-05-02 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 16:33 Identifying what's usable in installed headers [was Re: RFC: Foreign objects facility] Doug Evans
2014-04-29 18:33 ` Andy Wingo
2014-05-02 11:44 ` Ludovic Courtès
2014-05-02 18:34 ` Doug Evans [this message]
2014-05-02 23:19 ` Ludovic Courtès
2014-05-03 4:18 ` Doug Evans
2014-05-05 16:03 ` Ludovic Courtès
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP9bCMR0VEHsEFxxpM1ztpTUnm6Sd6s-Xpwg+qW0mZ+A9NTR9Q@mail.gmail.com \
--to=xdje42@gmail.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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.
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).