Re: RFC: Foreign objects facility

2014-05-02 Thread Doug Evans
On Tue, Apr 29, 2014 at 11:25 AM, Andy Wingo wrote: > Hi! > > Thanks for the feedback, it's really useful. > > On Tue 29 Apr 2014 17:56, Doug Evans writes: > >> The struct interface, contrary to what the documentation says, takes a >> stdarg list beginning with the number of fields (and not termi

Re: RFC: Foreign objects facility

2014-05-02 Thread Doug Evans
On Sun, Apr 27, 2014 at 10:51 AM, Andy Wingo wrote: >[...] >> Portability is more problematic for pointer types. The C standards make >> no guarantees about the semantics of converting between pointers and >> integers, and it's not clear to me how future proof this will be. > > Don't they make so

Re: Identifying what's usable in installed headers [was Re: RFC: Foreign objects facility]

2014-05-02 Thread Doug Evans
On Fri, May 2, 2014 at 4:19 PM, Ludovic Courtès wrote: > Doug Evans skribis: > >> On Fri, May 2, 2014 at 4:44 AM, Ludovic Courtès wrote: >>> Doug Evans skribis: >>> While function declarations are markable as being internal/external in published headers (SCM_INTERNAL vs SCM_API), macr

Re: Identifying what's usable in installed headers [was Re: RFC: Foreign objects facility]

2014-05-02 Thread Ludovic Courtès
Doug Evans skribis: > On Fri, May 2, 2014 at 4:44 AM, Ludovic Courtès wrote: >> Doug Evans 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 convent

bdw-gc hack

2014-05-02 Thread Stefan Israelsson Tampe
Hi all, I'm working with two paths right now when it comes to gc. 1. Using finalizers, that fails right now 2. A modded version of bdw-gc found at https://gitorious.org/bdw-gc-logical-mod I was thinking of showing how the new API in 2) is working, just for the curious. So: GC_new_kind_adv (...,

guile-gnome, master: fix unless macro definition for guile prior to guile-2 only

2014-05-02 Thread David Pirotte
Hello, guile-gnome master: fix unless macro definition for guile prior to guile-2 only Patch review solicited. Thanks, David >From 910343bf6793d512979af851b504b83b06a10ed2 Mon Sep 17 00:00:00 2001 From: David PIROTTE Date: Fri, 2 May 2014 16:01:30 -0300 Subject: [PATCH 2/2] fi

guile-gnome, master: fix scm-error incorrect arg ist in gtk.scm

2014-05-02 Thread David Pirotte
Hello, guile-gnome master: fix scm-error incorrect arg ist in gtk.scm Patch review solicited. Thanks, David>From df58a66726803f4698356d721d7611d2d11c9ee7 Mon Sep 17 00:00:00 2001 From: David PIROTTE Date: Fri, 2 May 2014 15:38:55 -0300 Subject: [PATCH 1/2] fix scm-error incorr

Re: Identifying what's usable in installed headers [was Re: RFC: Foreign objects facility]

2014-05-02 Thread Doug Evans
On Fri, May 2, 2014 at 4:44 AM, Ludovic Courtès wrote: > Doug Evans 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 > ‘S

Is struct.h:SCM_STRUCT_* "exported"?

2014-05-02 Thread Doug Evans
Hi. Is any of the following exported? [or are they internal implementation details?] I can certainly imagine it's the latter, but the DATA versions do solve the problem (*1) of accessing struct fields as raw values. #define SCM_STRUCT_DATA(X) ((scm_t_bits*)SCM_CELL_WORD_1 (X)) #defi

Re: Identifying what's usable in installed headers [was Re: RFC: Foreign objects facility]

2014-05-02 Thread Ludovic Courtès
Doug Evans 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’. If this convention is deemed insufficient, we could #ifdef