From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Thu,  2 May 2013 16:13:30 -0400
To: 9fans@9fans.net
Message-ID: <9caf3620f869ab9d4c386d5446ebbbf2@coraid.com>
In-Reply-To: <20130502193952.GA662@polynum.com>
References: <20130502123825.GA1975@polynum.com>
	<20130502150829.GA435@polynum.com>
	<d8aecdc9b2e88ca91a3730e70e1fef1c@ladd.quanstro.net>
	<2292951.aK3zqF2TmN@blitz> <20130502190415.GB412@polynum.com>
	<4a14b1c442389a52b89aad17acbb615e@ladd.quanstro.net>
	<20130502193952.GA662@polynum.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Octets regexp
Topicbox-Message-UUID: 51db138e-ead8-11e9-9d60-3106f5b1d025

> Indeed, if the regexp is an ASCII representation matching xd outputs
> there is not _this_ problem. But this is limited regexp, since one can
> not use "character" ranges (it depends on the size); not '.'; because

now you're at both ends.  the whole reason for this approach is to
match bytes that aren't valid runes.  so why complain that it does
what you want?

- erik