Re: [MacPerl] [ALBOT] Mac Y2K Oops?

[rjk@linguist.dartmouth.edu (Ronald J. Kimball)]

Richard Gordon wrote:
> 
> So,I don't even know if MacPerl provides access to StringToText via a
> toolbox module, but if it does, I would assume that it is also
> broken. Even if it doesn't I'm not sure how any of this ultimately plays
> out when using time or lacaltime while running MacPerl?
> 

I don't see how this would be an issue with time or localtime.  time()
returns seconds since the epoch; localtime() converts seconds since the
epoch into a date.  There's no obvious ambiguity there.

> My concluding comment is that I would imagine that Apple could patch the
> function pretty easily, but I'm having a little trouble understanding why
> this apparently hasn't been addressed by Apple thus far. Any thoughts?

How should Apple "address" this?  How would you have them patch the
function?

If you write out ambiguous dates, then you have to deal with that ambiguity
when you read the dates back in.  Apple's way of dealing with the
ambiguity, going by your description, seems to be as good as any, and
better than some.

The only real fix is to the data and the output routines.

Ronald

***** Want to unsubscribe from this list?
***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch