From: John Cowan <cowan@ccil.org>
To: divoplade <d@divoplade.fr>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: What is the point of bytevectors?
Date: Sat, 12 Sep 2020 12:48:50 -0400 [thread overview]
Message-ID: <CAD2gp_QgA6yDy0uEdaJeYAJR5yV1OESaf6MZGzpVG3eaakzStA@mail.gmail.com> (raw)
In-Reply-To: <663bcc3f7ca042bfd727cbcecb0dccfcde43aec8.camel@divoplade.fr>
On Sat, Sep 12, 2020 at 3:51 AM divoplade <d@divoplade.fr> wrote:
> From the scheme side, however:
> 1. The bytevector library needs to be imported;
>
If a single line is a serious overhead, then your program is tiny and you
can do whatever you want: it will be obvious to whoever maintains the
program next (including you).
> 2. The function names have way more characters to type;
>
Use an autocompleting editor such as Emacs.
> 3. The bytevector library is missing a lot of text functions (like
> join, split, trim, pad, searching...).
>
That is indeed an issue. Fortunately SRFI 207, though not yet final, comes
to your rescue. You can't get the spiffy syntax described at <
https://srfi.schemers.org/srfi-207/srfi-207.html> unless you modify the
Guile reader, but the procedures documented there can be found at <
https://github.com/Zipheir/bytestrings>.
John Cowan http://vrici.lojban.org/~cowan cowan@ccil.org
It was impossible to inveigle
Georg Wilhelm Friedrich Hegel
Into offering the slightest apology
For his Phenomenology. --W. H. Auden, from "People"
(1953)
next prev parent reply other threads:[~2020-09-12 16:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 7:49 What is the point of bytevectors? divoplade
2020-09-12 10:35 ` Linus Björnstam
2020-09-12 16:48 ` John Cowan [this message]
2020-09-12 17:14 ` divoplade
2020-09-12 17:24 ` John Cowan
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=CAD2gp_QgA6yDy0uEdaJeYAJR5yV1OESaf6MZGzpVG3eaakzStA@mail.gmail.com \
--to=cowan@ccil.org \
--cc=d@divoplade.fr \
--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).