From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Hook change hook?
Date: 14 Mar 2002 20:50:29 +0100 [thread overview]
Message-ID: <87pu27x722.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3u1s39b21.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> For a clean solution I guess we should either add a new
> scm_tc7_subr_3o type to the code (scary), or support genericization
> of cclos (also scary).
We should do the latter. I'll look at this and let you know when I
have something.
> PS. For future reference, here's the SCM_GDEFINE definition that I
> added to snarf.h to try this out:
>
> #define SCM_GDEFINE(FNAME, PRIMNAME, REQ, OPT, VAR, ARGLIST, DOCSTRING) \
> SCM_SNARF_HERE(\
> static const char s_ ## FNAME [] = PRIMNAME; \
> static SCM g_ ## FNAME; \
> SCM FNAME ARGLIST\
> )\
> SCM_SNARF_INIT(\
> scm_c_define_gsubr_with_generic (s_ ## FNAME, REQ, OPT, VAR, \
> (SCM_FUNC_CAST_ARBITRARY_ARGS) FNAME, \
> & g_ ## FNAME); \
Don't you need to initialize g_FNAME before calling
scm_c_define_gsubr_with_generic?
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next parent reply other threads:[~2002-03-14 19:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3lmdu7r01.fsf@laruns.ossau.uklinux.net>
[not found] ` <87ofigytfl.fsf@zagadka.ping.de>
[not found] ` <m3u1s39b21.fsf@laruns.ossau.uklinux.net>
2002-03-14 19:50 ` Marius Vollmer [this message]
2002-03-14 20:48 ` Hook change hook? Neil Jerram
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=87pu27x722.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.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).