From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from MTA-13-4.privateemail.com ([198.54.127.109]) by ewsd; Sat Sep 19 21:47:12 EDT 2020
Received: from mta-13.privateemail.com (localhost [127.0.0.1])
	by mta-13.privateemail.com (Postfix) with ESMTP id 2B30D80053
	for <9front@9front.org>; Sat, 19 Sep 2020 21:47:03 -0400 (EDT)
Received: from localhost (unknown [10.20.151.221])
	by mta-13.privateemail.com (Postfix) with ESMTPA id 7E7E28004B
	for <9front@9front.org>; Sun, 20 Sep 2020 01:47:02 +0000 (UTC)
Date: Sat, 19 Sep 2020 18:46:50 -0700
From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: Re: [9front] Upas: Complete date library conversion.
Message-ID: <20200920014650.GA15162@alice>
References: <4A5FA36F176704A4A945E80A3752EDBA@eigenstate.org>
 <355E3F0395C2F4AF941590B6BCBEBBA3@eigenstate.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <355E3F0395C2F4AF941590B6BCBEBBA3@eigenstate.org>
X-Virus-Scanned: ClamAV using ClamSMTP
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: anonymous basic polling HTTP over ORM base NoSQL database 

ori@eigenstate.org once said:
>  When parsing, this makes the following argument match fuzzily.
> +When formatting, this is ignored.
>  Fuzzy matching means that all formats are tried, from most to least specific.
>  For example,

The word "fuzzily" is a bit silly and this rule is not like
approximate string matching nor fuzzy logic.

How about:

	When parsing, all formats of the following argument are tried
	from most to least specific. For example, ?M will match January,
	Jan, 01, and 1, in that order. When formatting, this is ignored.

Cheers,
  Anthony