At 10:08 -0400 2000.09.14, Andy Dougherty wrote:
>This is not a simple either-or.  Suppose you are using a Mac and that
>perl6 decides to use the Unix epoch.  Suppose you want to communicate with
>other Mac programs or library functions about time (e.g. perhaps by
>calling things through the XS interface or by storing to a file). Since
>the perl6 time() and C time() will now disagree about what time it is,
>even the non-lazy programmer will have to use $Perl::EpochOffset
>everywhere.

There's also the possibility of time accepting an argument, where 0 would
be perl's time and 1 would be native time, or something.

-- 
Chris Nandor                      [EMAIL PROTECTED]    http://pudge.net/
Open Source Development Network    [EMAIL PROTECTED]     http://osdn.com/

Reply via email to