From: tomas@fabula.de
Cc: guile-devel@gnu.org
Subject: Re: How to replace a function
Date: Mon, 10 Mar 2003 13:25:10 +0100 [thread overview]
Message-ID: <20030310122510.GB26126@www> (raw)
In-Reply-To: <873clzxh1p.fsf@raven.i.defaultvalue.org>
On Fri, Mar 07, 2003 at 10:44:34AM -0600, Rob Browning wrote:
> tomas@fabula.de writes:
>
[About being compatible to two Guile versions]
> One other option. Could you you use something like this in a C file
> instead?
>
> #ifdef SCM_MAJOR_VERSION \
> && (SCM_MAJOR_VERSION == 1) \
> && (SCM_MINOR_VERSION == 6)
> # include "augment-1.6.c"
> #endif
>
> and add something similar in the header(s) for the missing prototypes?
Hmmm... It's tempting to skirt the Automonster this way, ain't it ;-)
But somehow a `feature test' seems to me the right thing here (and maybe
useful to others on this list). What do you think?
Thanks
-- tomas
prev parent reply other threads:[~2003-03-10 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 12:37 How to replace a function tomas
2003-03-07 16:38 ` Rob Browning
2003-03-10 12:21 ` tomas
2003-03-07 16:44 ` Rob Browning
2003-03-10 12:25 ` tomas [this message]
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=20030310122510.GB26126@www \
--to=tomas@fabula.de \
--cc=guile-devel@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).