zsh-workers
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-workers@zsh.org
Subject: Re: segfault in strftime
Date: Fri, 26 Feb 2010 23:45:25 +0100	[thread overview]
Message-ID: <20100226224525.GG13766@prunille.vinc17.org> (raw)
In-Reply-To: <100226094731.ZM3981@torch.brasslantern.com>

On 2010-02-26 09:47:31 -0800, Bart Schaefer wrote:
> That's *probably* safe in this case ... but in general I don't think
> so.  The standards make no guarantee about the value of errno in the
> case where the library call returns "successfully" (however that may
> be defined) -- that is, the implementation is allowed to set errno
> to what the next upcoming error *might* be, and is not required to
> then clear errno before returning success.

It is safe for functions that use errno: "The value of errno may
be set to nonzero by a library function call whether or not there
is an error, provided the use of errno is not documented in the
description of the function in this International Standard."

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)


      reply	other threads:[~2010-02-26 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A73C7D9C-66C5-4BFA-8FB3-8560FE65B529@biskalar.de>
     [not found] ` <20100226125256.GC13766@prunille.vinc17.org>
     [not found]   ` <20100226150748.GE13766@prunille.vinc17.org>
     [not found]     ` <20100226151712.05fbe555@news01>
     [not found]       ` <20100226162130.GF13766@prunille.vinc17.org>
     [not found]         ` <201002261645.o1QGji9R022432@news01.csr.com>
2010-02-26 17:47           ` Bart Schaefer
2010-02-26 22:45             ` Vincent Lefevre [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100226224525.GG13766@prunille.vinc17.org \
    --to=vincent@vinc17.org \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).