RubyGems - javonet-ruby-sdk - Versions diffs - 2.4.9 → 2.4.11 - Mend

javonet-ruby-sdk 2.4.9 → 2.4.11

Files changed (1457) hide show

data/lib/javonet-ruby-sdk/Binaries/Perl/MacOs/X64/deps/lib/perl5/darwin-thread-multi-2level/Moose/Manual/Unsweetened.pod DELETED Viewed

@@ -1,386 +0,0 @@
-# PODNAME: Moose::Manual::Unsweetened
-# ABSTRACT: Moose idioms in plain old Perl 5 without the sugar
-__END__
-=pod
-=encoding UTF-8
-=head1 NAME
-Moose::Manual::Unsweetened - Moose idioms in plain old Perl 5 without the sugar
-=head1 VERSION
-version 2.2207
-=head1 DESCRIPTION
-If you're trying to figure out just what the heck Moose does, and how
-it saves you time, you might find it helpful to see what Moose is
-I<really> doing for you. This document shows you the translation from
-Moose sugar back to plain old Perl 5.
-=head1 CLASSES AND ATTRIBUTES
-First, we define two very small classes the Moose way.
-  package Person;
-  use DateTime;
-  use DateTime::Format::Natural;
-  use Moose;
-  use Moose::Util::TypeConstraints;
-  has name => (
-      is       => 'rw',
-      isa      => 'Str',
-      required => 1,
-  );
-  # Moose doesn't know about non-Moose-based classes.
-  class_type 'DateTime';
-  my $en_parser = DateTime::Format::Natural->new(
-      lang      => 'en',
-      time_zone => 'UTC',
-  );
-  coerce 'DateTime'
-      => from 'Str'
-      => via { $en_parser->parse_datetime($_) };
-  has birth_date => (
-      is      => 'rw',
-      isa     => 'DateTime',
-      coerce  => 1,
-      handles => { birth_year => 'year' },
-  );
-  enum 'ShirtSize' => [qw( s m l xl xxl )];
-  has shirt_size => (
-      is      => 'rw',
-      isa     => 'ShirtSize',
-      default => 'l',
-  );
-This is a fairly simple class with three attributes. We also define an enum
-type to validate t-shirt sizes because we don't want to end up with something
-like "blue" for the shirt size!
-  package User;
-  use Email::Valid;
-  use Moose;
-  use Moose::Util::TypeConstraints;
-  extends 'Person';
-  subtype 'Email'
-      => as 'Str'
-      => where { Email::Valid->address($_) }
-      => message { "$_ is not a valid email address" };
-  has email_address => (
-      is       => 'rw',
-      isa      => 'Email',
-      required => 1,
-  );
-This class subclasses Person to add a single attribute, email address.
-Now we will show what these classes would look like in plain old Perl
-5. For the sake of argument, we won't use any base classes or any
-helpers like C<Class::Accessor>.
-  package Person;
-  use strict;
-  use warnings;
-  use Carp qw( confess );
-  use DateTime;
-  use DateTime::Format::Natural;
-  sub new {
-      my $class = shift;
-      my %p = ref $_[0] ? %{ $_[0] } : @_;
-      exists $p{name}
-          or confess 'name is a required attribute';
-      $class->_validate_name( $p{name} );
-      exists $p{birth_date}
-          or confess 'birth_date is a required attribute';
-      $p{birth_date} = $class->_coerce_birth_date( $p{birth_date} );
-      $class->_validate_birth_date( $p{birth_date} );
-      $p{shirt_size} = 'l'
-          unless exists $p{shirt_size};
-      $class->_validate_shirt_size( $p{shirt_size} );
-      return bless \%p, $class;
-  }
-  sub _validate_name {
-      shift;
-      my $name = shift;
-      local $Carp::CarpLevel = $Carp::CarpLevel + 1;
-      defined $name
-          or confess 'name must be a string';
-  }
-  {
-      my $en_parser = DateTime::Format::Natural->new(
-          lang      => 'en',
-          time_zone => 'UTC',
-      );
-      sub _coerce_birth_date {
-          shift;
-          my $date = shift;
-          return $date unless defined $date && ! ref $date;
-          my $dt = $en_parser->parse_datetime($date);
-          return $dt ? $dt : undef;
-      }
-  }
-  sub _validate_birth_date {
-      shift;
-      my $birth_date = shift;
-      local $Carp::CarpLevel = $Carp::CarpLevel + 1;
-      $birth_date->isa('DateTime')
-          or confess 'birth_date must be a DateTime object';
-  }
-  sub _validate_shirt_size {
-      shift;
-      my $shirt_size = shift;
-      local $Carp::CarpLevel = $Carp::CarpLevel + 1;
-      defined $shirt_size
-          or confess 'shirt_size cannot be undef';
-      my %sizes = map { $_ => 1 } qw( s m l xl xxl );
-      $sizes{$shirt_size}
-          or confess "$shirt_size is not a valid shirt size (s, m, l, xl, xxl)";
-  }
-  sub name {
-      my $self = shift;
-      if (@_) {
-          $self->_validate_name( $_[0] );
-          $self->{name} = $_[0];
-      }
-      return $self->{name};
-  }
-  sub birth_date {
-      my $self = shift;
-      if (@_) {
-          my $date = $self->_coerce_birth_date( $_[0] );
-          $self->_validate_birth_date( $date );
-          $self->{birth_date} = $date;
-      }
-      return $self->{birth_date};
-  }
-  sub birth_year {
-      my $self = shift;
-      return $self->birth_date->year;
-  }
-  sub shirt_size {
-      my $self = shift;
-      if (@_) {
-          $self->_validate_shirt_size( $_[0] );
-          $self->{shirt_size} = $_[0];
-      }
-      return $self->{shirt_size};
-  }
-Wow, that was a mouthful! One thing to note is just how much space the
-data validation code consumes. As a result, it's pretty common for
-Perl 5 programmers to just not bother. Unfortunately, not validating
-arguments leads to surprises down the line ("why is birth_date an
-email address?").
-Also, did you spot the (intentional) bug?
-It's in the C<_validate_birth_date()> method. We should check that
-the value in C<$birth_date> is actually defined and an object before
-we go and call C<isa()> on it! Leaving out those checks means our data
-validation code could actually cause our program to die. Oops.
-Note that if we add a superclass to Person we'll have to change the
-constructor to account for that.
-(As an aside, getting all the little details of what Moose does for
-you just right in this example was really not easy, which emphasizes
-the point of the example. Moose saves you a lot of work!)
-Now let's see User:
-  package User;
-  use strict;
-  use warnings;
-  use Carp qw( confess );
-  use Email::Valid;
-  use Scalar::Util qw( blessed );
-  use parent 'Person';
-  sub new {
-      my $class = shift;
-      my %p = ref $_[0] ? %{ $_[0] } : @_;
-      exists $p{email_address}
-          or confess 'email_address is a required attribute';
-      $class->_validate_email_address( $p{email_address} );
-      my $self = $class->SUPER::new(%p);
-      $self->{email_address} = $p{email_address};
-      return $self;
-  }
-  sub _validate_email_address {
-      shift;
-      my $email_address = shift;
-      local $Carp::CarpLevel = $Carp::CarpLevel + 1;
-      defined $email_address
-          or confess 'email_address must be a string';
-      Email::Valid->address($email_address)
-          or confess "$email_address is not a valid email address";
-  }
-  sub email_address {
-      my $self = shift;
-      if (@_) {
-          $self->_validate_email_address( $_[0] );
-          $self->{email_address} = $_[0];
-      }
-      return $self->{email_address};
-  }
-That one was shorter, but it only has one attribute.
-Between the two classes, we have a whole lot of code that doesn't do
-much. We could probably simplify this by defining some sort of
-"attribute and validation" hash, like this:
-  package Person;
-  my %Attr = (
-      name => {
-          required => 1,
-          validate => sub { defined $_ },
-      },
-      birth_date => {
-          required => 1,
-          validate => sub { blessed $_ && $_->isa('DateTime') },
-      },
-      shirt_size => {
-          required => 1,
-          validate => sub { defined $_ && $_ =~ /^(?:s|m|l|xl|xxl)$/i },
-      }
-  );
-Then we could define a base class that would accept such a definition
-and do the right thing. Keep that sort of thing up and we're well on
-our way to writing a half-assed version of Moose!
-Of course, there are CPAN modules that do some of what Moose does,
-like C<Class::Accessor>, C<Class::Meta>, and so on. But none of them
-put together all of Moose's features along with a layer of declarative
-sugar, nor are these other modules designed for extensibility in the
-same way as Moose. With Moose, it's easy to write a MooseX module to
-replace or extend a piece of built-in functionality.
-Moose is a complete OO package in and of itself, and is part of a rich
-ecosystem of extensions. It also has an enthusiastic community of
-users and is being actively maintained and developed.
-=head1 AUTHORS
-=over 4
-=item *
-Stevan Little <stevan@cpan.org>
-=item *
-Dave Rolsky <autarch@urth.org>
-=item *
-Jesse Luehrs <doy@cpan.org>
-=item *
-Shawn M Moore <sartak@cpan.org>
-=item *
-יובל קוג'מן (Yuval Kogman) <nothingmuch@woobling.org>
-=item *
-Karen Etheridge <ether@cpan.org>
-=item *
-Florian Ragwitz <rafl@debian.org>
-=item *
-Hans Dieter Pearcey <hdp@cpan.org>
-=item *
-Chris Prather <chris@prather.org>
-=item *
-Matt S Trout <mstrout@cpan.org>
-=back
-=head1 COPYRIGHT AND LICENSE
-This software is copyright (c) 2006 by Infinity Interactive, Inc.
-This is free software; you can redistribute it and/or modify it under
-the same terms as the Perl 5 programming language system itself.
-=cut

data/lib/javonet-ruby-sdk/Binaries/Perl/MacOs/X64/deps/lib/perl5/darwin-thread-multi-2level/Moose/Manual.pod DELETED Viewed

@@ -1,334 +0,0 @@
-# PODNAME: Moose::Manual
-# ABSTRACT: What is Moose, and how do I use it?
-__END__
-=pod
-=encoding UTF-8
-=head1 NAME
-Moose::Manual - What is Moose, and how do I use it?
-=head1 VERSION
-version 2.2207
-=head1 WHAT IS MOOSE?
-Moose is a I<complete> object system for Perl 5. Consider any modern
-object-oriented language (which Perl 5 definitely isn't). It provides
-keywords for attribute declaration, object construction, inheritance,
-and maybe more. These keywords are part of the language, and you don't
-care how they are implemented.
-Moose aims to do the same thing for Perl 5 OO. We can't actually
-create new keywords, but we do offer "sugar" that looks a lot like
-them. More importantly, with Moose, you I<define your class
-declaratively>, without needing to know about blessed hashrefs,
-accessor methods, and so on.
-With Moose, you can concentrate on the I<logical> structure of your
-classes, focusing on "what" rather than "how". A class definition with
-Moose reads like a list of very concise English sentences.
-Moose is built on top of C<Class::MOP>, a meta-object protocol (aka
-MOP). Using the MOP, Moose provides complete introspection for all
-Moose-using classes. This means you can ask classes about their
-attributes, parents, children, methods, etc., all using a well-defined
-API. The MOP abstracts away the symbol table, looking at C<@ISA> vars,
-and all the other crufty Perl tricks we know and love(?).
-Moose is based in large part on the Perl 6 object system, as well as
-drawing on the best ideas from CLOS, Smalltalk, and many other
-languages.
-=head1 WHY MOOSE?
-Moose makes Perl 5 OO both simpler and more powerful. It encapsulates
-Perl 5 power tools in high-level declarative APIs which are easy to
-use. Best of all, you don't need to be a wizard to use it.
-But if you want to dig about in the guts, Moose lets you do that too,
-by using and extending its powerful introspection API.
-=head1 AN EXAMPLE
-  package Person;
-  use Moose;
-  has 'first_name' => (
-      is  => 'rw',
-      isa => 'Str',
-  );
-  has 'last_name' => (
-      is  => 'rw',
-      isa => 'Str',
-  );
-  no Moose;
-  __PACKAGE__->meta->make_immutable;
-This is a I<complete and usable> class definition!
-  package User;
-  use DateTime;
-  use Moose;
-  extends 'Person';
-  has 'password' => (
-      is  => 'rw',
-      isa => 'Str',
-  );
-  has 'last_login' => (
-      is      => 'rw',
-      isa     => 'DateTime',
-      handles => { 'date_of_last_login' => 'date' },
-  );
-  sub login {
-      my $self = shift;
-      my $pw   = shift;
-      return 0 if $pw ne $self->password;
-      $self->last_login( DateTime->now() );
-      return 1;
-  }
-  no Moose;
-  __PACKAGE__->meta->make_immutable;
-When ready to instantiate your class in an application, use it in the
-"traditional" Perl manner:
-  use User;
-  my $user = User->new(
-    first_name => 'Example',
-    last_name  => 'User',
-    password   => 'letmein',
-  );
-  $user->login('letmein');
-  say $user->date_of_last_login;
-We'll leave the line-by-line explanation of this code to other
-documentation, but you can see how Moose reduces common OO idioms to
-simple declarative constructs.
-=head1 TABLE OF CONTENTS
-This manual consists of a number of documents.
-=over 4
-=item L<Moose::Manual::Concepts>
-Introduces Moose concepts, and contrasts them against "old school"
-Perl 5 OO.
-=item L<Moose::Manual::Unsweetened>
-Shows two example classes, each written first with Moose and then with
-"plain old Perl 5".
-=item L<Moose::Manual::Classes>
-How do you make use of Moose in your classes? Now that I'm a Moose,
-how do I subclass something?
-=item L<Moose::Manual::Attributes>
-Attributes are a core part of the Moose OO system. An attribute is a
-piece of data that an object has. Moose has a lot of attribute-related
-features!
-=item L<Moose::Manual::Delegation>
-Delegation is a powerful way to make use of attributes which are
-themselves objects.
-=item L<Moose::Manual::Construction>
-Learn how objects are built in Moose, and in particular about the
-C<BUILD> and C<BUILDARGS> methods. Also covers object destruction
-with C<DEMOLISH>.
-=item L<Moose::Manual::MethodModifiers>
-A method modifier lets you say "before calling method X, do this
-first", or "wrap method X in this code". Method modifiers are
-particularly handy in roles and with attribute accessors.
-=item L<Moose::Manual::Roles>
-A role is something a class does (like "Debuggable" or
-"Printable"). Roles provide a way of adding behavior to classes that
-is orthogonal to inheritance.
-=item L<Moose::Manual::Types>
-Moose's type system lets you strictly define what values an attribute
-can contain.
-=item L<Moose::Manual::MOP>
-Moose's meta API system lets you ask classes about their parents,
-children, methods, attributes, etc.
-=item L<Moose::Manual::MooseX>
-This document describes a few of the most useful Moose extensions on
-CPAN.
-=item L<Moose::Manual::BestPractices>
-Moose has a lot of features, and there's definitely more than one way
-to do it. However, we think that picking a subset of these features
-and using them consistently makes everyone's life easier.
-=item L<Moose::Manual::FAQ>
-Frequently asked questions about Moose.
-=item L<Moose::Manual::Resources>
-Links to various tutorials, videos, blogs, presentations, interviews, etc...
-=item L<Moose::Manual::Contributing>
-Interested in hacking on Moose? Read this.
-=item L<Moose::Manual::Delta>
-This document details backwards-incompatibilities and other major
-changes to Moose.
-=back
-=head1 JUSTIFICATION
-If you're still asking yourself "Why do I need this?", then this
-section is for you.
-=over 4
-=item Another object system!?!?
-Yes, we know there are many, many ways to build objects in Perl 5,
-many of them based on inside-out objects and other such things. Moose
-is different because it is not a new object system for Perl 5, but
-instead an extension of the existing object system.
-Moose is built on top of L<Class::MOP>, which is a metaclass system
-for Perl 5. This means that Moose not only makes building normal
-Perl 5 objects better, but it also provides the power of metaclass
-programming.
-=item Is this for real? Or is this just an experiment?
-Moose is I<based> on the prototypes and experiments Stevan did for the
-Perl 6 meta-model. However, Moose is B<NOT> an experiment or
-prototype; it is for B<real>.
-=item Is this ready for use in production?
-Yes.
-Moose has been used successfully in production environments by many
-people and companies. There are Moose applications which have been in
-production with little or no issue now for years. We consider it
-highly stable and we are committed to keeping it stable.
-Of course, in the end, you need to make this call yourself. If you
-have any questions or concerns, please feel free to email Stevan or
-the moose@perl.org list, or just stop by irc.perl.org#moose and ask
-away.
-=item Is Moose just Perl 6 in Perl 5?
-No. While Moose is very much inspired by Perl 6, it is not itself Perl
-6. Instead, it is an OO system for Perl 5. Stevan built Moose because
-he was tired of writing the same old boring Perl 5 OO code, and
-drooling over Perl 6 OO. So instead of switching to Ruby, he wrote
-Moose :)
-=item Wait, I<post> modern, I thought it was just I<modern>?
-Stevan read Larry Wall's talk from the 1999 Linux World entitled
-"Perl, the first postmodern computer language" in which he talks about
-how he picked the features for Perl because he thought they were cool
-and he threw out the ones that he thought sucked. This got him
-thinking about how we have done the same thing in Moose. For Moose, we
-have "borrowed" features from Perl 6, CLOS (LISP), Smalltalk, Java,
-BETA, OCaml, Ruby and more, and the bits we didn't like (cause they
-sucked) we tossed aside. So for this reason (and a few others) Stevan
-has re-dubbed Moose a I<postmodern> object system.
-Nuff Said.
-=back
-=head1 AUTHORS
-=over 4
-=item *
-Stevan Little <stevan@cpan.org>
-=item *
-Dave Rolsky <autarch@urth.org>
-=item *
-Jesse Luehrs <doy@cpan.org>
-=item *
-Shawn M Moore <sartak@cpan.org>
-=item *
-יובל קוג'מן (Yuval Kogman) <nothingmuch@woobling.org>
-=item *
-Karen Etheridge <ether@cpan.org>
-=item *
-Florian Ragwitz <rafl@debian.org>
-=item *
-Hans Dieter Pearcey <hdp@cpan.org>
-=item *
-Chris Prather <chris@prather.org>
-=item *
-Matt S Trout <mstrout@cpan.org>
-=back
-=head1 COPYRIGHT AND LICENSE
-This software is copyright (c) 2006 by Infinity Interactive, Inc.
-This is free software; you can redistribute it and/or modify it under
-the same terms as the Perl 5 programming language system itself.
-=cut