unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: Summary of config.h variables and questions.
Date: Fri, 07 Mar 2003 08:10:52 +1000	[thread overview]
Message-ID: <87of4okuxf.fsf@zip.com.au> (raw)
In-Reply-To: 87znoal646.fsf@raven.i.defaultvalue.org

Rob Browning <rlb@defaultvalue.org> writes:
>
> Note that "const" and "inline" above are normally #defined by
> configure in config.h to be something suitable for the given platform
> when possible, or #undef'ed otherwise.  If we have been (or want to)
> take advantage of this facility in our public headers, we probably
> need to use SCM_INLINE and SCM_CONST or similar...

It's worth bearing in mind that const and inline are aspects of the
compiler, so ideally they'd be determined based on #ifdefs, allowing
an application to be built with a different compiler than guile was
compiled with.

I'd suspect const doesn't need to be tested these days, especially not
if K&R isn't supported by the rest of the header file stuff.

For inline, maybe just testing for gcc or C++ would be enough, and let
anyone using a vendor compiler put their hand up.  If inline is only
used for optimizations then there'd be no great loss if a few non-free
compilers missed out on it.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2003-03-06 22:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05  5:44 Summary of config.h variables and questions Rob Browning
2003-03-06 14:37 ` Marius Vollmer
2003-03-06 15:57   ` Rob Browning
2003-03-06 16:21     ` Marius Vollmer
2003-03-06 16:32       ` Rob Browning
2003-03-06 16:34       ` Rob Browning
2003-03-06 16:48         ` Marius Vollmer
2003-03-06 16:49     ` Marius Vollmer
2003-03-06 17:26     ` Mikael Djurfeldt
2003-03-06 18:27   ` Rob Browning
2003-03-06 18:48     ` Marius Vollmer
2003-03-06 22:10 ` Kevin Ryde [this message]
2003-03-07  5:24   ` Rob Browning

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=87of4okuxf.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).