X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f X-Recipient: djgpp-workers AT delorie DOT com From: Martin Strömberg Message-Id: <201203091153.q29BrKKK018225@dexter.ludd.ltu.se> Subject: Re: errno returned by open() To: djgpp-workers AT delorie DOT com Date: Fri, 9 Mar 2012 12:53:19 +0100 (MET) In-Reply-To: <201203082306.15018.juan.guerrero@gmx.de> from "Juan Manuel Guerrero" at Mar 08, 2012 11:06:14 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by mother.ludd.ltu.se id q29BrKg7012795 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id q29CFeD1025736 Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk According to Juan Manuel Guerrero: > Am Mittwoch, 7. März 2012 schrieb Eli Zaretskii: [ errno setting stuff. ] This sounds weird to me. If you call a function that sets errno on failure (open e. g.), you must be prepared for that errno is changed. So a function may set errno even if it succeeds. The value of errno is valid only if the (just called) function returned failure (and is documented to set errno). Perhaps this is case where libc depends internally on an untouched errno, in which case sorry for piping up and disturbing you. -- MartinS