mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: strptime problems
Date: Thu, 8 May 2014 00:32:14 -0400	[thread overview]
Message-ID: <20140508043214.GA6149@brightrain.aerifal.cx> (raw)

It was raised somewhere (on IRC, I think) that strptime still has some
failure paths where functionality is unimplemented. These should have
been caught and fixed a long time ago, but they weren't, so I'd like
to get it done now. However I'm not clear on what the behavior of
strptime should be when reading "derived" fields that don't actually
correspond to anything in the "struct tm". Should it just parse and
ignore them, or should it somehow convert back? The week-based-year
stuff is probably the biggest question but there are others too.

Rich


             reply	other threads:[~2014-05-08  4:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  4:32 Rich Felker [this message]
2014-05-08 13:44 ` Isaac Dunham
2014-05-08 16:42 ` Szabolcs Nagy

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=20140508043214.GA6149@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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/musl/

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).