--- /dev/null
+Return-Path: <jani@nikula.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by olra.theworths.org (Postfix) with ESMTP id 621DC431FAF\r
+ for <notmuch@notmuchmail.org>; Mon, 17 Sep 2012 08:54:32 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+ tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+ by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id 3I74WdyBVlQI for <notmuch@notmuchmail.org>;\r
+ Mon, 17 Sep 2012 08:54:31 -0700 (PDT)\r
+Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com\r
+ [209.85.217.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+ (No client certificate requested)\r
+ by olra.theworths.org (Postfix) with ESMTPS id A1281431FAE\r
+ for <notmuch@notmuchmail.org>; Mon, 17 Sep 2012 08:54:31 -0700 (PDT)\r
+Received: by lbbgk1 with SMTP id gk1so4675913lbb.26\r
+ for <notmuch@notmuchmail.org>; Mon, 17 Sep 2012 08:54:30 -0700 (PDT)\r
+X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;\r
+ d=google.com; s=20120113;\r
+ h=from:to:subject:in-reply-to:references:user-agent:date:message-id\r
+ :mime-version:content-type:content-transfer-encoding\r
+ :x-gm-message-state;\r
+ bh=uR+CqFNrJVDPEG8kHiGmPHHZLW0aii0j00gulon9zQo=;\r
+ b=eh+ArTf/JVlbNH/4sGW/F3id6Tj4oiPtyskce68GxVWBLS3AAiMLR/plcps9J72IaG\r
+ E/I3NqjB2MFVeYE0N9W3T7eLF0WW+x8aHTznmootDn228ltEcEhXoO0HBLoXRLTz5QNI\r
+ q7jRfE/HcydpJld955AzibPtUwTtwqX9+9mlHbpBxlLnpJhsxawRpL/Y6GzOY8+INskA\r
+ QpC424zT1JDp1btkubbV0Wt/T3zi7xkKCf5e3/GVIncX33irc5ijgweGMgJdUHwGRUIK\r
+ hC9uMTPocKsFzz0v0Hz8G/OiE6uf7uc4p05B5UZV/y1MOad3aMISRQ/HpuEWDOfTsQvG\r
+ JXEQ==\r
+Received: by 10.112.24.233 with SMTP id x9mr3461893lbf.76.1347897270076;\r
+ Mon, 17 Sep 2012 08:54:30 -0700 (PDT)\r
+Received: from localhost (dsl-hkibrasgw4-fe51df00-27.dhcp.inet.fi.\r
+ [80.223.81.27])\r
+ by mx.google.com with ESMTPS id gt19sm3056351lab.8.2012.09.17.08.54.26\r
+ (version=SSLv3 cipher=OTHER); Mon, 17 Sep 2012 08:54:27 -0700 (PDT)\r
+From: Jani Nikula <jani@nikula.org>\r
+To: Michal Nazarewicz <mina86@mina86.com>, notmuch@notmuchmail.org,\r
+ David Bremner <david@tethera.net>\r
+Subject: Re: [PATCH v3 2/9] parse-time-string: add a date/time parser to\r
+ notmuch\r
+In-Reply-To: <xa1tpq5kzqi8.fsf@mina86.com>\r
+References: <cover.1347484177.git.jani@nikula.org>\r
+ <89741ec9a9687fca8b30aa1a4877392d355dd3ce.1347484177.git.jani@nikula.org>\r
+ <xa1tvcfidvpe.fsf@mina86.com> <878vcerurc.fsf@nikula.org>\r
+ <xa1tpq5kzqi8.fsf@mina86.com>\r
+User-Agent: Notmuch/0.14+29~g77c762c (http://notmuchmail.org) Emacs/23.3.1\r
+ (i686-pc-linux-gnu)\r
+Date: Mon, 17 Sep 2012 18:54:23 +0300\r
+Message-ID: <87wqzsfxw0.fsf@nikula.org>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=utf-8\r
+Content-Transfer-Encoding: quoted-printable\r
+X-Gm-Message-State:\r
+ ALoCoQmr/KIibUSRlVqTXYkNPc+1DF46w3OMiF5AmOGJR+7A7+0tcfViMEPyPuRlpmGFoAbeCW8E\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Mon, 17 Sep 2012 15:54:32 -0000\r
+\r
+On Mon, 17 Sep 2012, Michal Nazarewicz <mina86@mina86.com> wrote:\r
+> Bison can do a lot of weird stuff including modifying how lexer\r
+> interpretes tokens even while parsing given grammar rule.\r
+\r
+I'll just have to take your word for it.\r
+\r
+> I'm sorry. I sometime tend to go into extremes with my statements, so\r
+> yes, the =E2=80=9Ctotally unreadable=E2=80=9D was a over statement on my =\r
+part.\r
+\r
+Okay.\r
+\r
+> My point was however that parsing is a solved problem, and for\r
+> non-trivial parsers one needs to ask herself whether it's worth trying\r
+> to implement the logic, or maybe using a parser generator is just\r
+> simpler.\r
+\r
+If there's something non-trivial about parsing dates and times, it's not\r
+the actual parsing. It's not a well defined grammar. And judging by the\r
+number of date parsers available that would be suitable for notmuch, as\r
+a library, parsing dates is not a solved problem.\r
+\r
+> And in this particular case, my feeling is that bison is easier to read\r
+> and modify.\r
+>\r
+> To add some merit to my statement, I attach a bison parser.\r
+\r
+And there are people out there writing compilers without a parser\r
+generator... [1] But using a parser generator or not is really not the\r
+issue here, whichever has more merit. The issue is adding suitable date\r
+range queries to notmuch.\r
+\r
+I have submitted patches to do just that. I don't intend to rework them\r
+much anymore. It's always interesting in the beginning, but adding the\r
+last bits of polish and fixing the corner cases can get a bit\r
+tedious. You know how it is. At this point, I'd just like to have the\r
+feature in notmuch.\r
+\r
+So I don't know. I guess I want to say, please submit patches to add the\r
+feature, with polish, and not to prove a point, damnit. I have no issues\r
+with promoting whichever approach is the best in the end.\r
+\r
+\r
+BR,\r
+Jani.\r
+\r
+\r
+[1] http://git.kernel.org/?p=3Ddevel/sparse/sparse.git\r
projects / notmuch-archives.git / commitdiff