From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] grëp (rhymes with creep) and cptmp
Date: Mon, 30 Nov 2009 10:32:34 -0500 [thread overview]
Message-ID: <71b1e3b728efbd1b2a2ae2b5b4e2b1d0@coraid.com> (raw)
In-Reply-To: <d50d7d460911300710u697638cxf890f10283ee3a44@mail.gmail.com>
On Mon Nov 30 10:13:09 EST 2009, jason.catena@gmail.com wrote:
> > it turns out that doing regular expressions is difficult, since
> > it's not clear to me what [a-z] should match when unfolded.
>
> I have discovered a truly marvellous proof of this, which this memory
> is too narrow to contain.
>
> 209 runes in an unfolded a-Ǯ superclass later...
> 12498: signal: sys: segmentation violation
size isn't the real issue. the real issue is determining what
the ranges are for other than the base character. if a maps
to [aa'...] and z maps to [zz'...] it's not clear that [a'-z'] is a
sensible set. for example what does [e-f] map to? [e-f], clearly
but [ë-what?]
- erik
next prev parent reply other threads:[~2009-11-30 15:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<d50d7d460911292352j7cbcbc7erefa21b3b7f29f20a@mail.gmail.com>
2009-11-30 13:50 ` erik quanstrom
2009-11-30 14:48 ` roger peppe
2009-11-30 14:54 ` David Leimbach
2009-11-30 15:10 ` Jason Catena
2009-11-30 15:32 ` erik quanstrom [this message]
2009-11-30 15:54 ` Jorden Mauro
2009-11-30 16:00 ` erik quanstrom
2009-11-30 18:38 ` hiro
2009-11-30 19:43 ` Jorden Mauro
[not found] <<df49a7370911300648l5e243b12ncdf6de116d81afa9@mail.gmail.com>
2009-11-30 15:28 ` erik quanstrom
2009-11-30 16:38 ` roger peppe
2009-11-30 17:34 ` erik quanstrom
[not found] <<df49a7370911300326m3e3a6be1yc77e49a2b23a6da2@mail.gmail.com>
2009-11-30 14:06 ` erik quanstrom
[not found] <<d50d7d460911291101k7420eb0fna61f87646606e991@mail.gmail.com>
2009-11-30 4:29 ` erik quanstrom
2009-11-30 7:52 ` Jason Catena
2009-11-30 9:00 ` Eris Discordia
2009-11-29 19:01 Jason Catena
2009-11-30 4:51 ` Bruce Ellis
2009-11-30 11:26 ` roger peppe
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=71b1e3b728efbd1b2a2ae2b5b4e2b1d0@coraid.com \
--to=quanstro@coraid.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).