Free strftime software for linux

Data::Faker::DateTime is a Data::Faker plugin.

DATA PROVIDERS

unixtime

Return a unix time (seconds since the epoch) for a random time between the epoch and now.

date

Return a random date as a string, using a random date format (see date_format).

time

Return a random time as a string, using a random time format (see time_format).

rfc822

Return an RFC 822 formatted random date. This method may not work on systems using a non-GNU strftime implementation (kindly let me know if that is the case.)

ampm

Returns am or pm randomly (in the current locale) using one of the formats specified in ampm_format.

time_format

Return a random time format.

date_format

Return a random date format.

ampm_format

Return a random am/pm format.

datetime_format

Return a random date and time format.

month

Return a random month name, unabbreviated, in the current locale.

month_abbr

Return a random month name, abbreviated, in the current locale.

weekday

Return a random weekday name, unabbreviated, in the current locale.

weekday_abbr

Return a random weekday name, abbreviated, in the current locale.

sqldate

Return a random date in the ISO8601 format commonly used by SQL servers (YYYY-MM-DD).

datetime_locale

Return a datetime string in the preferred date representation for the current locale, for a random date.

date_locale

Return a date string in the preferred date representation for the current locale, for a random date.

time_locale

Return a time string in the preferred date representation for the current locale, for a random date.

century

Return a random century number.

dayofmonth

Return a random day of the month.

DateTime::Precise can perform common time and date operations with additional GPS operations.

SYNOPSIS

use DateTime::Precise;

use DateTime::Precise qw(:TimeVars);

# Constructors and ways to set time.
$t1 = DateTime::Precise->new;
$t2 = DateTime::Precise->new(1998. 4. 3 12:13:44.054);
$t3 = DateTime::Precise->new(time() - 100.23456);
$t4 = DateTime::Precise->new(1998.04.24);
$t1->set_localtime_from_epoch_time;
$t1->set_gmtime_from_epoch_time(time + 120.987);
$t1->set_from_datetime(1998.03.23 16:58:14.65);
$t1->set_time(YDHMS, 1998, 177, 9, 15, 26.5);

# This is the same as $d3->set_from_datetime(...)
$t3->dscanf("%^Y.%M.%D %h:%m:%s", "1998.03.25 20:25:23");
if ($msg = $d1->dscanf("%~M", $input)) {
print "error: $msgn";
print "Must enter a three-letter month abbrev.n";
}

# Get different parts of the time.
$year = $t3->year;
$month = $t3->month;
$day = $t3->day;
$hours = $t3->hours;
$minutes = $t3->minutes;
$seconds = $t3->seconds;
($year, $day_of_year) = $t3->get_time(Yj);

# Print times and dates.
print $t2->asctime;
print $t2->strftime(%T %C%n);
print $t2->dprintf("%^Y.%M.%D %h:%m:%s"); # datetime
print $t2->dprintf("%~w %~M %-D %h:%m:%s CST %^Y"); # ctime

# Copy times.
my $t4 = $t2->copy;

# Set one time object to the same time as another: set $t3 equal to $t2.
$t3->clone($t2);

# Find the difference between two times.
$secs_from_midnight = $t4 - $t1;
$secs_from_midnight = $t4->diff($t1);

# Add seconds, days, months, etc to time.
$t1 = $t4 + 3600; # $t1 is now an hour after midnight
$t1->inc_month(2); # add two months to $t1
$t1->floor_month; # set $t1 to the first of the month
$t1 -= 0.25; # subtract 1/4 of a second from $t1

# Can compare and sort DateTime::Precise.
print "Its late!!!" if ($t1 > $t4);
@sorted = sort @birthdays; # normal comparisons work fine

# Get the GPS weeks, seconds and day.
$gps_week = $t1->gps_week;
$gps_seconds = $t1->gps_seconds;
$gps_day = $t1->gps_day;
($gps_week, $gps_seconds, $gps_day) = $t1->gps_week_seconds_day;

