#!/usr/bin/perl -l

use strict;
use warnings;
use Date::Parse;

my $date1 = <<"EOF";
Sat, 7 Jul 12 20:55:04 +0300
EOF
print str2time($date1);

my $date2 = <<"EOF";
Sat, 7 Jul 12 20:55:04 CET
EOF
print str2time($date2);
[download]

Help what?

any sugestions?

:) About what?

I don't know, and I believe most programmers don't, what the correct return value is supposed to be

I get

1341719704
1341690904
[download]

perl -le " use DateTime; print DateTime->new(qw{ month 7 day 7 hour 20
+ minute 55 second 04 year 2012 time_zone GMT } )->epoch(); "
1341694504
[download]

perl -le " use DateTime; print DateTime->new(qw/ month 7 day 7 hour 20
+ minute 55 second 04 year 2012 time_zone CET / )->epoch(); "
1341687304
[download]

thank you

your second result seems to be CEST (-7200 to GMT). does the DateTime automaticly use DST iif the date is within the DST-timespan?
that is also a bit weird because not all CET-Countries may habe DST or am i wrong?

it seems that Date::Parse uses the local time zone then parsing unknwon dates. since iam in CEST the results i got are plausible.

i would consider this behaviour as a bug since the local time zone has nothing to do with the dates to parse.

I would definitely recommend DateTime. It is well done and actively maintained. You can set your locale or use time_zone => 'floating' to ignore time zones. I would also take a look at the slides from Dave Rolsky's DateTime talk (video here). They are handy for understanding why weird things happen with date math.

DateTime automatically uses DST, but only if your date is in a timezone that observes daylight savings.

use 5.010;
use DateTime;
use DateTime::Format::Strptime;

# Choose a datetime in the southern summer.
my $later = DateTime->now(time_zone => 'UTC')->add(months => 6);

# Choose an output format that includes time zone.
$later->set_formatter(DateTime::Format::Strptime->new(pattern => '%F %
+T %z'));

# An abstract time zone; no daylight savings.
say "UTC+10: ",
    $later->clone->set_time_zone('+1000');

# Queensland, Australia does not observe daylight savings.
say "Brisbane: ",
    $later->clone->set_time_zone('Australia/Brisbane');

# But New South Wales does!
say "Sydney: ",
    $later->clone->set_time_zone('Australia/Sydney');
[download]

perl -E'sub Monkey::do{say$_,for@_,do{($monkey=[caller(0)]->[3])=~s{::}{ }and$monkey}}"Monkey say"->Monkey::do'

DateTime automaticly use DST iif the date is within the DST-timespan?

Yes, I think so. See How does DST affect day length?

that is also a bit weird because not all CET-Countries may habe DST or am i wrong?

Don't know , don't care, its why I use DateTime. I think this is why you can specify timezone by country ( DateTime::TimeZone:: ) since DST is political concept and DateTime gets this information via olsondb

use DateTime;
my $tz = DateTime::TimeZone->new(qw{ name CET });
printf "%20s %s\n", $_, $tz->$_
    for qw/ is_floating is_utc has_dst_changes is_olson name category 
+/;
__END__
         is_floating 0
              is_utc 0
     has_dst_changes 54
            is_olson 1
                name CET
            category CET
[download]

Which is the CET you want?

i would consider this behaviour as a bug since the local time zone has nothing to do with the dates to parse.

I wouldn't, maybe it needs more explicit mention in the docs, but as a default it does make sense as much as any value (like GMT).

OTOH, I would consider the real bug to be vague timestamps :)

All CET countries use daylight saving, so the results look to be correct. If the function takes no account of what the actual time is, what use is it?