Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-15 Thread Bart Lateur
On Thu, 14 Sep 2000 19:19:34 -0400, Chris Nandor wrote: >And yes, sometimes the OS is completely lacking in knowledge of a >time zone. This problem isn't new. Currently, Perl must know the timezone to be able to correctly generate gmtime() and localtime(). -- Bart.

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-15 Thread Chris Nandor
At 9:17 -0400 2000.09.15, Chaim Frenkel wrote: >> "CN" == Chris Nandor <[EMAIL PROTECTED]> writes: > >CN> At 22:19 -0400 2000.09.14, Chaim Frenkel wrote: >>> If you want to adjust for timezones just calculate the constant. Which >>> since you are giving it in HHMM format you might as well just

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-15 Thread Bart Lateur
On Fri, 15 Sep 2000 11:58:08 -0400 (EDT), Andy Dougherty wrote: >[Aside: Does this mean that make(1) is useless for one hour after >standard time resumes?] That'll teach you. You shouldn't be programming in the middle of the night. -- Bart.

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-15 Thread Chaim Frenkel
> "CN" == Chris Nandor <[EMAIL PROTECTED]> writes: >> my_time_in_local_epoc >> + current_os_epoch_offset >> - timezone_ofset_in_seconds >> = time_in_unix_epoch_seconds CN> But again, I don't know what you are trying to say. Are you saying we CN> should have some global "constant"? If so, y

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-15 Thread Chris Nandor
At 15:55 -0400 2000.09.15, Chaim Frenkel wrote: >CN> * We do not know if it will always be this simple for every platform > >Hard to see how the three variables wouldn't cover the spectrum. Very hard to see, until we know what the disparate platforms might require. :) >CN> * You might need to

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-15 Thread Chaim Frenkel
> "CN" == Chris Nandor <[EMAIL PROTECTED]> writes: >> This new module to cover your feature would require that it know every >> known epoch and timesystem (or at least the useful ones.) Something >> this domain knowledgable shouldn't be in CORE. CN> Why? File::Spec is in the core. So are m

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-15 Thread Chris Nandor
At 17:11 -0400 2000.09.15, Chaim Frenkel wrote: >> "CN" == Chris Nandor <[EMAIL PROTECTED]> writes: > >>> This new module to cover your feature would require that it know every >>> known epoch and timesystem (or at least the useful ones.) Something >>> this domain knowledgable shouldn't be in

RFC 48 (v3) Replace localtime() and gmtime() with date() and utcdate()

2000-09-15 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Replace localtime() and gmtime() with date() and utcdate() =head1 VERSION Maintainer: Nathan Wiger <[EMAIL PROTECTED]> Date: 05 Aug 2000 Last Modified: 15 Sep 2000 Mailing List: [EMAIL PROTECTE

Re: RFC 99 (v3) Standardize ALL Perl platforms on UNIX epoch

2000-09-15 Thread Andy Dougherty
On Fri, 15 Sep 2000, Chris Nandor wrote: > You can only avoid breakage with current scripts if you make no changes to > the current facilities (which is what Andy proposed). Well I have to admit that I was unaware that on Mac and VMS (without the wizardry in vms/vms.c) the value returned by time