From: "Luis Souto Graña" <luissoutobueu@gmail.com>
To: Daniel Llorens <daniel.llorens@bluewin.ch>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Function set-gl-vertex-array in Guile-opengl
Date: Sat, 26 Jan 2019 20:00:28 +0100 [thread overview]
Message-ID: <CA+0Zd=_apQQrVExGhODhqcJtGTM_U8ODhgf9Okhg6zNwEEKOSA@mail.gmail.com> (raw)
In-Reply-To: <0BE53CE6-E3F3-4D2B-AB56-DAEE9A87F114@bluewin.ch>
Thank a lot, now at least I have clear f32vector structure.
El sáb., 26 ene. 2019 a las 16:39, Daniel Llorens (<
daniel.llorens@bluewin.ch>) escribió:
>
>
> > On 26 Jan 2019, at 17:05, Luis Souto Graña <luissoutobueu@gmail.com>
> wrote:
> >
> > The structure of my byvector is:
> >
> > 30.0(float) --- IEE754 converter --> 0x41F00000 (hexadecimal) ---
> little endian ---> 0000F041 --- hexadecimal to decimal converter ---> 00 00
> 240 65
> >
> > But I didn't notice and there's a lot of zeros before the next 00 00 240
> 65.
> >
> > I have to study what is the structure of a f32vector in Guile. I don't
> know it.
>
> The storage of an f32vector is exactly the same as if you declared float
> a[n] in C, one float after another, each taking 4 bytes. Endianness doesn't
> matter if you are producing and consuming the floats on the same machine.
>
> The source data is floats, OpenGL takes floats, you don't need to deal
> with bytes.
>
>
next prev parent reply other threads:[~2019-01-26 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.136.1548435627.3559.guile-user@gnu.org>
2019-01-25 18:25 ` Function set-gl-vertex-array in Guile-opengl Daniel Llorens
2019-01-26 1:33 ` Luis Souto Graña
2019-01-26 12:52 ` Daniel Llorens
2019-01-26 12:58 ` Daniel Llorens
2019-01-26 16:05 ` Luis Souto Graña
2019-01-26 15:39 ` Daniel Llorens
2019-01-26 19:00 ` Luis Souto Graña [this message]
2019-01-28 13:30 ` Luis Souto Graña
2019-01-31 11:14 ` Luis Souto Graña
2019-02-09 18:59 ` Luis Souto Graña
2019-01-25 10:36 Luis Souto Graña
2019-01-26 10:33 ` Catonano
2019-01-26 16:02 ` Luis Souto Graña
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+0Zd=_apQQrVExGhODhqcJtGTM_U8ODhgf9Okhg6zNwEEKOSA@mail.gmail.com' \
--to=luissoutobueu@gmail.com \
--cc=daniel.llorens@bluewin.ch \
--cc=guile-user@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).