From: Kevin Ryde <user42@zip.com.au>
Subject: trunc #define
Date: Mon, 17 May 2004 07:57:12 +1000 [thread overview]
Message-ID: <87pt94xcg7.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 198 bytes --]
* numbers.c (trunc): Remove #define to scm_truncate when the C library
doesn't provide trunc. This was for when `truncate' was done as a
scm_tc7_dsubr, no longer required.
[-- Attachment #2: numbers.c.define-trunc.diff --]
[-- Type: text/plain, Size: 265 bytes --]
--- numbers.c.~1.243.~ 2004-05-12 07:19:25.000000000 +1000
+++ numbers.c 2004-05-16 18:09:26.000000000 +1000
@@ -4937,7 +4937,6 @@
#if HAVE_TRUNC
return trunc (x);
#else
-#define trunc scm_truncate
if (x < 0.0)
return -floor (-x);
return floor (x);
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2004-05-16 21:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87pt94xcg7.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).