public inbox for guile-cvs@sourceware.org help / color / mirror / Atom feed
From: mdj@sourceware.cygnus.com To: guile-cvs@sourceware.cygnus.com Subject: guile/guile-core/libguile numbers.h Date: Mon, 13 Mar 2000 22:41:00 -0000 [thread overview] Message-ID: <20000314064125.27088.qmail@sourceware.cygnus.com> (raw) CVSROOT: /cvs/guile Module name: guile Changes by: mdj@sourceware.cygnus.com 00/03/13 22:41:25 Modified files: guile-core/libguile: numbers.h Log message: * __scm.h eq.c, eval.c, gc.c, hc.h, gh_data, hash.c, numbers.c, numbers.h, objects.c, ramap.c, random.c, unif.c, unif.h: Extensive rewrite of handling of real and complex numbers. (SCM_FLOATS, SCM_SINGLES): These #ifdef conditionals have been removed along with the support for floats. (Float vectors are still supported.) * numbers.h (SCM_BIGSIGN): Sign moved to bit 16. (scm_makdbl): Deprecated. (SCM_NEWREAL, SCM_NEWCOMPLEX): New macros. (SCM_SINGP): Deprecated. (SCM_FLO): Removed. (SCM_INEXP, SCM_CPLXP): Deprecated. (SCM_INEXACTP, SCM_COMPLEXP): New macros. (SCM_COMPLEX_REAL, SCM_COMPLEX_IMAG): Renamed from SCM_REAL, SCM_IMAG (and now only valid for complex numbers). (SCM_REAL, SCM_IMAG): New, *deprecated*, selectors which work both for doubles and complex numbers. (SCM_REAL_VALUE): New selector for doubles. (scm_double_t, scm_complex_t): New types. (scm_dbl): Removed. * numbers.h (struct scm_dbl): changed to represent a double cell, with the number in the second half. (struct scm_cplx): new, represents a complex number as a triple cell.
next reply other threads:[~2000-03-13 22:41 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2000-03-13 22:41 mdj [this message] -- strict thread matches above, loose matches on Subject: below -- 2000-06-20 7:57 mdj 2000-06-19 3:04 mdj 2000-03-12 8:10 mdj
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20000314064125.27088.qmail@sourceware.cygnus.com \ --to=mdj@sourceware.cygnus.com \ --cc=guile-cvs@sourceware.cygnus.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: linkBe 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).