view release on metacpan or search on metacpan
lib/Latin4.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Latin5.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Latin6.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Latin7.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Latin8.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Latin9.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/OldUTF8.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Sjis.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/TIS620.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/USASCII.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/UTF2.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Windows1252.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Windows1258.pm view on Meta::CPAN
    |  UTF-8   |  Latin-1  |                     |
    +----------+-----------+---------------------+
    | UTF8     |            Not UTF8             |
    | Flagged  |            Flagged              |
    +--------------------------------------------+
    http://perl-users.jp/articles/advent-calendar/2010/casual/4
  Confusion of Perl string model is made from double meanings of
  "Binary string."
  Meanings of "Binary string"
  1. Non-Text string
view release on metacpan or search on metacpan
lib/Chart/Plotly/Trace/Bar.pm view on Meta::CPAN
    is            => "rw",
    documentation =>
      "Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.",
);
has xcalendar => ( is  => "rw",
                   isa => enum(
                           [ "chinese", "coptic", "discworld",  "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
                             "julian",  "mayan",  "nanakshahi", "nepali",    "persian",   "taiwan", "thai", "ummalqura"
                           ]
                   ),
                   documentation => "Sets the calendar system to use with `x` date data.",
);
has xhoverformat => (
    is            => "rw",
    isa           => "Str",
lib/Chart/Plotly/Trace/Bar.pm view on Meta::CPAN
    is            => "rw",
    documentation =>
      "Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.",
);
has ycalendar => ( is  => "rw",
                   isa => enum(
                           [ "chinese", "coptic", "discworld",  "ethiopian", "gregorian", "hebrew", "islamic", "jalali",
                             "julian",  "mayan",  "nanakshahi", "nepali",    "persian",   "taiwan", "thai", "ummalqura"
                           ]
                   ),
                   documentation => "Sets the calendar system to use with `y` date data.",
);
has yhoverformat => (
    is            => "rw",
    isa           => "Str",
lib/Chart/Plotly/Trace/Bar.pm view on Meta::CPAN
=item * xaxis
Sets a reference between this trace's x coordinates and a 2D cartesian x axis. If *x* (the default value), the x coordinates refer to `layout.xaxis`. If *x2*, the x coordinates refer to `layout.xaxis2`, and so on.
=item * xcalendar
Sets the calendar system to use with `x` date data.
=item * xhoverformat
Sets the hover text formatting rulefor `x`  using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format...
lib/Chart/Plotly/Trace/Bar.pm view on Meta::CPAN
=item * yaxis
Sets a reference between this trace's y coordinates and a 2D cartesian y axis. If *y* (the default value), the y coordinates refer to `layout.yaxis`. If *y2*, the y coordinates refer to `layout.yaxis2`, and so on.
=item * ycalendar
Sets the calendar system to use with `y` date data.
=item * yhoverformat
Sets the hover text formatting rulefor `y`  using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format...
view release on metacpan or search on metacpan
t/datadir/bannertest view on Meta::CPAN
tftp client source-interface Loopback0
ntp
 server 100.2.3.12
 source Loopback0
 access-group peer 4
 update-calendar
!
ipv4 access-list 3
 10 permit ipv4 100.2.3.0 0.0.0.31 any
 20 permit ipv4 110.2.3.0 0.0.0.31 any
 30 permit ipv4 120.2.3.0 0.0.0.255 any
view release on metacpan or search on metacpan
lib/Class/DBI/Plugin/Calendar.pm view on Meta::CPAN
	
	my $caller = caller();
	no strict 'refs';
		# add some SQL to the calling class, as requested
	$caller->set_sql(calendar => <<"");
		SELECT *
		FROM __TABLE__
		%s
		ORDER BY `$date_field`
		# add the calendar method to the calling class
	*{"$caller\::calendar"} = sub {
		my($class,$month,$year,$mondays) = @_;
			# generate default values if necessary
		unless($month and $year) {
			my @lt = localtime;
lib/Class/DBI/Plugin/Calendar.pm view on Meta::CPAN
			# mysql required (for now?)
		my $where = qq[ WHERE MONTH(`$date_field`) = '$month' AND YEAR(`$date_field`) = '$year' ];
			# get the objects which are within the chosen month
		my @objects = $class->sth_to_objects($class->sql_calendar($where));
			
			# get the calendar layout for this month
			# map the dates to day objects:
			#
		my @weeks = Calendar::Simple::calendar($month,$year,$mondays);
		for my $week (@weeks) {
			for my $day (@$week) {
				$day ||= 0;
				my @events = ();
				while(@objects and $objects[0]->$date_field->mday == $day) {
lib/Class/DBI/Plugin/Calendar.pm view on Meta::CPAN
  package DB;
  use base 'Class::DBI';
  use Class::DBI::Plugin::Calendar qw(date_fieldname);
  # the same as Calendar::Simple::calendar
  my @curr      = DB->calendar;             # get current month
  my @this_sept = DB->calendar(9);          # get 9th month of current year
  my @sept_2002 = DB->calendar(9, 2002);    # get 9th month of 2002
  my @monday    = DB->calendar(9, 2002, 1); # week starts with Monday
=head1 DESCRIPTION
Please note that this module only works with mysql at this point, as 
far as I know. Retrieve the objects in useful calendar-like data 
structures, similar to Calendar::Simple.
=head2 my @weeks = calendar([$month,$year,$monday])
@weeks holds arefs of 7 days each (there are dummy placeholders where needed), 
which are represented by Class::DBI::Plugin::Calendar::Day objects. Please
refer to the Class::DBI::Plugin::Calendar::Day perldoc for instructions.
view release on metacpan or search on metacpan
lib/Class/Date.pm view on Meta::CPAN
A Class::Date object is an array reference.
A Class::Date::Rel object is an array reference, which contains month and
second information. I need to store it as an array ref, because array and month
values cannot be converted into seconds, because of our super calendar.
You can add code references to the @Class::Date::NEW_FROM_SCALAR and
@Class::Date::Rel::NEW_FROM_SCALAR. These arrays are iterated through when a
scalar-format date must be parsed. These arrays only have one or two values
at initialization. The parameters which the code references got are the same 
view release on metacpan or search on metacpan
examples/helloworld/htdocs/dwarf/bootstrap/css/bootstrap.css view on Meta::CPAN
  content: "\e107";
}
.glyphicon-plane:before {
  content: "\e108";
}
.glyphicon-calendar:before {
  content: "\e109";
}
.glyphicon-random:before {
  content: "\e110";
}
view release on metacpan or search on metacpan
share/js/jquery-ui-1.11.4.js view on Meta::CPAN
		}
	},
	/* Tidy up after a dialog display. */
	_tidyDialog: function(inst) {
		inst.dpDiv.removeClass(this._dialogClass).unbind(".ui-datepicker-calendar");
	},
	/* Close date picker if clicked elsewhere. */
	_checkExternalClick: function(event) {
		if (!$.datepicker._curInst) {
share/js/jquery-ui-1.11.4.js view on Meta::CPAN
				calender += "<div class='ui-datepicker-header ui-widget-header ui-helper-clearfix" + cornerClass + "'>" +
					(/all|left/.test(cornerClass) && row === 0 ? (isRTL ? next : prev) : "") +
					(/all|right/.test(cornerClass) && row === 0 ? (isRTL ? prev : next) : "") +
					this._generateMonthYearHeader(inst, drawMonth, drawYear, minDate, maxDate,
					row > 0 || col > 0, monthNames, monthNamesShort) + // draw month headers
					"</div><table class='ui-datepicker-calendar'><thead>" +
					"<tr>";
				thead = (showWeek ? "<th class='ui-datepicker-week-col'>" + this._get(inst, "weekHeader") + "</th>" : "");
				for (dow = 0; dow < 7; dow++) { // days of the week
					day = (dow + firstDay) % 7;
					thead += "<th scope='col'" + ((dow + firstDay + 6) % 7 >= 5 ? " class='ui-datepicker-week-end'" : "") + ">" +
share/js/jquery-ui-1.11.4.js view on Meta::CPAN
 * Bind hover events for datepicker elements.
 * Done via delegate so the binding only occurs once in the lifetime of the parent div.
 * Global datepicker_instActive, set by _updateDatepicker allows the handlers to find their way back to the active picker.
 */
function datepicker_bindHover(dpDiv) {
	var selector = "button, .ui-datepicker-prev, .ui-datepicker-next, .ui-datepicker-calendar td a";
	return dpDiv.delegate(selector, "mouseout", function() {
			$(this).removeClass("ui-state-hover");
			if (this.className.indexOf("ui-datepicker-prev") !== -1) {
				$(this).removeClass("ui-datepicker-prev-hover");
			}
share/js/jquery-ui-1.11.4.js view on Meta::CPAN
		.delegate( selector, "mouseover", datepicker_handleMouseover );
}
function datepicker_handleMouseover() {
	if (!$.datepicker._isDisabledDatepicker( datepicker_instActive.inline? datepicker_instActive.dpDiv.parent()[0] : datepicker_instActive.input[0])) {
		$(this).parents(".ui-datepicker-calendar").find("a").removeClass("ui-state-hover");
		$(this).addClass("ui-state-hover");
		if (this.className.indexOf("ui-datepicker-prev") !== -1) {
			$(this).addClass("ui-datepicker-prev-hover");
		}
		if (this.className.indexOf("ui-datepicker-next") !== -1) {
view release on metacpan or search on metacpan
share/web/static/css/main.css view on Meta::CPAN
@import "yui/grids/grids-min.css";
@import "app-base.css";
@import "base.css";
@import "nav.css";
@import "context-menus.css";
@import "calendar.css";
@import "combobox.css";
@import "keybindings.css";
@import "forms.css";
@import "halos.css";
@import "app.css";
@import "autocomplete.css";
@import "yui/calendar/calendar.css";
@import "notices.css";
view release on metacpan or search on metacpan
t/large.conf view on Meta::CPAN
    SetEnv DB_HOST ""
    SetEnv DB_USER "postgres"
    SetEnv DB_PASS ""
    SetEnv DB_CLIENT "ops@about-inc.com"
    SetEnv DB_CALENDAR "testcal"
    SetENV CAL_PUB_DIR "/mnt/output/tools/calendar/" 
  Options FollowSymLinks ExecCGI
  <Directory /mnt/www/tools/cal>
    AllowOverride None
    Options ExecCGI Includes
    Order allow,deny
view release on metacpan or search on metacpan
Debian_CPANTS.txt view on Meta::CPAN
"libcache-cache-perl", "Cache-Cache", "1.05", "0", "0"
"libcache-fastmmap-perl", "Cache-FastMmap", "1.28", "0", "0"
"libcache-memcached-perl", "Cache-Memcached", "1.24", "0", "0"
"libcache-mmap-perl", "Cache-Mmap", "0.11", "0", "0"
"libcache-simple-timedexpiry-perl", "Cache-Simple-TimedExpiry", "0.27", "0", "1"
"libcalendar-simple-perl", "Calendar-Simple", "1.20", "0", "0"
"libcarp-assert-more-perl", "Carp-Assert-More", "1.12", "0", "0"
"libcarp-assert-perl", "Carp-Assert", "0.20", "0", "0"
"libcarp-clan-perl", "Carp-Clan", "6.00", "0", "0"
"libcarp-datum-perl", "Carp-Datum", "0.1.3", "0", "0"
"libcddb-file-perl", "CDDB-File", "not-uploaded", "0", "0"
Debian_CPANTS.txt view on Meta::CPAN
"libsys-syslog-perl", "Sys-Syslog", "0.26", "0", "1"
"libsys-utmp-perl", "Sys-Utmp", "1.6", "0", "1"
"libsysadm-install-perl", "Sysadm-Install", "0.27", "0", "0"
"libtemplate-declare-perl", "Template-Declare", "0.28", "0", "1"
"libtemplate-multilingual-perl", "Template-Multilingual", "0.09", "0", "0"
"libtemplate-plugin-calendar-simple-perl", "Template-Plugin-Calendar-Simple", "0.02", "0", "0"
"libtemplate-plugin-class-perl", "Template-Plugin-Class", "0.13", "0", "0"
"libtemplate-plugin-clickable-perl", "Template-Plugin-Clickable", "0.06", "0", "0"
"libtemplate-plugin-number-format-perl", "Template-Plugin-Number-Format", "not-uploaded", "0", "0"
"libtemplate-plugin-textile2-perl", "Template-Plugin-Textile2", "1.21", "0", "0"
"libtemplate-plugin-yaml-perl", "Template-Plugin-YAML", "1.22", "0", "0"
view release on metacpan or search on metacpan
lib/Config/Model/models/Systemd/Section/Timer.pl view on Meta::CPAN
Multiple directives may be combined of the same and of different types, in which case the timer
unit will trigger whenever any of the specified timer expressions elapse. For example, by combining
C<OnBootSec> and C<OnUnitActiveSec>, it is possible to define a
timer that elapses in regular intervals and activates a specific service each time. Moreover, both
monotonic time expressions and C<OnCalendar> calendar expressions may be combined in
the same timer unit.
The arguments to the directives are time spans
configured in seconds. Example: "OnBootSec=50" means 50s after
boot-up. The argument may also include time units. Example:
lib/Config/Model/models/Systemd/Section/Timer.pl view on Meta::CPAN
Multiple directives may be combined of the same and of different types, in which case the timer
unit will trigger whenever any of the specified timer expressions elapse. For example, by combining
C<OnBootSec> and C<OnUnitActiveSec>, it is possible to define a
timer that elapses in regular intervals and activates a specific service each time. Moreover, both
monotonic time expressions and C<OnCalendar> calendar expressions may be combined in
the same timer unit.
The arguments to the directives are time spans
configured in seconds. Example: "OnBootSec=50" means 50s after
boot-up. The argument may also include time units. Example:
lib/Config/Model/models/Systemd/Section/Timer.pl view on Meta::CPAN
Multiple directives may be combined of the same and of different types, in which case the timer
unit will trigger whenever any of the specified timer expressions elapse. For example, by combining
C<OnBootSec> and C<OnUnitActiveSec>, it is possible to define a
timer that elapses in regular intervals and activates a specific service each time. Moreover, both
monotonic time expressions and C<OnCalendar> calendar expressions may be combined in
the same timer unit.
The arguments to the directives are time spans
configured in seconds. Example: "OnBootSec=50" means 50s after
boot-up. The argument may also include time units. Example:
lib/Config/Model/models/Systemd/Section/Timer.pl view on Meta::CPAN
Multiple directives may be combined of the same and of different types, in which case the timer
unit will trigger whenever any of the specified timer expressions elapse. For example, by combining
C<OnBootSec> and C<OnUnitActiveSec>, it is possible to define a
timer that elapses in regular intervals and activates a specific service each time. Moreover, both
monotonic time expressions and C<OnCalendar> calendar expressions may be combined in
the same timer unit.
The arguments to the directives are time spans
configured in seconds. Example: "OnBootSec=50" means 50s after
boot-up. The argument may also include time units. Example:
lib/Config/Model/models/Systemd/Section/Timer.pl view on Meta::CPAN
Multiple directives may be combined of the same and of different types, in which case the timer
unit will trigger whenever any of the specified timer expressions elapse. For example, by combining
C<OnBootSec> and C<OnUnitActiveSec>, it is possible to define a
timer that elapses in regular intervals and activates a specific service each time. Moreover, both
monotonic time expressions and C<OnCalendar> calendar expressions may be combined in
the same timer unit.
The arguments to the directives are time spans
configured in seconds. Example: "OnBootSec=50" means 50s after
boot-up. The argument may also include time units. Example:
lib/Config/Model/models/Systemd/Section/Timer.pl view on Meta::CPAN
      {
        'cargo' => {
          'type' => 'leaf',
          'value_type' => 'uniline'
        },
        'description' => 'Defines realtime (i.e. wallclock) timers with calendar event expressions. See
L<systemd.time(7)> for
more information on the syntax of calendar event expressions. Otherwise, the semantics are similar to
C<OnActiveSec> and related settings.
Note that timers do not necessarily expire at the precise time configured with this setting, as
it is subject to the C<AccuracySec> setting below.
May be specified more than once, in which case the timer unit will trigger whenever any of the
specified expressions elapse. Moreover, calendar timers and monotonic timers (see above) may be
combined within the same timer unit.
If the empty string is assigned to any of these options, the list of timers is reset (both
C<OnCalendar> timers and monotonic timers, see above), and all prior assignments
will have no effect.
Note that calendar timers might be triggered at unexpected times if the system\'s realtime clock
is not set correctly. Specifically, on systems that lack a battery-buffered Realtime Clock (RTC) it
might be wise to enable C<systemd-time-wait-sync.service> to ensure the clock is
adjusted to a network time source before the timer event is set up. Timer units
with at least one C<OnCalendar> expression are automatically ordered after
C<time-sync.target>, which C<systemd-time-wait-sync.service> is
ordered before.
When a system is temporarily put to sleep (i.e. system suspend or hibernation) the realtime
clock does not pause. When a calendar timer elapses while the system is sleeping it will not be acted
on immediately, but once the system is later resumed it will catch up and process all timers that
triggered while the system was sleeping. Note that if a calendar timer elapsed more than once while
the system was continuously sleeping the timer will only result in a single service activation. If
C<WakeSystem> (see below) is enabled a calendar time event elapsing while the system
is suspended will cause the system to wake up (under the condition the system\'s hardware supports
time-triggered wake-up functionality).',
        'type' => 'list'
      },
      'AccuracySec',
view release on metacpan or search on metacpan
lib/Config/OpenSSH/Authkey.pm view on Meta::CPAN
=back
Rotating C<authorized_keys> data is difficult, as the entries contain
no date related metadata like X.509 certificates do. Solutions would be
to schedule a yearly calendar event during which all the keys are
rotated, or maintain the keys in a database that includes a creation
date field on the record.
=head1 CLASS METHODS
view release on metacpan or search on metacpan
tests/include/pdclib/functions/time/ctime.c view on Meta::CPAN
#ifndef REGTEST
char * ctime( const time_t * timer )
{
    /* Section 4.12.3.2 of X3.159-1989 requires that
        The ctime function converts the calendar time pointed to by timer
        to local time in the form of a string. It is equivalent to
            asctime(localtime(timer))
    */
    struct tm * tmp = localtime( timer );
    return tmp ? asctime( tmp ) : NULL;
view release on metacpan or search on metacpan
bin/soap/Ethiopic/Convert.pm view on Meta::CPAN
__END__
=head1 NAME
Ethiopic::Time - conversions of calendar systems to/from Ethiopic and Gregorian.
=head1 SYNOPSIS
  use LiveGeez::Request;
  require Convert::Ethiopic::Time;
view release on metacpan or search on metacpan
include/bearssl_x509.h view on Meta::CPAN
 *
 * The function receives as parameter an arbitrary user-provided context,
 * and the notBefore and notAfter dates specified in an X.509 certificate,
 * both expressed as a number of days and a number of seconds:
 *
 *   - Days are counted in a proleptic Gregorian calendar since
 *     January 1st, 0 AD. Year "0 AD" is the one that preceded "1 AD";
 *     it is also traditionally known as "1 BC".
 *
 *   - Seconds are counted since midnight, from 0 to 86400 (a count of
 *     86400 is possible only if a leap second happened).
include/bearssl_x509.h view on Meta::CPAN
 * \brief Set the validation time for the X.509 "minimal" engine.
 *
 * The validation time is set as two 32-bit integers, for days and
 * seconds since a fixed epoch:
 *
 *   - Days are counted in a proleptic Gregorian calendar since
 *     January 1st, 0 AD. Year "0 AD" is the one that preceded "1 AD";
 *     it is also traditionally known as "1 BC".
 *
 *   - Seconds are counted since midnight, from 0 to 86400 (a count of
 *     86400 is possible only if a leap second happened).
include/bearssl_x509.h view on Meta::CPAN
 * platform, then the current time will automatically be used. Otherwise,
 * not setting the validation date and time implies a validation
 * failure (except in case of direct trust of the EE key).
 *
 * \param ctx       validation context.
 * \param days      days since January 1st, 0 AD (Gregorian calendar).
 * \param seconds   seconds since midnight (0 to 86400).
 */
static inline void
br_x509_minimal_set_time(br_x509_minimal_context *ctx,
	uint32_t days, uint32_t seconds)
view release on metacpan or search on metacpan
lib/Crypt/HSXKPasswd/Dictionary/ES.pm view on Meta::CPAN
    'calefacción',
    'calefactor',
    'calefactores',
    'calemos',
    'calen',
    'calendario',
    'calendarios',
    'calentaba',
    'calentaban',
    'calentada',
    'calentadas',
    'calentado',
view release on metacpan or search on metacpan
lib/Crypt/XkcdPassword/Words/EN.pm view on Meta::CPAN
d'angelo
cursed
controlled
content
combat
calendar
brutal
bing
bette
assets
warlocks