From: "Daniel Llorens del Río" <dll@jast.ch>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: bug in scm_arrray_handle_[srfi tag]_elements
Date: Tue, 12 Jan 2010 01:54:41 +0100 [thread overview]
Message-ID: <4855505A-8773-42E8-9AB1-7961E4013BA7@jast.ch> (raw)
In-Reply-To: <78A42C13-02F1-46A8-8E9C-B457687B0B5D@bluewin.ch>
On 12 Jan, 2010, at 0:49, Daniel Llorens del Río wrote:
> - return h-
> >elements; \
> + return ((const ctype*) h->elements) + h-
> >base; \
>
> I wrote it this way at first, too, but it doesn't work for c32/c64
> because ctype for those is float/double.
Or maybe hardcode the sizes in the macro call, it's not like they are
not already in two places.
Regards,
Daniel.
next prev parent reply other threads:[~2010-01-12 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0JCC00MW3LBEPQ@imap0.epfl.ch>
2010-01-11 18:49 ` bug in scm_arrray_handle_[srfi tag]_elements Daniel Llorens del Río
2010-01-11 23:22 ` Andy Wingo
2010-01-11 23:49 ` Daniel Llorens del Río
2010-01-12 0:54 ` Daniel Llorens del Río [this message]
2010-01-12 19:16 ` Andy Wingo
2010-01-12 19:48 ` Daniel Llorens del Río
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=4855505A-8773-42E8-9AB1-7961E4013BA7@jast.ch \
--to=dll@jast.ch \
--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).