Regexp::Common::time Perl module contains date and time regexps.

SYNOPSIS

use Regexp::Common qw(time);

# Piecemeal, Time::Format-like patterns
$RE{time}{tf}{-pat => pattern}

# Piecemeal, strftime-like patterns
$RE{time}{strftime}{-pat => pattern}

# Match ISO8601-style date/time strings
$RE{time}{iso}

# Fuzzy date patterns
# YEAR/MONTH/DAY
$RE{time}{ymd} # Most flexible
$RE{time}{YMD} # Strictest (equivalent to y4m2d2)
# Other available patterns: y2md, y4md, y2m2d2, y4m2d2

# MONTH/DAY/YEAR (American style)
$RE{time}{mdy} # Most flexible
$RE{time}{MDY} # Strictest (equivalent to m2d2y4)
# Other available patterns: mdy2, mdy4, m2d2y2, m2d2y4

# DAY/MONTH/YEAR (European style)
$RE{time}{mdy} # Most flexible
$RE{time}{MDY} # Strictest (equivalent to d2m2y4)
# Other available patterns: dmy2, dmy4, d2m2y2, d2m2y4

# Fuzzy time pattern
# HOUR/MINUTE/SECOND
$RE{time}{hms} # H: matches 1 or 2 digits; 12 or 24 hours
# M: matches 2 digits.
# S: matches 2 digits; may be omitted
# May be followed by "a", "am", "p.m.", etc.

This module creates regular expressions that can be used for parsing dates and times. See Regexp::Common for a general description of how to use this interface.

Parsing dates is a dirty business. Dates are generally specified in one of three possible orders: year/month/day, month/day/year, and day/month/year. Years can be specified with four digits or with two digits (with assumptions made about the century). Months can be specified as one digit, two digits, as a spelled-out name, or as a three-letter abbreviation. Day numbers can be one digit or two digits, with limits depending on the month (and, in the case of February, even the year). Also, different people use different punctuation for separating the various elements.
A human can easily recognize that "October 21, 2005" and "21.10.05" refer to the same date, but its tricky to get a program to come to the same conclusion. This module attempts to make it possible to do so, with a minimum of difficulty.

If you know the exact format of the data to be matched, use one of the specific, piecemeal pattern builders: tf or strftime. If there is some variability, use one of the fuzzy-matching patterns in the dmy, mdy, or ymd families. If the data are wildly variable, such as raw user input, give up and use the Date::Manip or Date::Parse module.

Time values are generally much simpler to parse than date values. Only one fuzzy pattern is provided, and it should suffice for most needs.

Tk::Date is a date/time widget for perl/Tk.

SYNOPSIS

use Tk::Date;
$date_widget = $top->Date->pack;
$date_widget->get("%x %X");

Tk::Date implements a date/time widget. There are three ways to input a date:
Using the keyboard to input the digits and the tab key or the mouse pointer to move focus between fields.

Using up and down cursor keys to increment/decrement the date (only with installed Tk::NumEntryPlain widget).

Selecting up and down arrow buttons will increment or decrement the value of the active field (only with installed Tk::FireButton widget).

The Date/Time Format

Unlike Java, Perl does not have a date/time object. However, it is possible to use the unix time (seconds since epoch, that is 1st January 1970) as a replacement. This is limited, since on most architectures, the valid range is between 14th December 1901 and 19th January 2038. For other dates, it is possible to use a hash notation:

{ y => year,
m => month,
d => day,
H => hour,
M => minute,
S => second }

The abbreviations are derivated from the format letters of strftime. Note that year is the full year (1998 instead of 98) and month is the real month number, as opposed to the output of localtime(), where the month is subtracted by one.

In this document, the first method will be referred as unixtime and the second method as datehash.

STANDARD OPTIONS

Tk::Date descends from Frame and inherits all of its options.

-orient

Specified orientation of the increment and decrements buttons. May be vertical (default) or horizontal.

