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 17:20:06 +0200 [thread overview]
Message-ID: <20130502152006.GA490@polynum.com> (raw)
In-Reply-To: <CAOCRf5Wu6+3t5MzZ28SjD6_oNBtpXRFNpjny0T=WHCm_rjcRew@mail.gmail.com>
On Thu, May 02, 2013 at 05:02:45PM +0200, Bence Fábián wrote:
> you want to change default behaviour and make the usual usecase special?
>
For the moment, I don't want to change anything, I'm trying to be
convinced where the border has to be: "characters" (for me user
level) on the one side, octets strings on the other system and
library side (on a distributed system, it makes sense that filenames,
being userlevel nicknames be UTF-8---supposed to be UTF-8 without any
per filename codepage or whatever).
The usual behavior could perfectly be the same (the
leading "L" was just an exemple; it could be reversed; and octets
matching could simply be called by new functions---new names---, the
historical ones calling these new character agnostic ones). The
problem is not there. The problem is: are regexp only useful with
"text" implying "characters", or more widely useful? My feeling is
that they are more generally useful.
--
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 15:20 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
2013-05-02 15:02 ` Bence Fábián
2013-05-02 15:20 ` tlaronde [this message]
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=20130502152006.GA490@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).