From: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: python on guile, bytevectors
Date: Tue, 23 Jul 2019 13:14:21 +0200 [thread overview]
Message-ID: <CAGua6m0DBXQF5O=y5nxhgQNCPTXfeux1hXhX=3CLOXRVc5WbMA@mail.gmail.com> (raw)
Hi,
Sometimes people complain about guile string handling, that it is heavy and
that it does some interpretation of the characters. The answer is that you
should use bytevecors and then you hear that bytevectors containing char
codes does not have all the fetaures string has.
If you use python-on-guile you do have the python bytevector interface and
almost all string functions are available. Furthermore I landed yesterday
bytevector support for the python regexp module so that you can now
intyerpret bytevectors with regexpes as well (use the ASCII flag).
To note, I use a PEG parser to manage the regular expressions and it's
slow. You can use the stis-paser directly and get some speedup using cuts
however. This to enable a maintainable and quick implementation. Any patch
that speeds the regexp engine is most welcome.
Happy hacking!
reply other threads:[~2019-07-23 11:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGua6m0DBXQF5O=y5nxhgQNCPTXfeux1hXhX=3CLOXRVc5WbMA@mail.gmail.com' \
--to=stefan.itampe@gmail.com \
--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).