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 13:56:57 -0700 Organization: UCLA Computer Science Department Message-ID: <83af2f70-480b-6e5f-06a5-876224e2b715@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> 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="153731"; 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: Eli Zaretskii , andrewjmoreton@gmail.com, emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 17 22:57:14 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 1hz5lB-000dtJ-IX for ged-emacs-devel@m.gmane.org; Sat, 17 Aug 2019 22:57:13 +0200 Original-Received: from localhost ([::1]:37930 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hz5l9-0003Wm-TA for ged-emacs-devel@m.gmane.org; Sat, 17 Aug 2019 16:57:11 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35554) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hz5l3-0003WS-3e for emacs-devel@gnu.org; Sat, 17 Aug 2019 16:57:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hz5l2-0004Sq-1D for emacs-devel@gnu.org; Sat, 17 Aug 2019 16:57:04 -0400 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:42222) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hz5l0-0004QL-3R; Sat, 17 Aug 2019 16:57:02 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 346DF1626F2; Sat, 17 Aug 2019 13:57:00 -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 aIm-KB1UpAMZ; Sat, 17 Aug 2019 13:56:59 -0700 (PDT) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 416B9162711; Sat, 17 Aug 2019 13:56:59 -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 nnZpmEyRXLpo; Sat, 17 Aug 2019 13:56:58 -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 B48D61626F2; Sat, 17 Aug 2019 13:56:58 -0700 (PDT) In-Reply-To: <87v9uvmsfa.fsf@mouse.gnus.org> 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:239422 Archived-At: Lars Ingebrigtsen wrote: > "Broken-down time" sounds OK to me, although there may be some > confusion: Some may assume that it's a faulty time or something. Yes, I'm not a big fan of "broken-down time" either. Its main advantages are (1) we can't think of a better name and (2) it's used elsewhere in GNU and POSIX. > And when we get to the accessor names, it perhaps gets even more > potentially confusing: > > (broken-down-seconds time) > (broken-down-zone time) > > Hm... Perhaps not ideal? The POSIX identifier for broken-down time is 'tm', as in 'struct tm'. We could steal that identifier too, e.g., (tm-seconds time), (tm-zone time), etc. Again, not ideal, but perhaps better than (broken-down-seconds time). If the prefix 'tm-' is too short, we could expand it to 'time-tm-' or something like that.