From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Guile 1.8 success on `i386-apple-darwin9.6.0'
Date: Fri, 27 Mar 2009 20:14:39 +0000 [thread overview]
Message-ID: <8763hurads.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <87ab774a1n.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri\, 27 Mar 2009 09\:58\:12 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Good morning!
Hello again!
>> Just one nit: I think there's now only 1 piece of Automake magic being
>> relied on, so you could update that text (in Makefile.am) and remove
>> the "2. ".
>
> Right, I did this:
>
> http://git.savannah.gnu.org/cgit/guile.git/commit/?id=0fe95f9c4ce063781e79a15bc123c57c33ef9755
Thanks, that looks good.
> So IIUC you're advocating the creation of 88 new header files, right?
Potentially, yes. :-)
> I think I'd prefer the single-private-header option, but I'm not 100%
> convinced either.
>
> Actually there's yet another option: enclose internal declarations in
> "#ifdef LIBGUILE_IN_LIBGUILE" or similar, which we only define when
> compiling Guile itself. This is what Glibc does with, e.g.,
> `__LIBC_INTERNAL_MATH_INLINES' and what GMP does with
> `__GMP_WITHIN_GMP'. I think I like it better.
That sounds fine to me too - so I guess we should choose this
approach. Although I would find "LIBGUILE_INTERNAL" more intuitive
than "LIBGUILE_IN_LIBGUILE".
Regards,
Neil
next prev parent reply other threads:[~2009-03-27 20:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 17:08 Guile 1.8 success on `i386-apple-darwin9.6.0' Ludovic Courtès
2009-03-26 18:34 ` Ludovic Courtès
2009-03-26 21:10 ` Neil Jerram
2009-03-26 21:36 ` Ludovic Courtès
2009-03-26 22:21 ` Neil Jerram
2009-03-27 8:58 ` Ludovic Courtès
2009-03-27 20:14 ` Neil Jerram [this message]
2009-03-27 13:48 ` Greg Troxel
2009-03-27 14:54 ` Ludovic Courtès
2009-03-27 18:34 ` Greg Troxel
2009-03-31 16:10 ` Dealing with cross-compilation Ludovic Courtès
2009-03-31 19:04 ` Andy Wingo
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=8763hurads.fsf@arudy.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).