9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] command repetition in sam/acme
Date: Wed,  4 Mar 2009 14:31:38 +0100	[thread overview]
Message-ID: <5d375e920903040531j29fcbdc6na7b4e9a57563b708@mail.gmail.com> (raw)
In-Reply-To: <a560a5d00903040332g61739013ke948a8fdff1e9ca1@mail.gmail.com>

>From earlier in this thread:

"Sam and Acme use a simple, pure form of regular expressions. If they
had the counting operations, this would be a trivial task, but to add
them would open the door to the enormous, ill-conceived complexity of
(no longer) regular expressions as the open source community thinks of
them."

So, if you want counting, you can always write a patch, who knows, it
might even be accepted.

But I think that anyone not under the influence of psychedelic
substances that has suffered PCR, will agree we don't want to move in
that direction, and even if small, counting is a step in that
direction.

I personally rarely have use for it, and when I do, it is trivial to
write a script to generate the desired regexp, and I'm eternally
grateful for being free from Perl-induced psychosis.

uriel

On Wed, Mar 4, 2009 at 12:32 PM, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
> 2009/3/4 Rob Pike <robpike@gmail.com>:
>> Not all the features adapt as easily.
>>
>> -rob
>
> By counted repetittion I've  always meant just the mentioned, i.e.
> {n}
> {n,}
> {,m}
> {n,m}
> .
> What feature do you have on mind?
>
> Thanks
> Ruda
>
>



  reply	other threads:[~2009-03-04 13:31 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-03 12:07 Rudolf Sykora
2009-03-03 12:49 ` Steve Simon
2009-03-03 13:53   ` Rudolf Sykora
2009-03-03 15:40     ` roger peppe
2009-03-03 15:58       ` yy
2009-03-03 16:25         ` Rudolf Sykora
2009-03-03 15:58       ` Uriel
2009-03-03 15:59         ` Uriel
2009-03-03 14:15 ` John Stalker
2009-03-03 14:23   ` Rudolf Sykora
2009-03-03 16:09 ` Russ Cox
2009-03-03 16:31   ` roger peppe
2009-03-03 17:16     ` Uriel
2009-03-03 18:50       ` Rudolf Sykora
2009-03-03 16:39   ` Rudolf Sykora
2009-03-03 20:30   ` Arvindh Rajesh Tamilmani
2009-03-03 22:13     ` ron minnich
2009-03-03 23:19       ` J.R. Mauro
2009-03-03 23:37       ` Anthony Sorace
2009-03-04  0:31         ` Rob Pike
2009-03-04  0:44           ` J.R. Mauro
2009-03-04  0:56             ` Rob Pike
2009-03-04  1:51               ` J.R. Mauro
2009-03-04  2:15                 ` Rob Pike
2009-03-04  4:59                   ` J.R. Mauro
2009-03-04  9:41           ` Rudolf Sykora
2009-03-04  9:52             ` Rob Pike
2009-03-04 11:32               ` Rudolf Sykora
2009-03-04 13:31                 ` Uriel [this message]
2009-03-04 13:41                   ` Rudolf Sykora
2009-03-04 16:35                   ` John Stalker
2009-03-04 16:56                     ` ron minnich
2009-03-04 13:37             ` erik quanstrom
2009-03-04 14:14               ` Rudolf Sykora
2009-03-04 14:37                 ` erik quanstrom
2009-03-04 14:59                   ` Rudolf Sykora
2009-03-04 16:34                 ` Steve Simon
2009-03-04 17:03             ` Russ Cox

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=5d375e920903040531j29fcbdc6na7b4e9a57563b708@mail.gmail.com \
    --to=uriel99@gmail.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).