On Friday, July 18, 2003, at 11:20 PM, Ben Bennett wrote:
I am not a big fan of DateTime::Format::Simple either. My best
suggestions are:
DateTime::Format::Basic
Common
Generic
Localized
I'd say it's between Basic and Common. A more accurate n
On Friday, July 18, 2003, at 11:17 PM, Ben Bennett wrote:
- Suggestions of additional formats to parse would be greatly
appreciated
Ooo, and didn't you also forget "now"?
-John
Looks good so far! :)
- Suggestions of additional formats to parse would be greatly
appreciated
...or so you'd think! +/-infinity...pretty please? :)
-John
DateTime::Locale defines 4 lengths for dates and times (full, long,
medium, and short), defines which date format length is the default
one and which time one is the default. It also defines whether the
date preceeds the time or not.
With all of this info, I think it would be nice to be able to
Eugene van der Pijll wrote:
>
> I would prefer if this:
>
> DateTime::Incomplete->new( year => 2003 );
>
> would create the incomplete dt
> 2003-xx-xxTxx:xx:xx; that is: the
> defaults of the DT::I constructor should be
> 'unknown'. That simplifies the creation of DT::I
> objects, and is t
I am not a big fan of DateTime::Format::Simple either. My best
suggestions are:
DateTime::Format::Basic
Common
Generic
Localized
Can anyone come up with anything better?
-ben
Sorry this is such a dense post, but this module spawned a lot of
discussion and deciding what a simple format turned out to be not so
simple. Anyway, if you want to play with this, make sure you look at
the note about regenerating the DT::Locale data.
If people are okay with the general directio
> I don't really see a strong reason to rename the module.
It just feels inconsistent to me. It'll be easier to rename now then after someone is
using it.
-J
--
Flavio S. Glock schreef:
> First release of DateTime::Incomplete !
>
> http://www.ipct.pucrs.br/flavio/perl/DateTime-Incomplete-0.00_01.tar.gz
>
> It is incomplete, of course.
Very much so...
I would prefer if this:
DateTime::Incomplete->new( year => 2003 );
would create the incomplete d
On Fri, 18 Jul 2003, Joshua Hoblitt wrote:
> > > Since much of DT::TZ is being renamed how about changing
> > > DT::TimeZoneCatalog to DT::TimeZone::Catalog? I think it would feel a
> > > little more orthogonal with the other naming conventions.
> >
> > Huh? None of it's being renamed.
>
> You'v
> > Since much of DT::TZ is being renamed how about changing
> > DT::TimeZoneCatalog to DT::TimeZone::Catalog? I think it would feel a
> > little more orthogonal with the other naming conventions.
>
> Huh? None of it's being renamed.
You've renamed a lot of variables. :)
-J
--
Ben Bennett wrote:
> For the name, my thoughts are:
> DT::Partial
> DT::Incomplete
> DT::Reduced
First release of DateTime::Incomplete !
http://www.ipct.pucrs.br/flavio/perl/DateTime-Incomplete-0.00_01.tar.gz
It is incomplete, of course.
- Flavio S. Glock
Hi Arno,
[snipped]
> Dear Sirs
> Please help.
>
> My problem is that when reading data from the Data Base via
> Perl script all extracted dates remain unchanged by
> Perl except dates within Daylight Savings periods.
How are you extracting the dates? Are you using DBI?
Are you using the sql
Ben Bennett wrote:
>
> What were your thoughts on the constructor? I think people expect a
> new, but are unspecified things 0 (like DateTime) or undefined?
new() could be just like DateTime->new,
while whatever() defaults to -xx-xxTxx:xx:xx
> Also, what happens when you compare dates (or i
What were your thoughts on the constructor? I think people expect a
new, but are unspecified things 0 (like DateTime) or undefined?
Also, what happens when you compare dates (or is that simply not
defined?).
Now that I think about it, you will probably need contains,
intersects, etc. But I assu
On Thu, 17 Jul 2003, Joshua Hoblitt wrote:
> Since much of DT::TZ is being renamed how about changing
> DT::TimeZoneCatalog to DT::TimeZone::Catalog? I think it would feel a
> little more orthogonal with the other naming conventions.
Huh? None of it's being renamed.
-dave
/*=
Yes, this is better:
$dtc1->set( month => 12 );
$dtc1->set( month => undef );
It can work without cloning, in order to be compatible with DateTime
API.
Name - how about DateTime::Whatever ? (I like it)
$date = DateTime::Whatever->whatever( year => 2003 );
# 2003-xx-xxTxx:xx:xx
$
I like the idea (this is the partial date & time thing right?) but I
am not too sure about the name... unless you start dealing with times
with real and imaginary parts :-) (Not that I have any suggestions for
a name yet).
Regarding the interface would it be better to have:
--
my $dtc1 = DateTim
PPM choked on Class-Factory-Util when following dependencies and quit to the
c:\ prompt so I had to install it by itself, after which, 'install DateTime'
installed the module and the rest of the dependents without a problem.
Much thanks to you Ron and everyone else who's working on this project.
* Ben Bennett ([EMAIL PROTECTED]) [18 Jul 2003 22:04]:
> Do they call the standard and summer times different things?
> The current DT::TZ stuff and POSIX::strftime and date on
> Linux and Solaris all say EST in January and July... I
> have also seen it given as EAST and EADT (actually I just
> c
RFC: DateTime::Complex
use DateTime;
use DateTime::Complex;
use strict;
my $dtc1 = DateTime::Complex->new_undef;
my $dtc2 = $dtc1->define_month( 12 );
my $christmas = $dtc2->define_day( 24 );
my $december = $christmas->undef_day;
print $december->datetime;
# -12-xxTxx:xx:
Do they call the standard and summer times different things?
The current DT::TZ stuff and POSIX::strftime and date on Linux and
Solaris all say EST in January and July... I have also seen it given
as EAST and EADT (actually I just checked www.worldtimezone.com and it
gives AEST, AES, EAST and EST
Ron, that would make everything so much easyer. Yes I'm using 5.8.0.
Although DateTime was the only one I couldn't get to install.
DateTime::TimeZone and DateTime::LeapSecond went in without a hitch.
--
np
> -Original Message-
> From: Hill, Ronald [mailto:[EMAIL PROTECTED]
> Sent: 17 July
Since much of DT::TZ is being renamed how about changing DT::TimeZoneCatalog to
DT::TimeZone::Catalog? I think it would feel a little more orthogonal with the other
naming conventions.
-J
--
24 matches
Mail list logo
