On Fri, 28 May 2004, Jean Forget wrote:
First question: what about copyright? I plan to
write something like (taking Ben's FAQ as an example):
English original version: copyright 2003 Ben Bennett
French translation: copyright 2004 Jean Forget and les Mongueurs de Perl
Distributed under the
0.27 2004-05-27
- This release is based on version 2004a of the Olson database.
- /etc/timezone and /etc/TIMEZONE are not the same thing. Code for
getting the local time zone name from the latter was supplied by
Daniel Boorstein.
- Added support for getting the local time zone from
On Thu, 13 May 2004, Danny Rathjens wrote:
Am I misunderstanding these methods or is this a bug? ;)
You're misunderstanding, but it may be a doc problem.
perl -MData::Dumper -MDateTime -wle'$past = DateTime-now-subtract(months=2); $now
= DateTime-now; $dur = $now-delta_days($past); print
On Fri, 14 May 2004, Danny Rathjens wrote:
ok, I was confused into thinking this was possible by my $dur =
$now-delta_days($past)
in my first example, which results in 61 days due to a two month difference.
I realize now that DT::delta_days means something different than
On Fri, 14 May 2004, Danny Rathjens wrote:
That seems a bit overcomplicated just to figure out the number of days
between two dates, though.
Is there anything wrong with using this?:
[EMAIL PROTECTED]:~/tst% perl -MDateTime -wle'$past =
DateTime-now-subtract(months=2); print
On Sun, 9 May 2004, Jonah Petri wrote:
Did DateTime::TimeZone::offset_as_seconds at some point allow 2 digit
offsets? (i can't find any evidence of this...)
No
Did postgres at some point output data with 4 (or 6) digit offsets?
(Not that I can find or remember)
I dunno.
Has
On Thu, 22 Apr 2004, Daniel B. Boorstein wrote:
Attached are patches to 'DateTime/TimeZone/Local.pm' and '04local.t'
that correct this for me.
I applied this, and also added support for getting the time zone from
/etc/default/init.
-dave
/*===
House Absolute Consulting
On Thu, 22 Apr 2004, David Wheeler wrote:
My only objection to svn is that activitymail doesn't work with it.
Perhaps someone could convince the maintainer of that program to find
the tuits to port it, eh?
Um, yeah, that maintainer should! There are two scripts that come with
Subversion for
I'm getting fed up with the damn sourceforge CVS instability and slowness.
What do people think of moving to Subversion, hosted either on my own box
(svn.urth.org) or maybe svn.perl.org if I can talk Ask and/or Robert into
it?
I'd convert the existing CVS repo, and since we don't have any
On Wed, 21 Apr 2004, Joshua Hoblitt wrote:
On Wed, 21 Apr 2004, Dave Rolsky wrote:
I'm getting fed up with the damn sourceforge CVS instability and slowness.
But at least it's backed up occasionaly...
What do people think of moving to Subversion, hosted either on my own box
On Thu, 22 Apr 2004, Daisuke Maki wrote:
Too bad we can't just get a free copy of Perforce. I really enjoyed it
at my previous work.
We probably could, but I wouldn't use it. I prefer free software over
propietary when given the choice, and Subversion works quite well.
-dave
On Wed, 14 Apr 2004, Ken Burcham wrote:
[EMAIL PROTECTED] DateTime-0.21]# make
Makefile:96: *** missing separator. Stop.
[EMAIL PROTECTED] DateTime-0.21]#
hmm... So not to be deterred, I looked at line 96 of the
makefile and here's the weird stuff I find:
94:installhtml1dir=''
On Wed, 14 Apr 2004, Ken Burcham wrote:
Well, I was finally able to get it to work by making
a bunch of changes to the Makefile. Then I also had
to copy the binary stuff by hand ( mv
./blib/arch/auto/DateTime
/usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-
multi/auto/.).
Well, the
1.092004-04-07
- Fixed a bug in the test suite that led to timegm not getting tested
properly, and timelocal getting tested twice for the same values.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Sun, 28 Mar 2004, Eugene van der Pijll wrote:
Is it possible to detect mixed durations other than checking all of
is_positive, is_zero and is_negative? For example by adding an is_mixed
method?
Something like that, with a better name than is_mixed would be good.
Name suggestions, anyone
0.21 2004-03-28 (The Another YAPC::Taipei release party release
release)
[ *** BACKWARDS INCOMPATIBILITIES *** ]
- When given mixed positive negative arguments, DateTime::Duration
no longer forces all arguments to be negative.
- For mixed durations, the is_positive, is_zero, and is_negative
So you know that you've become the man when you see this:
Date::Object is an alternative to the DateTime modules, with the main
pourpose to handle dates using a single object or make multiple
Date::Objects work together to calculate and handle dates.
I guess the DateTime project has now
On Thu, 18 Mar 2004, Eugene van der Pijll wrote:
Unfortunately, I have no internet connection at home at the moment, so it
could take a while for me to upload a new version. Perhaps someone else can do
it? (There are also some new DT modules to be added: DT::Stringify and
Daisuke Maki's new
On Wed, 17 Mar 2004, Joshua Hoblitt wrote:
Does it make sense to add Module::Build to the bundle? DateTime::Locale immediately
asks for it.
Yeah, it seems like a good idea.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
0.26 2004-03-09
- Added DateTime::TimeZone-is_valid_name class method.
- Added Storable freeze thaw hooks. This should fix RT ticket
#5542, reported by Dan Rowles (I hope).
Rick, the Storable hooks should mean that with the next release of
DateTime.pm (out shortly), you could give it an
On Sat, 28 Feb 2004 [EMAIL PROTECTED] wrote:
DateTime.pm 0.20 works in Windows NT, with
this patch:
15a16,17
eval
{
26a29
};
35a39,40
require DateTimePP
unless defined DateTime::_ymd2rd;
This patch makes no sense when applied to the current code,
On Sun, 15 Feb 2004, Andrew Pimlott wrote:
On Sat, Feb 14, 2004 at 11:26:52AM -0500, Andrew Pimlott wrote:
$self-{nanoseconds} = 1 - $self-{nanoseconds} if $seconds 0;
$self-{nanoseconds} -= MAX_NANOSECONDS if $seconds 0;
And this time I really tested it! (All tests pass, since
On Thu, 4 Mar 2004, Flavio S. Glock wrote:
Looks good. How about:
* set_map
$set2 = $set-set_map( sub { return } );
# same as $set-clone
This would be the same as $set-empty_set, actally.
Clone would be:
$set2 = $set-set-Map( sub { return $_[0]-clone } );
$set2 = $set-set_map(
On Thu, 4 Mar 2004, Dave Rolsky wrote:
$set2 = $set-set_map( sub {
$_[0]-add( hours = 1 );
return;
}
);
# same as before.
Hmm, this does encourage the map in void context idiom, which is
unfortunate. In this case, $set2 would be an empty set. Maybe we should
On Wed, 3 Mar 2004, Joshua Hoblitt wrote:
There are two threads running on the p6i list right now dealing with
date and time handling. The threads are Dates and Times and
Epoch Larry Wall has stated that by default Perl 6 will return
time as a floating point number of seconds since
On Wed, 3 Mar 2004, Andrew Pimlott wrote:
As an immediate reaction from someone who hasn't used any of the
Set/Span modules, I don't like that last part. One, it's too easy for
someone who only skims the documentation to miss it, and end up with a
very subtle bug. Two, lots of functions
On Thu, 4 Mar 2004 [EMAIL PROTECTED] wrote:
Accepting 'undef' in a map operation is ok, but a Set cannot contain
'undef' !
The problem is that if the callback is called in a scalar context, and it
does a bare return, like this:
$set-iterate( sub { return } )
then that return returns an
This sounds interesting. Anything we can steal?
-- Forwarded message --
Date: Tue, 02 Mar 2004 09:13:08 -0800
From: Brian S O'Neill [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Another tz compiler
Resent-Date: Tue, 2 Mar 2004 12:12:37 -0500 (EST)
Resent-From: [EMAIL
On Wed, 3 Mar 2004, Rick Measham wrote:
Currently if I have:
$this_year = span 2004-01-01 to 2004-12-31
$today = span 2004-03-03
And I put them into a spanset, then all I can retrieve is a span
equivelent to $this_year.
I'm assuming by put them into a spanset, you mean creating a set
On Tue, 2 Mar 2004 [EMAIL PROTECTED] wrote:
On Mon, 1 Mar 2004, Flavio S. Glock wrote:
How about this API (almost the same as
Date::Set's):
my $start_set =
$spanset-iterate(
sub { $_[0]-start }
);
my $end_set =
$spanset-iterate(
On Sat, 28 Feb 2004, Rich Bowen wrote:
Anyways, mostly I just wanted to mention that I'm working on it, and
that I'm finally back.
Glad to have you back.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Tue, 24 Feb 2004, Christopher Pryce wrote:
On Mac OSX ( darwin ) 10.2.8
Perl Makefile.PL returns:
perl Build.PL
Checking whether your kit is complete...
Looks good
Deleting Build
Removed previous script 'Build'
Creating new 'Build' script for 'DateTime-Format-ICal' version '0.08'
On Wed, 25 Feb 2004, Rick Measham wrote:
I can't give more technical info at this point except that I need to
install Module::Build before I install anything that depends on it.
I'll be doing another virgin install later in the week if you're
interested in some sort of output. But I'm led to
On Wed, 25 Feb 2004, Rick Measham wrote:
You think MakeMaker is robust? Hahahahahaha
That's funny.
And that's rude.
There absolutely no need for rudeness here. I had a problem, I
described the problem. Rather than responding to the problem you
belittle me ... I don't understand why?
On Tue, 24 Feb 2004, David Wheeler wrote:
1. Every one of us who has Module::Build built modules can release new
versions with the Makefile.PL generated by Module::Build 0.23, which
will not have this problem. Or
2. Wait for the release of Module::Build 0.24, which corrects the
problem in a
On Sun, 22 Feb 2004, Rick Measham wrote:
Back on Topic, below is the module I use for dumping ... if people
are interested I don't mind releasing it. Basically I summarise some
of the long parts of the dump as strings. If you pass it anything but
a DateTime object the module just passes it
On Sat, 21 Feb 2004, David Wheeler wrote:
On Feb 21, 2004, at 7:48 AM, Dave Rolsky wrote:
I found the discussion about stringification. The reason I took it
out of the DateTime.pm code was that it made stack traces look quite
wack.
I trust that's only true when you use a DT object
On Sat, 21 Feb 2004, Matt Sisk wrote:
On second thought...probably a better approach would be for
Devel::StackTrace and Carp to make liberal use of the no overload pragma.
Will that work? If so, I'll gladly add strinfication back, after changing
Devel::StackTrace. Carp users will just have
On Sat, 21 Feb 2004, John Siracusa wrote:
On 2/21/04 3:49 PM, Ben Bennett wrote:
If I remember correctly the argument against auto stringification was
that it made debugging harder.
Speaking of difficult debugging and DT, every time I feed something to
Data::Dumper that contains a DT
On Sat, 21 Feb 2004, John Siracusa wrote:
On 2/21/04 4:33 PM, Dave Rolsky wrote:
On Sat, 21 Feb 2004, John Siracusa wrote:
Speaking of difficult debugging and DT, every time I feed something to
Data::Dumper that contains a DT object (or several) I cringe at the giant
output. I don't
On Sat, 21 Feb 2004, Matt Sisk wrote:
Hmmm, I guess not. At least, I couldn't get 'no overload' to do anything
useful.
How much of a PITA is it to use overload::StrVal and
overload::Overloaded in Devel::StackTrace?
Not a PITA at all, I just liked the other solution even more.
-dave
On Fri, 20 Feb 2004, Nik Clayton wrote:
Richard Clamp and myself have just released Text::vFile::asData, for easy
parsing of vFile files, including (and hopefully of relevance to this list)
RFC2445 vCalendar files.
http://search.cpan.org/~rclamp/Text-vFile-asData/
In particular, some
On Sun, 15 Feb 2004, Andrew Pimlott wrote:
Here is a new version that revises the documentation a little more and
has tests.
Looks good, applied.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Fri, 13 Feb 2004, Randal L. Schwartz wrote:
Dave == Dave Rolsky [EMAIL PROTECTED] writes:
Dave 0.20 2004-02-12
Dave [ IMPROVEMENTS ]
The DateTime-0.20.tar.gz at www.cpan.org is corrupt. I don't know
how many other places are also messed up, but it's not a pretty sight.
I just
On Tue, 10 Feb 2004, Andrew Pimlott wrote:
I don't see why nanoseconds aren't normalized to [0, 1s). The tests
seem to indicate that this is intentional, but I don't see what good
negative nanoseconds do. It doesn't seem to make any difference in any
calculation; the only visible effect
On Thu, 12 Feb 2004, Dave Rolsky wrote:
And by what logic should
Duration-new(seconds = 1) - Duration-new(nanoseconds = 5)
and
Duration-new(nanoseconds = 5)
differ?
I think you're seeing buggy behavior enshrined via tests ;)
In other words, the code
On Tue, 10 Feb 2004, John Siracusa wrote:
On 2/10/04 12:17 PM, Dave Rolsky wrote:
I should add a section to the docs on this so that people know what to
expect.
Yes, please do, because I am eternally confused by this :)
There are some docs already, in DateTime.pm, under the header How
0.20 2004-02-12
[ IMPROVEMENTS ]
- Tweaked the How Date Math is Done section in DateTime.pm to
provide some more explicit examples.
[ BUG FIXES ]
- If seconds are not negative, DateTime::Duration will try to keep
nanoseconds = 0 when normalizing them to seconds, as long as this
doesn't make
On Thu, 12 Feb 2004, Dave Rolsky wrote:
On Tue, 10 Feb 2004, John Siracusa wrote:
On 2/10/04 12:17 PM, Dave Rolsky wrote:
I should add a section to the docs on this so that people know what to
expect.
Yes, please do, because I am eternally confused by this :)
There are some docs
On Mon, 9 Feb 2004, Andrew Pimlott wrote:
It seems consistent and logical to normalize nanoseconds when
multiplying durations. There is also a comment about normalization that
seems both redundant and misleading (since comparison doesn't depend on
nanoseconds being normalized; I assume
On Mon, 9 Feb 2004, Andrew Pimlott wrote:
Miscalculation of when we're in a leap minute.
Applied.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
0.36 2004-02-10
[ BACKWARDS INCOMPATIBILITY ]
- The default time zone is now the floating time zone, not the local
time zone, because we cannot determine the local time zone reliably on
all systems.
Note that we really cannot assume that using local for a time zone will
work, and so parsing
I wrote up some quick guidelines for these modules after fixing a test
failure in DateTime::Format::HTTP where it assumed that it could use
local for the time zone and have it work everywhere.
Please feel free to suggest changes to the document or supply patches.
The POD is in the repo and the
On Tue, 10 Feb 2004, Mark Fowler wrote:
Okay, I'm probably being stupid but...how do I get the number of seconds
a DateTime::Duration takes? I *think* I should be using delta_seconds,
but that doesn't seem to work:
use DateTime::Duration;
my $dur = DateTime::Duration-new(hours = 2);
On Tue, 10 Feb 2004, Matt Sisk wrote:
I understand why you have to deal with the ambiguity, but I still really
wish there were an easer way to get a rough shot at this value when
absolute precision is not required.
In particular I run into this problem when I'm trying to generate
values, in
On Thu, 5 Feb 2004, Jamie LeTual wrote:
Uh... that 'cl' program is didn't find would be a C compiler its looking
for.
But it should just use the pure Perl version if it can't find a compiler.
I'm not sure what's going on here. Probably a bug in the Makefile.PL
script.
-dave
On Thu, 5 Feb 2004, Hill, Ronald wrote:
[EMAIL PROTECTED] wrote:
Summary of the problem:
Creating new 'Build' script for 'DateTime-Calendar-Japanese' version
'0.03' Running [/usr/perl/v5.8.3/bin/perl Build UNINST=1]...
lib/DateTime/Calendar/Japanese.pm -
On Thu, 5 Feb 2004, Jamie LeTual wrote:
Oops, I just realized that my timezone wasn't set properly. After
resetting it to the proper timezone, I reran the c prog, and the values
it gave were
tzname 0: Eastern Standard Time
tzname 1: Eastern Daylight Time
which makes a little more sense
On Thu, 5 Feb 2004, Jamie LeTual wrote:
The following C code will get the windowsified time zone (i.e.
'Atlantic Standard Time')
#include stdio.h
#include time.h
int main(int argc, char **argv)
{
_tzset();
printf(tzname 0: %s\n,_tzname[0]);
printf(tzname 1:
On Wed, 4 Feb 2004, Ilya A. Tereshchenko wrote:
my @t = gmtime;
my $local = Time::Local::timelocal(@t);
my $gm= Time::Local::timegm(@t);
return
DateTime::TimeZone::OffsetOnly-new
( offset =
On Wed, 4 Feb 2004, Daisuke Maki wrote:
My main concerns in trying to encode this into a (strp|strf)time-ish
format are as follows:
- Encoding is actually a combination of number representation
and whatever else format. for example, the era notation is
actually 1) era/roman 2)
On Tue, 3 Feb 2004, John Nystrom wrote:
I am using your DateTime module, and see that when I set the timezone as
'local' it changes directories to get the timezone, but it does not change
the directory back to the working directory. Any information would be
greatly appreciated.
Ah,
On Fri, 30 Jan 2004, Hill, Ronald wrote:
And for the modules that use module build we would need
perl Makefile.pl
perl build
perl build test
perl build dist
perl build ppd
This all works (now!!) I was having major problems creating
the archive. It seems that Archive-tar-1.08 did the
On Fri, 30 Jan 2004, Hill, Ronald wrote:
I check the build results for the current perl version
for DateTime
failed building DateTime prerequisite DateTime-Locale
aborting build of DateTime: failed prerequisites
Checked results for DateTime-locale
failed building DateTime-Locale
On Fri, 30 Jan 2004, Hill, Ronald wrote:
I think it is time that we do come up with a standard way
of shipping out modules. ( Module-Build or makemaker)It sure
would make installing DateTime modules much simpler.
It would? Why? As long as the Module::Build using distros provide a
On Thu, 29 Jan 2004, Daisuke Maki wrote:
It was really annoying me that parsers based on DT::F::Builder would by
default report a parse failure as being in DT::F::B::Parser.
I'd like the error message to tell me where in the calling script it
failed, so I'd like to introduce this patch.
On Thu, 29 Jan 2004, Daisuke Maki wrote:
Can't this be done with the @CARP_NOT variable?
Wow, how on earth have I been ignorant of this variable for such a long
time...?
Anyway, I can write a different version, but is the idea acceptable?
Yeah, the idea is good. Feel free to check the
On Fri, 16 Jan 2004, Jonathan Leffler wrote:
When I was installing using CPANPLUS, it went off and automatically tried
to install Math::BigInt::GMP, and that process failed because I didn't have
GMP amongst my libraries. Now, that might be because it was 'recommended'
rather than 'optional',
On Fri, 16 Jan 2004, Jonathan Leffler wrote:
And, I suppose, it might be sensible to let the Math::BigInt::GMP people
know there are problems when their code is automatically installed on a
system without GMP. There's probably not much they can do except improve
the error messages - if GMP
The signature check fails on my box. I'm guessing that's because the
distro signature used GnuPG 1.0.6 and I have 1.2.4
Can anyone else check this?
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Tue, 13 Jan 2004, Dave Rolsky wrote:
The signature check fails on my box. I'm guessing that's because the
distro signature used GnuPG 1.0.6 and I have 1.2.4
Specifically, I'm talking about Daisuke Maki's new calendar and other
modules.
-dave
/*===
House Absolute
On Tue, 13 Jan 2004, Dave Rolsky wrote:
The signature check fails on my box. I'm guessing that's because the
distro signature used GnuPG 1.0.6 and I have 1.2.4
Can anyone else check this?
Ah, I don't think this is a GPG version mismatch.
Daisuke, you need to put your key on a keyserver
0.1901 2004-01-07 (the people care about ancient history? release)
[ BUG FIXES ]
- The day of week was totally busted for dates before -12-25.
Reported by Flavio Glock.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Mon, 5 Jan 2004, Rick Measham wrote:
It seems that DateTime::LeapSecond adds the extra seconds at midnight UTC.
Two questions:
1. Did it always do that .. I seem to recall that it used to add it
at midnight in the local time zone.
Yes, I think so.
2. Should it be at midnight UTC? I
On Thu, 18 Dec 2003, Mike Schilli wrote:
Hey guys,
while doing some DateTime calculations, I just stumbled across this
weird error: The following snippet produces Invalid local time for the
America/Winnipeg timezone while it works for all others:
use DateTime;
my $dt =
0.2506 2003-12-15
- On systems where /etc/localtime is a copy of a zone info file (like
FreeBSD), we now look for a matching file in /usr/share/zoneinfo in
order to determine the local time zone. Based on a patch from Slaven
Rezic.
- This release is based on the 2003e Olson database
On Mon, 16 Dec 2003, Rick Measham wrote:
- The normalisation works for all the tests, but kick it in the shins;
does it really work?
You should handle leap seconds too, otherwise it could be subtly broken
when using non-floating datetimes. This isn't that hard.
You basically have to check
0.07 2003-12-14
- If given an id like 'en_US.UTF-8', DateTime::Locale would die with
the message 'Can't locate object method _load_from_id via package
DateTime::Locale at /usr/share/perl5/DateTime/Locale.pm line 220'.
Reported by Sylvain Daubert.
-dave
/*===
House
On Sun, 14 Dec 2003, Sylvain Daubert wrote:
I am trying using DateTime with localization. But, when i run my app,
perl complains :
Can't locate object method _load_from_id via package
DateTime::Locale at /usr/share/perl5/DateTime/Locale.pm line 220.
I looked for such a function in
1.07_94 2003-12-11
- More changes from Henrik Gulbrandsen to make sure that very large
negative epoch values are handled properly on platforms that can
handle negative epoch values at all.
- Make sure that we really do always return the earliest of two local
times when DST makes a conversion
On Tue, 9 Dec 2003, Henry Sobotka wrote:
2009. I would expect 9-12-2003 (expressing years in two digits is
frowned upon; e.g. 1998-99 is considered an anglicism, the proper way
to write it being 1998-1999). The string version would be le 9
décembre 2003; month abbreviations tend to be used
On Mon, 8 Dec 2003, Doug Treder wrote:
and I know that locale knows what formatting it prefers (such as
day-month-year versus month-day-year abbreviations). But is there an
less verbose way to pull it out than this:
$dt-strftime($dt-locale-date_formats-{'medium'});
I was hoping for
0.06 2003-12-08
- The DateTime::Locale docs now includes docs for all the methods that
a locale object has.
No notable code changes.
-dave
/*===
House Absolute Consulting
www.houseabsolute.com
===*/
On Mon, 8 Dec 2003, Doug Treder wrote:
the object should be able to use the locale it already contains; I
shouldn't have to pass it in. We already have shortcuts for -mdy,
-dmy, -hms so there should be a nice little shortcut for a
locale-aware getter. The presence of the former in the
[ cc'ing this back to the list ]
On Mon, 8 Dec 2003, Mike Schilli wrote:
I'm using your DateTime::TimeZone module extensively right now -- it's
great! Hey, one thing I noticed: How can you determine the time zone of
Arizona, because they don't have daylight savings time there (besides in
the
On Mon, 8 Dec 2003, Doug Treder wrote:
Good point, for example:
$dt = DateTime-now(locale=fr_FR); # france french
print $dt-strftime('%x');
'9 déc. 03'
$dt = DateTime-now(locale=fr_CA); # canadian french
print $dt-strftime('%x');
'03-12-09'
the medium format may or
On Thu, 4 Dec 2003, Anton Berezin wrote:
- if TZ environment variable is not set, TimeZone tries /etc/localtime,
which is present on FreeBSD. Unfortunately, on FreeBSD this file is
*NOT* a symlink to a timezone name, but a FreeBSD-specific binary file
(see tzfile(5) for details);
On Thu, 4 Dec 2003, Mathieu Arnold wrote:
+-le 04/12/2003 10:05 -0600, Dave Rolsky écrivait :
| On Thu, 4 Dec 2003, Anton Berezin wrote:
|
| - even if TZ is set, it is very likely to contain something like CET,
|
| That's not a time zone.
Hum, what is it if not a time zone ?
It's a 3
On Thu, 4 Dec 2003, Thomas Bergmann wrote:
I had the some problem Cannot determine local time zone on W2K.
i dont like to set an additional enviroment variable TZ to find the right
TimeZone on the server, because
perl knows the timezone. gmtime and localtime work fine. So i wrote a
small
On Thu, 4 Dec 2003, Anton Berezin wrote:
Setting your system's time zone to such a thing is asking for trouble.
I really don't know. Three-letter abbreviations are POSIX.1. They
might be obsolete, but they are still supported by most implementations,
and used widely.
POSIX is wrong.
On Thu, 4 Dec 2003, Anton Berezin wrote:
Maybe have a default aliases like certain annoying OS's, to borrow
your expression? As a matter of fact, last time I tried, Linux did the
same thing - understood them. EST actually designates Indianapolis
time - America/Indianapolis and EST are
On Sun, 23 Nov 2003, Joshua Hoblitt wrote:
On Sun, 23 Nov 2003, Dave Rolsky wrote:
This should be relatively simple to do, but I'm sure the current API makes
it easy. Basically, it'd be something like:
(86400 * (Rata Die days) + (seconds) + (leap seconds so far)) * 10_000_000
On Sun, 23 Nov 2003, Todd Lorenz wrote:
Mr. van der Pijll -- Thanks very much; your observations on
Params::Validate do check out on my system. Is running the pure Perl
version of PV considered deprecated, or is there otherwise any reason
why I shouldn't use it?
It's much slower. I just
0.70 Nov 23, 2003
- Any validation call that used a callback leaked memory when using
the XS version. This was introduced in 0.67, when callbacks started
receiving a reference to the parameters as a second argument.
Reported by Eugene van der Pijll.
Since DateTime.pm (and maybe other DateTime
On Sun, 23 Nov 2003 [EMAIL PROTECTED] wrote:
Someone should add that to the developer section on the website. :)
Or even better to the Mailing List section of the website. I'm happy to
make the change in CVS if that would help (pretty sure I still have
access). But someone would have to
On Sun, 23 Nov 2003, Eugene van der Pijll wrote:
Todd Lorenz schreef:
Could someone kindly confirm/debunk this?
Confirmed. It seems that this is a memory leak in
Params::Validate::validate(), possibly connected to optional parameters.
Try upgrading to Params::Validate 0.69.
-dave
On Fri, 21 Nov 2003 [EMAIL PROTECTED] wrote:
Looks like there are some problems with the datetime list archive at
archive.develooper.com, only messages from July 2003 are showing.
I know there is also the nttp.perl.org archive, but unfortunately it
doesn't seem to be threaded (very odd from
On Sun, 16 Nov 2003, Yitzchak Scott-Thoennes wrote:
I assume Perl uses these internally, so if none of them are defined, that
may cause problems.
I think isnan is only used for =. isinf doesn't seem to be used at
all. I think these aren't widely enough available for perl to make
On Sat, 15 Nov 2003, Max Maischein wrote:
PS: I didn't know that this was some hornets nest I stirred up again -
it was just a problem I wanted to solve for myself ...
Almost every facet of DateTime stuff is a hornet's nest. It seems simple
at first, but the deeper you get into it, the
On Sat, 15 Nov 2003, Rick Measham wrote:
1. Create DateTime::TimeZone::Lite.
- This would return a subset of the Olson data that assumed the current
rules extend infinitely in both directions.
- This would not be a prereq, or be installed by DateTime itself.
- I suggest we might make this
501 - 600 of 1076 matches
Mail list logo
