From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: open-{gnutls,network}-stream backwards compatibility Date: Wed, 02 Jan 2019 21:49:53 +0200 Message-ID: <83wonm3km6.fsf@gnu.org> References: <831s5v3s9w.fsf@gnu.org> <83y3823oap.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1546458490 4993 195.159.176.226 (2 Jan 2019 19:48:10 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 2 Jan 2019 19:48:10 +0000 (UTC) Cc: emacs-devel@gnu.org To: Ted Zlatanov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jan 02 20:48:06 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1gemUo-0001DA-8R for ged-emacs-devel@m.gmane.org; Wed, 02 Jan 2019 20:48:06 +0100 Original-Received: from localhost ([127.0.0.1]:47094 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gemWv-0007rY-2Q for ged-emacs-devel@m.gmane.org; Wed, 02 Jan 2019 14:50:17 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:59841) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gemWm-0007p9-Nu for emacs-devel@gnu.org; Wed, 02 Jan 2019 14:50:09 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gemWh-0000Yg-Jp for emacs-devel@gnu.org; Wed, 02 Jan 2019 14:50:07 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:57382) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gemWf-0000XV-Mq; Wed, 02 Jan 2019 14:50:01 -0500 Original-Received: from [176.228.60.248] (port=4917 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gemWd-00042S-M9; Wed, 02 Jan 2019 14:50:00 -0500 In-reply-to: (message from Ted Zlatanov on Wed, 02 Jan 2019 19:18:26 +0000) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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:232102 Archived-At: > From: Ted Zlatanov > Cc: emacs-devel@gnu.org > Date: Wed, 02 Jan 2019 19:18:26 +0000 > > EZ> If we can make the change backward-compatible, there's no reason to > EZ> deprecate it. > > As the author I appreciate your authorship, but in Emacs, once we release our code, we no longer have much of control on it. It's out in the open. > I think there is: the function is used in one place and > doesn't fit the use cases well. All the existing usage goes through > `open-network-stream'. So it's a layer of indirection with one user, > that removes API features in a way that's hard to work around. I think > it's better to remove the source of the problem than to patch it. I don't think I understand why this justifies deprecation of an API. Deprecation is a nuisance: it chatters when you compile code, it nags. We need a seriously good reason to impose that on unsuspecting users.