Zsh 2.6 and Y2K status

Zsh 2.6 and Y2K status

[Chan Sean]

To whom it may concern,

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??

Thanks in advance,

Sean
--
Sean H.Y. Chan (sean@tsm.com.au)
IT Consultant
DSM Group Pty. Ltd.       +61 (0)414-467-077 (M)
PO Box 1493, West Perth, 6872, WESTERN AUSTRALIA

Re: Zsh 2.6 and Y2K status

[Bart Schaefer]

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

Re: Zsh 2.6 and Y2K status

[Zefram]

Ahem.

*** utils.c.old	Thu Jul  2 17:14:24 1998
--- utils.c	Thu Jul  2 17:14:39 1998
***************
*** 1370,1376 ****
  		*buf++ = '0' + tm->tm_sec % 10;
  		break;
  	    case 'y':
! 		*buf++ = '0' + tm->tm_year / 10;
  		*buf++ = '0' + tm->tm_year % 10;
  		break;
  #ifndef HAVE_STRFTIME
--- 1370,1376 ----
  		*buf++ = '0' + tm->tm_sec % 10;
  		break;
  	    case 'y':
! 		*buf++ = '0' + (tm->tm_year / 10) % 10;
  		*buf++ = '0' + tm->tm_year % 10;
  		break;
  #ifndef HAVE_STRFTIME

Re: Zsh 2.6 and Y2K status

[Anthony Heading]

On Thu, Jul 02, 1998 at 05:16:44PM +0100, Zefram wrote:
> Ahem.
> 
> *** utils.c.old	Thu Jul  2 17:14:24 1998
> --- utils.c	Thu Jul  2 17:14:39 1998

You can't just do that!!  Think of the effect on the Y2K strategic compliance
assessment team's project timeline projection if you actually just fix things
rather than documenting a requirement to rewrite the system.  And consider
the world economy.  Already international consultancies are crashing into
receivership as the basis of their service is callously rendered redundant.

When we see the children starving in the streets we'll know why.

A
-- 
Anthony J.R. Heading    J.P. Morgan & Co. Inc, Singapore
Email: heading_anthony@jpmorgan.com    Tel: +65 326 9027