summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdtime
Commit message (Collapse)AuthorAgeFilesLines
* Detect range errors when using the %s specifier. Previously, LONG_MAXnectar2003-11-171-3/+10
| | | | | | | was rejected as a range error, while any values less than LONG_MIN were silently substituted with LONG_MIN. Furthermore, on some platforms `time_t' has less range than `long' (e.g. alpha), which may give incorrect results when parsing some strings.
* mdoc(7): Use the new feature of the .In macro.ru2003-09-081-1/+1
|
* Fixes to locale code to properly use indirect pointers in order to preventjkh2003-06-131-1/+1
| | | | | | | memory leaks (fixes bugs earlier purported to be fixed). Submitted by: Ed Moy <emoy@apple.com> Obtained from: Apple Computer, Inc. MFC after: 2 weeks
* Backout my changes in rev. 1.32 and 1.33. There is some code that dependsmtm2003-04-301-4/+2
| | | | | | | on the previous behaviour. This also brings strptime(3) behaviour back in line with the other BSDs. Approved by: markm (mentor)
* Zero out the struct tm supplied by the caller. Otherwise,mtm2003-04-051-0/+1
| | | | | | | | strange things might happen when garbage values in the struct get passed in to localtime_r() and family. Noticed by: marcus Approved by: markm (mentor)(implicit)
* Fill in the rest of the fields in the resulting struct tmmtm2003-03-291-2/+3
| | | | | | | | | | from strptime(3). Previously, they would get filled only for the %s specifier and as a side effect of using the the %Z specifier with a GMT time zone. PR: misc/48993 Approved by: markm (mentor) Silence on: -standards
* Ditch a static global and the mutex that protected it. Achieve themtm2003-03-121-27/+18
| | | | | | | | desired strptime(3) reentrancy by adding an extra argument to _strptime() instead. Approved by: markm (mentor) MFC: 4 weeks
* Eliminate 61 warnings emitted at WARNS=2 (leaving 53 to go).nectar2003-02-164-9/+9
| | | | | | | Only warnings that could be fixed without changing the generated object code and without restructuring the source code have been handled. Reviewed by: /sbin/md5
* strptime(), like strftime(), does not handle multibyte characterstjr2003-01-041-1/+7
| | | | in the format string correctly.
* Mention in the BUGS section that strftime() does not handle multibytetjr2003-01-041-1/+7
| | | | characters in the format string correctly.
* mdoc(7) police: Fixed a few .Fa abuses.ru2002-12-191-2/+4
|
* mdoc(7) police: excessive quotes.ru2002-12-191-1/+1
|
* mdoc(7) police: "The .Fn function".ru2002-12-181-1/+13
|
* Document what happens when the format string contains insufficienttjr2002-12-181-0/+23
| | | | | | | | conversion specifications to completely specify the resulting struct tm. PR: 46331 Submitted by: Christian S.J. Peron MFC after: 2 weeks
* Do not guarantee an overflow of tm_year when doing the binary search inpeter2002-12-051-0/+6
| | | | | | localtime/mktime/tmcomp and friends on ia64. Approved by: re
* Replace rev 1.33 with a real fix. The problem was integer overflowspeter2002-12-021-8/+2
| | | | | | | | | | | | | | | | when trying to store the year in a signed int. The maximum time_t on ia64 is around 292 billion years in the future, but 'int' and struct tm.tm_year can only represent then ext 2.1 billion years or so. This solves the problem of mktime/localtime looping on ia64. Unfortunately, the standards say that tm_year is an 'int', so we are still stuck with a y2147483647 bug. bash2's configure script looks for bugs in mktime() and fails on ia64 because of this. However, mktime() on FreeBSD fails the test normally anyway so this is no big loss. This change does not affect any other platforms besides ia64. Approved by: re
* libc_r wasn't so tied to libc for 22 months.ru2002-11-181-3/+1
|
* Add cross-references to the wide character counterparts of these functions.tjr2002-10-151-1/+2
|
* Style: One space between "restrict" qualifier and "*".tjr2002-09-064-12/+12
|
* Fix a nasty bug exposed by mktime() when time_t is significantly biggerpeter2002-09-031-0/+6
| | | | | | | than 32 bits. It was trying to figure out things like the day of week of when time_t is roughly 2^62 etc. Make a better guess for the starting point for the binary search that works on both 32 and 64 bit types. I have been using this for a while now.
* Use one line for each function argument to keep the linerobert2002-08-152-2/+11
| | | | | | | width smaller than 80 columns. Thanks to Ruslan for an explanation of multiple ways to achieve this.
* - Add the 'restrict' qualifier to the function definition ofrobert2002-08-142-7/+5
| | | | | | | | | strftime(3) for IEEE Std 1003.1-2001 compliance and remove excessive usage of the 'const' qualifier that was neither present in the prototype in the publice header, nor in the local prototype just above the function definition. - Replace the K&R function definition with a ANSI-C one. - Update the prototype of strftime(3) in its manual page.
* - Add the C99 'restrict' qualifier using the '__restrict' macro torobert2002-08-142-2/+3
| | | | | function prototype and definition of strptime(3). - Update the manual page.
* Style fixesache2002-08-071-9/+6
|
* Move dillon's time conversion functions to a new header <timeconv.h>.wollman2002-06-171-1/+1
| | | | | | Since they were never documented and have never appeared in a FreeBSD release, no repo-copy of the header is done. This removes namespace pollution from <time.h>.
* Grammar nit: treat "contents" as plural.archie2002-05-311-1/+1
|
* Remove use of __P() (actually P()) from code now that it's no longeralfred2002-05-282-42/+42
| | | | available.
* Assume __STDC__, remove non-__STDC__ code.alfred2002-05-281-13/+0
| | | | Submitted by: keramida
* Fix fd leak. Threads people: does the call above to `access' need to bewollman2002-05-031-1/+3
| | | | | | | underscored as well? PR: 37717 Submitted by: fred@clift.org (slightly modified by me)
* Fix the style of the SCM ID's.obrien2002-03-222-3/+5
| | | | I believe have made all of libc .h's as consistent as possible.
* Fix the style of the SCM ID's.obrien2002-03-227-25/+18
| | | | I believe have made all of libc .c's as consistent as possible.
* Remove 'register' keyword.obrien2002-03-212-75/+75
|
* * style(9)'fyphantom2002-01-242-33/+34
| | | | * declare prototype for __time_load_locale() in timelocal.h
* I've been meaning to do this for a while. Add an underscore to thedillon2002-01-191-12/+12
| | | | | | | | time_to_xxx() and xxx_to_time() functions. e.g. _time_to_xxx() instead of time_to_xxx(), to make it more obvious that these are stopgap functions & placemarkers and not meant to create a defacto standard. They will eventually be replaced when a real standard comes out of committee.
* Add my e-mail to copyrightsphantom2001-12-111-1/+1
|
* Add time_to_int(), int_to_time(), time_to_long(), long_to_time().dillon2001-10-281-0/+40
|
* Add routines to convert time_t to/from fixed-bit fields. These routinesdillon2001-10-282-1/+62
| | | | | | | | | | | | | | | | | | | serve two purposes: (1) so we can maintain backwards compatibility with protocols (rwhod, dump, etc...) that either assume time_t is 32 bits or assume sizeof(time_t) == sizeof(int), or make other similar assumptions. (2) To tag such routines (by the presence of these calls) for future cleanup/extension work. The 32->64 routine, time32_to_time() (when time_t is 64 bits, that is), is defined specifically to implement temporal locality to properly set the msb bits of a 64 bit time_t quantity, using the 50 year rule. The locality code has not been implemented yet (and doesn't need to be for a while), but that is the intent. This will allow us to maintain backwards protocol compatibility past 2038. These routines are intended to be platform and time_t agnostic. MFC after: 1 week
* mdoc(7) police: Use the new .In macro for #include statements.ru2001-10-014-4/+4
|
* mdoc(7) police:ru2001-08-071-2/+2
| | | | | | | Avoid using parenthesis enclosure macros (.Pq and .Po/.Pc) with plain text. Not only this slows down the mdoc(7) processing significantly, but it also has an undesired (in this case) effect of disabling hyphenation within the entire enclosed block.
* Remove whitespace at EOL.dd2001-07-152-6/+6
|
* Recognize the %s format.dd2001-07-131-0/+16
| | | | | | Submitted by: Thomas Zenker <thz@lennartz-electronic.de> and Maxim Konovalov <maxim@macomnet.ru>, respectively Reviewed by: -audit
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-102-2/+2
|
* mdoc(7) police: remove extraneous .Pp before and/or after .Sh.dd2001-07-091-1/+0
|
* Document "normalizing" behavior of mktime(3).ru2001-06-231-1/+12
| | | | | | PR: bin/28313 Reviewed by: bde, wollman MFC after: 1 week
* Don't mung the user's tm_sec field if we don't need to. (Belt-and-suspenderswollman2001-06-051-1/+3
| | | | | | | | | version.) PR: bin/27630 Submitted by: Arthur David Olson <ado@nci.nih.gov> Obtained from: Timezone mailing-list <tz@elsie.nci.nih.gov> MFC after: 1 month
* MAN[1-9] -> MAN.ru2001-03-271-2/+2
|
* Get rid of non-standard %E[Ff] formats, userland apps already fixedache2001-03-213-33/+4
|
* Oops, back out prev. change - POSIX require %y in d_fmtache2001-03-211-4/+4
| | | | Cosmetique - use exact POSIX string for %c
* Replace %y with %Yache2001-03-211-1/+1
|
* Fix typo in the commentache2001-03-181-1/+1
|
OpenPOWER on IntegriCloud