Ovid

#!/usr/bin/env perl

use v5.14.0;
use warnings;
use JSON::PP qw(decode_json);
use Data::Dumper;
use Getopt::Long;

GetOptions(
    'perl'    => \my $perl,

Ovid

#!/usr/bin/env perl

use v5.20;
use warnings;
use lib 'lib';
use WebService::OpenSky;
use Geo::ICAO 'code2airport';
use Text::CSV_XS 'csv';
use File::Temp 'tempfile';
use Mojo::UserAgent;

Ovid

#!/usr/bin/env perl

# See also: https://fosstodon.org/@ovid/109745522656272671
# See also: https://priceonomics.com/the-time-everyone-corrected-the-worlds-smartest/

use Less::Boilerplate;

# $does_switch = 0 means they don't switch doors
# $does_switch = 1 means they do switch doors
my $does_switch = 0;

Ovid

Data Types in Perl

This document is to open discussion about what it takes to create an optional, native data type constraint system for Perl. It it not about building a type system.

In the book Types and Programming Languages by Benjamin Pierce, he writes:

Ovid

# RedBlack tree mockup for Corinna, modeled after https://metacpan.org/pod/Tree::RedBlack
# It is not guaranteed to work

use feature 'class';

# we really want this to be a private class, but we can't yet
class RedBlack::Node {
    field $key    :reader :writer :param { undef };
    field $value  :reader :writer :param { undef };
    field $parent :reader :writer :param { undef };

Ovid

UPDATE

This document now resides at https://github.com/Ovid/Cor/blob/master/pod/perlclasstut.pod

Ovid

# I needed to sure I was operating on pristine test databases
# every time my code called $test->schema (DBIx::Class and Test::Class::Moose).
# This handles that for me
package TestsFor::SeKreT {
    use Test::Class::Moose;
    use Less::Boilerplate; # gives me a sane version of Perl
    use File::Copy qw(copy);
    use File::Spec::Functions qw(catfile);
    use SeKreT::Util::Data qw(
      make_slug

Ovid

Preface

This is something that likely cannot be made into an RFC for the Perl language at this time because implementation would be greatly simplified when the Corinna object model is in core. For example, a base class for what is discussed might look like the following:

# Exception is a poor name for warnings, so a better name is warranted
class Exception :version(v0.1.0) {
    # $message and $description might be from a messaging role
    field $message     :reader :param;
    field $description :reader :param { "" };

Ovid

#!/usr/bin/env perl

# I decided it was time to learn PPR::X (Damian Conway's excellent regex-based Perl parser)
# 
# This code is still heuristic in nature, but the challenge seemd fun.
#
# I thought it would be an interesting project to try to extract dependencies from
# Perl code. Thanks to `haj` giving me the clue needed to find a parsing error

use strict;

Ovid

class Counter {
    # My::Cor::Attributes is using some hypothetical
    # tool to extend Cor attributes. Because it's a
    # `use` statement, it happens at compile time
    use My::Cor::Attributes ':isa';
    has $count :reader :new :isa(PositiveInt) = 0;
    
    method inc () { $count++ }
    method dec () { $count-- unless 0 == $count }
}