From: Kevin Ryde <user42@zip.com.au>
Subject: Re: stime.c forcing errno
Date: Sun, 15 Feb 2004 08:54:59 +1000 [thread overview]
Message-ID: <87r7wxi858.fsf@zip.com.au> (raw)
In-Reply-To: <m3ad3mtizr.fsf@multivac.cwru.edu> (Paul Jarc's message of "Fri, 13 Feb 2004 22:52:34 -0500")
prj@po.cwru.edu (Paul Jarc) writes:
>
> But for mktime/strptime, test for failure afterwards and
> set errno in that case. Setting it beforehand may not help; since
> these functions are not documented to have any particular effect on
> errno, they might have any effect at all - such as replacing our
> EINVAL with something nonsensical.
I guess it's a possibility. I'll set it afterwards.
> It would also be ok to test afterwards for localtime/gmtime as well.
> POSIX says they should set errno, but the C standard doesn't, so that
> might be a good idea.
Ok, then I'll go with what I made.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-02-14 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-14 0:09 stime.c forcing errno Kevin Ryde
2004-02-14 3:52 ` Paul Jarc
2004-02-14 3:58 ` Paul Jarc
2004-02-14 22:54 ` Kevin Ryde [this message]
2004-02-23 19:32 ` Marius Vollmer
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r7wxi858.fsf@zip.com.au \
--to=user42@zip.com.au \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).