From: Luiji Maryo <luiji@users.sourceforge.net>
To: Guile Mailing List <guile-user@gnu.org>
Subject: Some I/O Questions
Date: Thu, 9 Feb 2012 22:50:05 -0500 [thread overview]
Message-ID: <CAAXjPiR2qHAeL8sTHWE+0b8agtDLwG+8g++WreyacPtR_bkcmA@mail.gmail.com> (raw)
Hello,
I have some questions regarding Guile I/O and byte order.
1. Is there an I/O function for reading a fixed set of bytes into a
buffer, i.e. if I wanted to read a 56-byte string from a binary
archive?
2. Is there a way to specifically read a 8/16/32/64-bit string from a file/port?
3. Is there a built-in function for converting between byte orders
(i.e. BSD-style htobe32 and such) or must I implement them myself?
4. Is writing an archive manager using Guile for implementing archive
formats a bad idea to start with?
Thank you for your time,
- LM <luiji@users.sourceforge.net>
http://entertainingsoftware.com/
next reply other threads:[~2012-02-10 3:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 3:50 Luiji Maryo [this message]
2012-02-10 20:05 ` Some I/O Questions Ian Price
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=CAAXjPiR2qHAeL8sTHWE+0b8agtDLwG+8g++WreyacPtR_bkcmA@mail.gmail.com \
--to=luiji@users.sourceforge.net \
--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).