From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Inconsistencies regarding nil coding-system Date: Tue, 14 Dec 2010 10:41:18 +0900 Message-ID: References: <83aakcvbtp.fsf@gnu.org> <834oahiute.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1292291555 17211 80.91.229.12 (14 Dec 2010 01:52:35 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 14 Dec 2010 01:52:35 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 14 02:52:31 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PSK42-0004NV-JK for ged-emacs-devel@m.gmane.org; Tue, 14 Dec 2010 02:52:26 +0100 Original-Received: from localhost ([127.0.0.1]:43185 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PSJtW-00062R-79 for ged-emacs-devel@m.gmane.org; Mon, 13 Dec 2010 20:41:34 -0500 Original-Received: from [140.186.70.92] (port=43739 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PSJtQ-0005zC-IJ for emacs-devel@gnu.org; Mon, 13 Dec 2010 20:41:30 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PSJtP-0001YJ-Kf for emacs-devel@gnu.org; Mon, 13 Dec 2010 20:41:28 -0500 Original-Received: from mx1.aist.go.jp ([150.29.246.133]:50981) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PSJtM-0001UX-L8; Mon, 13 Dec 2010 20:41:25 -0500 Original-Received: from rqsmtp2.aist.go.jp (rqsmtp2.aist.go.jp [150.29.254.123]) by mx1.aist.go.jp with ESMTP id oBE1fIVb028659; Tue, 14 Dec 2010 10:41:18 +0900 (JST) env-from (handa@m17n.org) Original-Received: from smtp2.aist.go.jp by rqsmtp2.aist.go.jp with ESMTP id oBE1fIkR017167; Tue, 14 Dec 2010 10:41:18 +0900 (JST) env-from (handa@m17n.org) Original-Received: by smtp2.aist.go.jp with ESMTP id oBE1fIYe021892; Tue, 14 Dec 2010 10:41:18 +0900 (JST) env-from (handa@m17n.org) Original-Received: from handa by etlken with local (Exim 4.71) (envelope-from ) id 1PSJtG-0003OG-7Z; Tue, 14 Dec 2010 10:41:18 +0900 In-Reply-To: <834oahiute.fsf@gnu.org> (message from Eli Zaretskii on Mon, 13 Dec 2010 16:58:05 +0200) X-detected-operating-system: by eggs.gnu.org: Solaris 9 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:133673 Archived-At: In article <834oahiute.fsf@gnu.org>, Eli Zaretskii writes: > > some old codes still treat nil for `no-conversion' > I see a few of such places in coding.c; are there others? I don't remember at the momemnt, but mule.el, mule-cmds.el, and mule-util.el should be checked. > If coding.c is the only place, I think we can safely change it to > tread nil as unidecided. > > and new codes consider nil as "unspecified" and thus treat it as > > `undecided'. Perhaps, ver. 24 is a good timing to wipe out this > > confusion, but I'm not sure how to treat nil. Nil should usually > > mean "unspecified", and what exactly "unspecified" means depends on > > a situaion. > What would be a situation where it's inappropriate to interpret nil as > undecided? For instance, coding-system-for-read being bound to nil and to `undecided' have different meanings. --- Kenichi Handa handa@m17n.org