From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/109 Path: news.gmane.org!not-for-mail From: Solar Designer Newsgroups: gmane.linux.lib.musl.general Subject: errno (was: Weekly reports - B) Date: Wed, 6 Jul 2011 15:35:08 +0400 Message-ID: <20110706113508.GA21773@openwall.com> References: <4DF12B1D.7050106@gmail.com> <20110613021130.GA21268@openwall.com> <20110613022221.GO191@brightrain.aerifal.cx> <20110613025655.GA21653@openwall.com> <20110613045418.GQ191@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1309952117 26006 80.91.229.12 (6 Jul 2011 11:35:17 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 6 Jul 2011 11:35:17 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-193-gllmg-musl=m.gmane.org@lists.openwall.com Wed Jul 06 13:35:13 2011 Return-path: Envelope-to: gllmg-musl@lo.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by lo.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1QeQNt-0005MZ-7s for gllmg-musl@lo.gmane.org; Wed, 06 Jul 2011 13:35:13 +0200 Original-Received: (qmail 30617 invoked by uid 550); 6 Jul 2011 11:35:12 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 30608 invoked from network); 6 Jul 2011 11:35:12 -0000 Content-Disposition: inline In-Reply-To: <20110613045418.GQ191@brightrain.aerifal.cx> User-Agent: Mutt/1.4.2.3i Xref: news.gmane.org gmane.linux.lib.musl.general:109 Archived-At: Rich, On Mon, Jun 13, 2011 at 12:54:18AM -0400, Rich Felker wrote: > ... errno is a macro and has been for a > long time (ever since threads) on most systems. It's required by the > standard to be an lvalue macro. Any idea why glibc has __set_errno() internally instead of assigning to its errno directly, then? The implementation for __set_errno() does a direct assignment anyway. What did the glibc developers need __set_errno() for if errno is required to be an lvalue, and do they still need __set_errno() or is it legacy? Meanwhile, I continue to use __set_errno() in my glibc patches, at least for consistency with upstream's code. Thanks, Alexander