From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp's future Date: Sat, 11 Oct 2014 10:18:49 +0300 Message-ID: <83zjd3846e.fsf@gnu.org> References: <54193A70.9020901@member.fsf.org> <87wq8pwjen.fsf@uwakimon.sk.tsukuba.ac.jp> <837g0ptnlj.fsf@gnu.org> <87r3yxwdr6.fsf@uwakimon.sk.tsukuba.ac.jp> <87tx3tmi3t.fsf@fencepost.gnu.org> <834mvttgsf.fsf@gnu.org> <87lhp5m99w.fsf@fencepost.gnu.org> <87h9ztm5oa.fsf@fencepost.gnu.org> <87d2ahm3nw.fsf@fencepost.gnu.org> <871tqneyvl.fsf@netris.org> <87d2a54t1m.fsf@yeeloong.lan> <83lhotme1e.fsf@gnu.org> <871tql17uw.fsf@yeeloong.lan> <838uktm9gw.fsf@gnu.org> <87h9zgarvp.fsf@fencepost.gnu.org> <83y4srjaot.fsf@gnu.org> <83r3yhiu8c.fsf@gnu.org> <83siiw9c6t.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1413011969 30340 80.91.229.3 (11 Oct 2014 07:19:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 11 Oct 2014 07:19:29 +0000 (UTC) Cc: dak@gnu.org, mhw@netris.org, dmantipov@yandex.ru, emacs-devel@gnu.org, handa@gnu.org, monnier@iro.umontreal.ca, stephen@xemacs.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 11 09:19:21 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XcqxU-00076K-LP for ged-emacs-devel@m.gmane.org; Sat, 11 Oct 2014 09:19:20 +0200 Original-Received: from localhost ([::1]:53222 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcqxU-00088V-5U for ged-emacs-devel@m.gmane.org; Sat, 11 Oct 2014 03:19:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35151) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcqxN-00088H-CZ for emacs-devel@gnu.org; Sat, 11 Oct 2014 03:19:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XcqxI-0003zy-RA for emacs-devel@gnu.org; Sat, 11 Oct 2014 03:19:13 -0400 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:51808) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XcqxD-0003ya-V7; Sat, 11 Oct 2014 03:19:04 -0400 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0ND900400QBT5H00@a-mtaout22.012.net.il>; Sat, 11 Oct 2014 10:19:01 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0ND90040RQZP1C40@a-mtaout22.012.net.il>; Sat, 11 Oct 2014 10:19:01 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:175249 Archived-At: > Date: Fri, 10 Oct 2014 21:15:26 -0400 > From: Richard Stallman > CC: dak@gnu.org, mhw@netris.org, dmantipov@yandex.ru, > emacs-devel@gnu.org, handa@gnu.org, monnier@iro.umontreal.ca, > stephen@xemacs.org > > > They don't HAVE to be treated the same. We are talking about changes, > > here. > > They will be very deep and invasive changes, because currently the > encoding/decoding routines don't know the purpose of the stuff they > are producing. > > No, it's just a matter of setting some parameter to specify a particular > decision in decoding or encoding behavior. Specify, and then drag it all the way down the encoding/decoding machinery. > > But changes may not be needed. All operations that do encoding or > > decoding allow explicit specification of the coding system. > > Of course, they do. But the issue at hand is precisely whether it is > the application's responsibility to explicitly specify conversions > that will be strict wrt invalid byte sequences, or should Emacs do > that by default. > > Yes. > > It will be easy to specify one or the other, so why not make the default > be strict, except in the primitives that operate on files? Because I believe this will annoy users and cause a lot of complaining.