Hello brian,
Thanks for your review. With the word "strict" I was trying to reflect the
fact that your regular core functions (time, localtime, gmtime, sleep, etc)
are changing their normal behavior everywhere, along with the added/extended
ones (timelocal, timegm, etc) to strictly make use of full year and
microseconds.
I did like the name "Strict", but If you think I should chose a different
word, I guess it could be Time::Complete or Time::Extended. Does that sound
better?
Thanks for your time.
Francisco
-----Mensaje original-----
From: brian d foy
Sent: Tuesday, August 20, 2013 11:01 AM Newsgroups: perl.modules
To: [email protected]
Subject: Re: Module submission Time::Strict
[[ This message was both posted and mailed: see
the "To," "Cc," and "Newsgroups" headers for details. ]]
In article <[email protected]>, "Perl Authors
Upload Server" <[email protected]> wrote:
The following module was proposed for inclusion in the Module List:
modid: Time::Strict
DSLIP: bdpfp
description: Strict values for core time functions
userid: ZARABOZO (Francisco Zarabozo)
chapterid: 2 (Language_Extensions)
Time::Strict transforms automatically core time functions to force
the use of more precise values.
This seems to me like an odd use of the word "strict". Is there another
word or name that might more closely describe this module?
--
brian d foy (one of many PAUSE admins), http://pause.perl.org
PAUSE instructions: http://pause.perl.org/pause/query?ACTION=pause_04about
Archives: http://www.xray.mpe.mpg.de/mailing-lists/modules
Please send all messages back to [email protected] with no CC to me.
