aboutsummaryrefslogtreecommitdiff
path: root/manual/time.texi
diff options
context:
space:
mode:
authorUlrich Drepper <drepper@redhat.com>2001-09-01 06:22:57 +0000
committerUlrich Drepper <drepper@redhat.com>2001-09-01 06:22:57 +0000
commit45e0579fb7f8008c3df3358ca63bf9189e236edb (patch)
tree1bd2af73894fcac810c9b10b3bc72ee05a05162e /manual/time.texi
parenteaad82e00522075b805621309775131e27388791 (diff)
downloadglibc-45e0579fb7f8008c3df3358ca63bf9189e236edb.tar
glibc-45e0579fb7f8008c3df3358ca63bf9189e236edb.tar.gz
glibc-45e0579fb7f8008c3df3358ca63bf9189e236edb.tar.bz2
glibc-45e0579fb7f8008c3df3358ca63bf9189e236edb.zip
Update.
2001-08-31 Ulrich Drepper <drepper@redhat.com> * time/strptime.c (strptime_internal): Recognize 'l' format and handle it like 'I' for symmatry with strftime.
Diffstat (limited to 'manual/time.texi')
-rw-r--r--manual/time.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/manual/time.texi b/manual/time.texi
index 27060b5358..a128243d4d 100644
--- a/manual/time.texi
+++ b/manual/time.texi
@@ -1480,6 +1480,11 @@ format; e.g. a date passed as @code{"02:1999:9"} is acceptable, even
though it is ambiguous without context. As long as the format string
@var{fmt} matches the input string the function will succeed.
+The user has to make sure, though, that the input can be parsed in a
+unambiguous way. The string @code{"1999112"} can be parsed using the
+format @code{"%Y%m%d"} as 1999-1-12, 1999-11-2, or even 19991-1-2. It
+is necessary to add appropriate separators to reliably get results.
+
The format string consists of the same components as the format string
of the @code{strftime} function. The only difference is that the flags
@code{_}, @code{-}, @code{0}, and @code{^} are not allowed.