unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: incoming parameter validation (float/double deprecated)
Date: Sat, 11 Aug 2012 08:45:33 -0700	[thread overview]
Message-ID: <CA+XASoUziyOhjaY-Td0E7Dq32utOXXTRyA=BfAL5sX7+sowANA@mail.gmail.com> (raw)

Hi,

I have started using  SCM_VALIDATE_XXX_COPY to check incoming parameters.

I have seen that for most of the types, for example uint, this is
equivalent to scm_to_uint which is what I was doing before.

I have also found that SCM_VALIDATE_FLOAT_COPY and
SCM_VALIDATE_DOUBLE_COPY use deprecated functions scm_num2float and
scm_num2double respectively.

So...

- Should SCM_VALIDATE_(FLOAT|DOUBLE)_COPY use scm_to_double?

- Are SCM_VALIDATE_XXX_COPY the way to go? Because it is ignoring the
pos argument. It seems, simply calling scm_to_int, etc. would be
enough. But that might change in the future, so I guess the macro is
fine.

Thanks in advance,

Aleix



             reply	other threads:[~2012-08-11 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-11 15:45 Aleix Conchillo Flaqué [this message]
2012-11-05 18:05 ` incoming parameter validation (float/double deprecated) Ludovic Courtès

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='CA+XASoUziyOhjaY-Td0E7Dq32utOXXTRyA=BfAL5sX7+sowANA@mail.gmail.com' \
    --to=aconchillo@gmail.com \
    --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).