From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Octets regexp
Date: Thu, 2 May 2013 16:51:39 +0200 [thread overview]
Message-ID: <20130502145139.GB438@polynum.com> (raw)
In-Reply-To: <257b5f.1257db09.089d.mx@tumtum.plumbweb.net>
On Thu, May 02, 2013 at 09:43:10AM -0400, Tristan wrote:
> > And after some thought, I don't see an obvious reason why the regexp
> > could not be used with bytes strings (so UTF-8 is OK) without trying to
> > match runes (since not every bytes string is a correct UTF-8 sequence).
>
> with octet based regexps, [Þþ] doesn't match þ, but 0xc3, 0xbe and 0x9e
> independantly.
>
Regexp knows subexpressions. So it could be achieved, and one could even
have the present functions be higher level ones, calling more basic ones
dealing with bytes (a rune specified by an UTF-8 sequence being replaced
by a subexpression) or even dealing with various sizes of element
(character; but one fixed size for the processing).
Or even a specification à la C: by adding a leading 'L' meaning:
treat the string as UTF-8 that is masters runes. And if not, leave
it alone.
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2013-05-02 14:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 12:38 tlaronde
2013-05-02 12:48 ` erik quanstrom
2013-05-02 13:25 ` tlaronde
2013-05-02 13:43 ` Tristan
2013-05-02 14:19 ` Tristan
2013-05-02 14:51 ` tlaronde [this message]
2013-05-02 15:02 ` Bence Fábián
2013-05-02 15:20 ` tlaronde
2013-05-02 15:27 ` erik quanstrom
2013-05-02 15:10 ` Kurt H Maier
2013-05-02 15:21 ` tlaronde
2013-05-02 13:44 ` erik quanstrom
2013-05-02 14:43 ` tlaronde
2013-05-02 14:58 ` a
2013-05-02 15:08 ` tlaronde
2013-05-02 15:19 ` erik quanstrom
2013-05-02 15:31 ` tlaronde
2013-05-02 16:53 ` erik quanstrom
2013-05-02 18:59 ` tlaronde
2013-05-02 18:45 ` dexen deVries
2013-05-02 19:04 ` tlaronde
2013-05-02 19:22 ` erik quanstrom
2013-05-02 19:39 ` tlaronde
2013-05-02 20:13 ` erik quanstrom
2013-05-02 20:17 ` 9p-st
2013-05-03 11:16 ` tlaronde
2013-05-03 13:15 ` Tristan
2013-05-03 16:33 ` tlaronde
2013-05-02 16:16 ` tlaronde
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130502145139.GB438@polynum.com \
--to=tlaronde@polynum.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).