[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Identifying what's usable in installed headers [was Re: RFC: Foreign
From: |
Ludovic Courtès |
Subject: |
Re: Identifying what's usable in installed headers [was Re: RFC: Foreign objects facility] |
Date: |
Sat, 03 May 2014 01:19:33 +0200 |
User-agent: |
Gnus/5.130009 (Ma Gnus v0.9) Emacs/24.3 (gnu/linux) |
Doug Evans <address@hidden> skribis:
> On Fri, May 2, 2014 at 4:44 AM, Ludovic Courtès <address@hidden> wrote:
>> Doug Evans <address@hidden> 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?
You got me. ;-)
These ones are not documented, and some of them are clearly too
low-level and expose too many implementation details (flags, indexes,
etc.)
‘SCM_STRUCTP’, ‘SCM_STRUCT_SLOT_REF’, and a few others may be OK, but
there are equivalent public functions anyway, so it’s better to use
them.
I’m not sure what to do for this particular header.
Ludo’.