From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@yhbt.net>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00
	shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id DE72F1F5AE;
	Thu,  9 Jul 2020 22:57:46 +0000 (UTC)
Date: Thu, 9 Jul 2020 22:57:46 +0000
From: Eric Wong <e@yhbt.net>
To: Josh Natanson <josh@natanson.net>
Cc: clogger-public@yhbt.net
Subject: Re: Clogger request_time formatting
Message-ID: <20200709225746.GB23508@dcvr>
References: <CAPdx2szjqUuFjUtrgoeXXwmz0HzfdnWe+2h2Sp_ywDkTDVL0-g@mail.gmail.com>
 <20200709202820.GA30471@dcvr>
 <CAPdx2syEU5WLBx9PezfQ6nFdpnouscXwnm-bg0+t5ERi7EPnJg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAPdx2syEU5WLBx9PezfQ6nFdpnouscXwnm-bg0+t5ERi7EPnJg@mail.gmail.com>
List-Id: <clogger-public.yhbt.net>

Josh Natanson <josh@natanson.net> wrote:
> > Or is the "." component not desirable?
> 
> Exactly, my requirements require actual microseconds, not just that precision.

OK.

Btw, please keep clogger-public@yhbt.net Cc-ed for public
archival purposes.   Most people reading these emails are not
subscribed via SMTP, but rather via NNTP/Atom/HTML/IMAP/git;
so we have no idea how many people read this inbox.

> > I suppose something like $request_time{6,0} could be added
> > (Multiply by 10**6, PRECISION=0)
> 
> I think that would do the trick, but probably wouldn't be backwards
> compatible with people already using $request_time{6,0}?  Maybe a
> second optional {}, like $request_time{0}{6}?  Or a separate token
> altogether, $request_time_micro, but that could be less flexible.

There shouldn't be any incompatibility, since it currently
accepts only matching /\A\$request_time\{(\d+)\}\z/.  Thus "{6,0}"
is rejected by current versions.