unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Andy Wingo" <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, master, updated. release_1-9-6-75-g9c246c0
Date: Tue, 05 Jan 2010 18:57:07 +0100	[thread overview]
Message-ID: <87r5q48mfg.fsf@gnu.org> (raw)
In-Reply-To: <E1NSBM6-00076R-0m@cvs.savannah.gnu.org> (Andy Wingo's message of "Tue, 05 Jan 2010 15:29:58 +0000")

Hi Andy!

"Andy Wingo" <wingo@pobox.com> writes:

> commit 9fdf9fd3ea7130fd85eaf0a333a965ac4d2b07c3
> Author: Andy Wingo <wingo@pobox.com>
> Date:   Tue Jan 5 16:15:14 2010 +0100
>
>     move subr implementation details to gsubr.[ch]
>     
>     * libguile/procs.h: Move subr macros to gsubr.h.
>     * libguile/procs.c (scm_c_make_subr, scm_c_make_subr_with_generic)
>       (scm_c_define_subr, scm_c_define_subr_with_generic): Remove these,
>       because they deal in subr types, and now there is only one subr type.

This is slightly scary, because these were really-public functions, but
I guess there’s no other choice anyway (and fundamentally I think this
change is going in the Right Direction!).

> +/* Deprecated 2010-01-05, use SCM_PRIMITIVE_P instead */
> +#define scm_subr_p(x) (SCM_PRIMITIVE_P (x))

Can you change it so it generates a link-time and run-time warning?
See, e.g., ‘scm_mask_ints’.

> +/* Return the most suitable subr type for a subr with REQ required arguments,
> +   OPT optional arguments, and REST (0 or 1) arguments.  This has to be in
> +   sync with `create_gsubr ()'.  */
> +#define SCM_SUBR_ARITY_TO_TYPE(req, opt, rest)				\
> +  (scm_tc7_gsubr | (SCM_GSUBR_MAKTYPE (req, opt, rest) << 8U))

“Most suitable” and the second sentence can be removed now.

Thanks,
Ludo’.




       reply	other threads:[~2010-01-05 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1NSBM6-00076R-0m@cvs.savannah.gnu.org>
2010-01-05 17:57 ` Ludovic Courtès [this message]
2010-01-06 10:13   ` [Guile-commits] GNU Guile branch, master, updated. release_1-9-6-75-g9c246c0 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=87r5q48mfg.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /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).