DateTime::Format::Strptime is a Perl module to parse and format strp and strf time patterns.

SYNOPSIS

use DateTime::Format::Strptime;

my $Strp = new DateTime::Format::Strptime(
pattern => %T,
locale => en_AU,
time_zone => Australia/Melbourne,
);

my $dt = $Strp->parse_datetime(23:16:42);

$Strp->format_datetime($dt);
# 23:16:42



# Croak when things go wrong:
my $Strp = new DateTime::Format::Strptime(
pattern => %T,
locale => en_AU,
time_zone => Australia/Melbourne,
on_error => croak,
);

$newpattern = $Strp->pattern(%Q);
# Unidentified token in pattern: %Q in %Q at line 34 of script.pl

# Do something else when things go wrong:
my $Strp = new DateTime::Format::Strptime(
pattern => %T,
locale => en_AU,
time_zone => Australia/Melbourne,
on_error => &phone_police,
);

This module implements most of strptime(3), the POSIX function that is the reverse of strftime(3), for DateTime. While strftime takes a DateTime and a pattern and returns a string, strptime takes a string and a pattern and returns the DateTime object associated.

Test::Reporter::Date::Format Perl module contains date formating subroutines.

SYNOPSIS

use Test::Reporter::Date::Format;

@lt = localtime(time);

print time2str($template, time);
print strftime($template, @lt);

print time2str($template, time, $zone);
print strftime($template, @lt, $zone);

print ctime(time);
print asctime(@lt);

print ctime(time, $zone);
print asctime(@lt, $zone);

This module provides routines to format dates into ASCII strings. They correspond to the C library routines strftime and ctime.

time2str(TEMPLATE, TIME [, ZONE])

time2str converts TIME into an ASCII string using the conversion specification given in TEMPLATE. ZONE if given specifies the zone which the output is required to be in, ZONE defaults to your current zone.

strftime(TEMPLATE, TIME [, ZONE])

strftime is similar to time2str with the exception that the time is passed as an array, such as the array returned by localtime.

ctime(TIME [, ZONE])

ctime calls time2str with the given arguments using the conversion specification "%a %b %e %T %Yn"

asctime(TIME [, ZONE])

asctime calls time2str with the given arguments using the conversion specification "%a %b %e %T %Yn"

orbitclock displays a small circular representation of a clock in a pseudo-Star-Trek style.

Nifty little Star-Trek-ish clock display. Resizable, but some of the parameters in the code may need to be tweaked to make it look good at other sizes.

Feel free to play with the parameters at the top of draw() and the colors. Let me know if you get something niftier.

Usage:

orbitclock [options]
-geometry WxH[+X+Y] set window geometry
-bg < color name > background color
-fg < color name > foreground 1 color (tick)
-fg2 < color name > foreground 2 color (block)
-rings < hms|smh|etc. > ordering of rings from inside out (default hms)
-font < font > font to use for date (implies -date)
-date[=optional format] draw date in center, strftime format string literal n causes line break example: -date="%m/%d/%Yn%H:%M:%S" equals sign is REQUIRED, dont ask me why.

AxKit::XSP::ESQL is an Extended SQL taglib for AxKit eXtensible Server Pages.

SYNOPSIS

Add the esql: namespace to your XSP < xsp:page > tag:

< xsp:page
language="Perl"
xmlns:xsp="http://apache.org/xsp/core/v1"
xmlns:esql="http://apache.org/xsp/SQL/v2"
>

And add this taglib to AxKit (via httpd.conf or .htaccess):

AxAddXSPTaglib AxKit::XSP::ESQL

This tag library provides extensive support for executing SQL statements from within XSP. This tag library is the same as the Cocoon ESQL taglib.

TAG REFERENCE

Note that below we use the esql: prefix as a convention, however you can use whatever prefix you like provided it is mapped to the appropriate namespace.

< esql:connection>

parent: none

This is the required wrapper element that declares your connection.

< esql:driver>

