From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: encode-time vs decode-time Date: Sat, 17 Aug 2019 15:53:13 -0700 Organization: UCLA Computer Science Department Message-ID: <88b57699-fbdb-bd43-6627-f7491b834955@cs.ucla.edu> References: <502b23f8-58ed-38ff-ae50-fae391129a10@cs.ucla.edu> <87v9viuivo.fsf@mouse.gnus.org> <83blx2cr2o.fsf@gnu.org> <8336iecfvr.fsf@gnu.org> <68d24d6a-d427-baef-27e9-ea1cbbd64c18@cs.ucla.edu> <87sgqd9plt.fsf@mouse.gnus.org> <89271843-6d47-8315-ed9a-540657298985@cs.ucla.edu> <87v9uvmsfa.fsf@mouse.gnus.org> <83af2f70-480b-6e5f-06a5-876224e2b715@cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="70040"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 Cc: Lars Ingebrigtsen , andrewjmoreton@gmail.com, Eli Zaretskii , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 18 00:53:56 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hz7a8-000I7W-IQ for ged-emacs-devel@m.gmane.org; Sun, 18 Aug 2019 00:53:56 +0200 Original-Received: from localhost ([::1]:38432 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hz7a7-0004PI-Em for ged-emacs-devel@m.gmane.org; Sat, 17 Aug 2019 18:53:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50090) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hz7ZX-0004M8-83 for emacs-devel@gnu.org; Sat, 17 Aug 2019 18:53:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hz7ZW-000799-5y for emacs-devel@gnu.org; Sat, 17 Aug 2019 18:53:19 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:51064) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hz7ZU-00077Z-Hq; Sat, 17 Aug 2019 18:53:16 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 12E8B161906; Sat, 17 Aug 2019 15:53:15 -0700 (PDT) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id HXMPGWQGec-Y; Sat, 17 Aug 2019 15:53:14 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 472FD162711; Sat, 17 Aug 2019 15:53:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id K9riUdPSgMIU; Sat, 17 Aug 2019 15:53:14 -0700 (PDT) Original-Received: from [192.168.1.9] (cpe-23-242-74-103.socal.res.rr.com [23.242.74.103]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id E8B8C161906; Sat, 17 Aug 2019 15:53:13 -0700 (PDT) In-Reply-To: Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:239426 Archived-At: Stefan Monnier wrote: > I think neither "broken down time" nor "tm" are significantly less > bad than "decoded-time", so I don't think it's worth changing the term > we've been using. I'm starting to come around to the same feeling. > So maybe we should stop documenting "decoded time" objects as being of > the form (SEC MINUTE HOUR DAY MONTH YEAR DOW DST UTCOFF SUBSEC), but > instead say that it's a `decoded-time` object on which you can use > the `decoded-time-*` accessors (and provide a corresponding pcase pattern > to replace the `(,sec ,minute ...) one). That sounds like a reasonable way to move forward. I'm not a pcase expert. How would one go about doing the pcase stuff? That is, how does one provide a pattern so that code like (pcase time ((decoded-time :year y :month m) (some-expr-involving y & m))) can extract the year and month components Y and M from the broken-down time TIME that was created via (make-decoded-time :year y :month m)? Is there an example of doing this sort of thing somewhere?