zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Chan Sean <Sean.Chan@wmc.com.au>,
	"'zsh-workers@math.gatech.edu '" <zsh-workers@math.gatech.edu>
Subject: Re: Zsh 2.6 and Y2K status
Date: Thu, 2 Jul 1998 08:37:07 -0700	[thread overview]
Message-ID: <980702083707.ZM17926@candle.brasslantern.com> (raw)
In-Reply-To: <B0000125963@bell04.its.wmc.com.au>

On Jul 2,  3:58pm, Chan Sean wrote:
} Subject: Zsh 2.6 and Y2K status
}
} On behalf of my client WMC Resources Ltd. I need to know if ZSH is Y2K
} compliant. May I know where I can find such information??

You can confirm the following by looking at the source code yourself if
necessary; there's no other definitive reference:

Zsh uses UNIX/POSIX time_t, timeval, and tm data types for internal date
manipulations.  These types either do not store year values at all (for
example, time_t is measured in seconds since midnight, Jan 1, 1970) or
store them as integer types and NOT as pairs of digits.  Thus there can
be no overflows at year 2000.  On some unix systems, time_t is a 32-bit
value and will overflow during the year 2038, but more modern systems use
a 64-bit time_t.

The only input and output of dates that zsh performs is optional history
time-stamping.  This is performed using time_t values converted to long
integers, which are either 32 or 64 bits, see above.

Note, however, that zsh does provide facilities for formatted date output,
so it's possible that scripts written for zsh might employ 2-digit years.
Shell scripts should always be considered separate programs and therefore
evaluated individually.

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1998-07-02 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-02  7:58 Chan Sean
1998-07-02 15:37 ` Bart Schaefer [this message]
1998-07-02 16:16   ` Zefram
1998-07-03  4:40     ` Anthony Heading

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=980702083707.ZM17926@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=Sean.Chan@wmc.com.au \
    --cc=zsh-workers@math.gatech.edu \
    /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).