From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: encode-time vs decode-time Date: Sat, 17 Aug 2019 13:51:09 -0700 Message-ID: <87r25jms76.fsf@mouse.gnus.org> References: <502b23f8-58ed-38ff-ae50-fae391129a10@cs.ucla.edu> <87v9viuivo.fsf@mouse.gnus.org> <87o9119p8i.fsf@mouse.gnus.org> <47b9fb2f-3ae6-14d3-5f68-7dda13d92e5d@cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="131763"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Andy Moreton , emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Aug 17 22:51:29 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 1hz5fc-000Y8S-Py for ged-emacs-devel@m.gmane.org; Sat, 17 Aug 2019 22:51:28 +0200 Original-Received: from localhost ([::1]:37916 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hz5fb-0002Bs-62 for ged-emacs-devel@m.gmane.org; Sat, 17 Aug 2019 16:51:27 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35093) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hz5fU-0002AK-6I for emacs-devel@gnu.org; Sat, 17 Aug 2019 16:51:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hz5fR-0001D8-Kj for emacs-devel@gnu.org; Sat, 17 Aug 2019 16:51:20 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:49604) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hz5fP-0001CC-UF for emacs-devel@gnu.org; Sat, 17 Aug 2019 16:51:16 -0400 Original-Received: from [50.225.213.182] (helo=sandy) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hz5fM-0003bP-3J; Sat, 17 Aug 2019 22:51:14 +0200 In-Reply-To: <47b9fb2f-3ae6-14d3-5f68-7dda13d92e5d@cs.ucla.edu> (Paul Eggert's message of "Sat, 17 Aug 2019 02:25:48 -0700") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.231.51 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:239421 Archived-At: Paul Eggert writes: > Lars Ingebrigtsen wrote: >> I thought it would be good to introduce a new function, say >> `get-current-time', that could have our new signature. We'd then >> deprecate `current-time' > > It's not just current-time; it's also encode-time, file-attributes, > directory-files-and-attributes, visited-file-modtime, > current-idle-time, process-attributes, get-internal-run-time, > make-frame-visible, time-add, time-subtract, and no doubt other > primitives written in C that make Lisp timestamps visible to user > code, along with the many functions written in Lisp (e.g., > time-since) that call these primitives and give Lisp timestamps to > users. Yeah, that's true, so introducing a new function here wouldn't help. But I think that having these functions return something that doesn't have the second spec in car/cadr is going to break a lot of people's out-of-tree code. So my feeling is that your plan isn't feasible, and we'll have to live with these functions returning encoded time on the current form forever. Which I think is OK, although your new format is more elegant. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no