public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@ciaranm.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: GLEP 42?
Date: Thu, 12 Oct 2006 16:40:40 +0100	[thread overview]
Message-ID: <20061012164040.2ab6cad8@snowdrop.home> (raw)
In-Reply-To: <b38c6f4c0610120152w942f7f8q7194082f4ae944c8@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

On Thu, 12 Oct 2006 09:52:42 +0100 "Stuart Herbert"
<stuart.herbert@gmail.com> wrote:
| On 10/11/06, Stephen Bennett <spb@gentoo.org> wrote:
| > We also use space-delimited depend atoms everywhere else. It makes
| > no sense to break that when a comma works equally well.
| 
| I'm sorry, are you telling everyone that it's too difficult for you to
| write an ungreedy regex that also tests for the possibility of a list
| bounded by [ and ] being part of an atom?

We are not talking about us. We have access to a full parser that could
very easily be told to handle spaces, backspaces, tabs and anything
else you'd care to use. It can even go beyond the single lookahead
element that's required here.

No. We're talking about other developers and users who just want to do
a quick script without having to care about all that. You know, not
making design decisions that have no affect on the top 1% but that
screw over significant parts of the remainder just for the sake of
using a space over a comma.

-- 
Ciaran McCreesh
Mail                : ciaranm at ciaranm.org
Web                 : http://ciaranm.org/
as-needed is broken : http://ciaranm.org/show_post.pl?post_id=13


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-10-12 15:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-11 12:59 [gentoo-dev] GLEP 42? Stuart Herbert
2006-10-11 14:37 ` Ciaran McCreesh
2006-10-11 17:37 ` Zac Medico
2006-10-11 18:28   ` Donnie Berkholz
2006-10-11 18:52     ` Zac Medico
2006-10-11 21:04       ` Stuart Herbert
2006-10-11 18:36   ` Brian Jackson
2006-10-11 18:44     ` Ciaran McCreesh
2006-10-11 19:30       ` Chris Gianelloni
2006-10-11 19:46         ` Ciaran McCreesh
2006-10-11 19:52           ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2006-10-11 20:04             ` Brian Harring
2006-10-12 15:10               ` Jan Kundrát
2006-10-11 20:26             ` Ciaran McCreesh
2006-10-11 20:45               ` [gentoo-dev] " Michael Sterrett -Mr. Bones.-
2006-10-11 21:08               ` [gentoo-dev] " Stuart Herbert
2006-10-11 21:17                 ` Ciaran McCreesh
2006-10-12  9:00                   ` Stuart Herbert
2006-10-12 15:18                     ` Ciaran McCreesh
2006-10-12 12:24                   ` Natanael Copa
2006-10-12 15:18                     ` Ciaran McCreesh
2006-10-12 15:41                       ` [gentoo-dev] Paladius (was: GLEP 42?) Natanael Copa
2006-10-12 19:28                         ` Ciaran McCreesh
2006-10-12 16:03                     ` [gentoo-dev] Re: GLEP 42? Andrew Gaffney
2006-10-12 16:37                       ` Stephen Bennett
2006-10-11 22:34                 ` Stephen Bennett
2006-10-12  8:52                   ` Stuart Herbert
2006-10-12 10:57                     ` Stephen Bennett
2006-10-12 15:40                     ` Ciaran McCreesh [this message]
2006-10-11 19:11     ` [gentoo-dev] " Danny van Dyk

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=20061012164040.2ab6cad8@snowdrop.home \
    --to=ciaranm@ciaranm.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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