parent: < esql:connection>

The contents of this element define the DBI driver to be used. For example, Pg, Sybase, Oracle.

You can also add an optional attribute: transactions=no to the driver element, to indicate that this driver does not support transactions (or just that you dont want to use transactions).

< esql:dburl>

parent: < esql:connection>

The name of this tag is a hang-over from the Cocoon (Java) version. In the AxKit version this is simply anything that goes after the driver in the connection string. So for PostgreSQL you might have in here dbname=axkit, to connect to the "axkit" database. The full connect string is constructed as follows:

"dbi:$driver" . ($dburl ? ":$dburl" : "")

See your DBD driver documentation for more details on what is valid for the connection string.

< esql:username>

parent: < esql:connection>

The username to connect to the database with.

< esql:password>

parent: < esql:connection>

The password to use to connect to the database.

< esql:execute-query>

parent: < esql:connection>

This tag is a wrapper tag around queries. You may have as many queries as you like within a single < esql:connection> tag.

< esql:skip-rows>

parent: < esql:execute-query>

The contents of this tag (which may be an < xsp:expr>) define a number of rows to skip forward in the result set.

< esql:max-rows>

parent: < esql:execute-query>

The maximum number of rows to return.

< esql:query>

parent: < esql:execute-query>

The contents of this tag define the query to be executed.

< esql:parameter>

parent: < esql:query>

This tag can be put in your SQL query everywhere you might put a ? in your SQL in DBI. ESQL is intelligent enough to create a cached statement when you do this, and only execute your code when necessary. You put an expression (or another taglib) within the parameter tag (see the example below).

< esql:results>

parent: < esql:execute-query>

The contents of this tag are "executed" whenever the query returns some results.

< esql:row-results>

parent: < esql:results>

The contents of this tag are "executed" for each row of the results

< esql:get-columns>

parent: < esql:row-results>

This tag gets all of the columns in the current row, and outputs them as < column_name>value< /column_name>. If you specify an attribute tag-case="upper", all columns are upper case. Alternatively, "lower" gives you all tags in lower case. An ancestor attribute is also allowed, see "Nested Results" below for more details.
get-*

parent: < esql:row-results>

These are:

get-column
get-string
get-boolean
get-double
get-float
get-int
get-long
get-short
(and more below)

Each of these takes either an attribute column="name", or a child tag, < esql:column> which gives the column name. Alternatively either the attribute or child element can be an integer (starting at 1) specifying the column number.
Also allowed is an ancestor attribute, which is an integer (default 0), which indicates how far up the nested results you go. See Nested Results below.

< esql:get-date>, < esql:get-time>, < esql:get-timestamp>

parent: < esql:row-results>

These tags are the same as get-* above, except they also take a format="..." attribute, which contains a strftime formatting string.

< esql:get-xml>

parent: < esql:row-results>

Again the same as get-* above. This tag assumes the contents of the column are valid XML, and appends that XML into the result tree.

< esql:get-row-position>

parent: < esql:row-results>

Gets the current row number. Optional ancestor attribute.

< esql:get-column-name>

parent: < esql:row-results>

Gets the column name indicated by the numbered column in the column="..." attribute, or the child < esql:column> element. The attribute/child can actually be a string (name), but then what is the point of that?

< esql:get-column-label>

parent: < esql:row-results>

Gets the label of the column. This is a hang-over from the Cocoon java implementation where sadly nobody seems to know what label is compared with name. In this case, get-column-name is always lower case, whereas get-column-label is returned in the case that the DBD driver returns it as.

< esql:get-column-type-name>

parent: < esql:row-results>

Returns the TYPE_NAME of the column indicated as other get-* elements. See the DBI docs for more details.

< esql:no-results>

parent: < esql:execute-query>

The contents of this element are executed when the SQL returned no rows.

< esql:update-results>

parent: < esql:execute-query>

The contents of this element are executed when the SQL was an update statement. The number of rows updated are in the $rv variable.