From: Aaron VanDevender <sig@netdot.net>
Cc: guile-user@gnu.org
Subject: Re: guile.m4
Date: Wed, 14 Jun 2006 20:59:24 -0500 [thread overview]
Message-ID: <1150336764.2726.161.camel@lazlo.netdot.net> (raw)
In-Reply-To: <87pshb5j7x.fsf@zip.com.au>
On Thu, 2006-06-15 at 10:57 +1000, Kevin Ryde wrote:
> The autoconf philosophy is usually not to check version numbers
> explicitly if it can be avoided, better to check for desired
> feature(s).
>
> Since guile is interpreted you can do a lot at runtime instead of
> worrying about it during configure too.
Not really for my purposes. I want to be able to decide if I should use
SCM_MUST_MALLOC or scm_gc_malloc. This isn't something that the
interpreter can tell me. I suppose I can grep though the header file,
but it seemed that checking for the version was more robust.
Is there a better way?
--
sig@netdot.net
Plead the First.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2006-06-15 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-13 14:40 guile.m4 Aaron VanDevender
2006-06-14 0:17 ` guile.m4 Neil Jerram
2006-06-14 3:02 ` guile.m4 Aaron VanDevender
2006-06-15 0:57 ` guile.m4 Kevin Ryde
2006-06-15 1:59 ` Aaron VanDevender [this message]
2006-06-15 5:52 ` guile.m4 Stephen Compall
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=1150336764.2726.161.camel@lazlo.netdot.net \
--to=sig@netdot.net \
--cc=guile-user@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).