summaryrefslogtreecommitdiff
path: root/README
blob: 3479820ac2a7ad631334e8ee5355d410995727a6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
NAME
    MooX::late - easily translate Moose code to Moo

SYNOPSIS
       package Foo;
       use Moo;
       use MooX::late;
       has bar => (is => "ro", isa => "Str", default => "MacLaren's Pub");

    (Examples for Moo roles in section below.)

DESCRIPTION
    Moo is a light-weight object oriented programming framework which aims to
    be compatible with Moose. It does this by detecting when Moose has been
    loaded, and automatically "inflating" its classes and roles to full Moose
    classes and roles. This way, Moo classes can consume Moose roles, Moose
    classes can extend Moo classes, and so forth.

    However, the surface syntax of Moo differs somewhat from Moose. For
    example the `isa` option when defining attributes in Moose must be either
    a string or a blessed Moose::Meta::TypeConstraint object; but in Moo must
    be a coderef. These differences in surface syntax make porting code from
    Moose to Moo potentially tricky. MooX::late provides some assistance by
    enabling a slightly more Moosey surface syntax.

    MooX::late does the following:

    1.  Supports `isa => $stringytype`.

    2.  Supports `does => $rolename` .

    3.  Supports `lazy_build => 1`.

    4.  Exports `blessed` and `confess` functions to your namespace.

    5.  Handles native attribute traits.

    Five features. It is not the aim of `MooX::late` to make every aspect of
    Moo behave exactly identically to Moose. It's just going after the
    low-hanging fruit. So it does five things right now, and I promise that
    future versions will never do more than seven.

    Previous releases of MooX::late added support for `coerce => 1` and
    `default => $nonref`. These features have now been added to Moo itself, so
    MooX::late no longer has to deal with them.

  Use in Moo::Roles
    MooX::late should work in Moo::Roles, with no particular caveats.

       package MyRole;
       use Moo::Role;
       use MooX::late;

    Package::Variant can be used to build the Moo equivalent of parameterized
    roles. MooX::late should work in roles built with Package::Variant.

       use Package::Variant
          importing => [ qw( Moo::Role MooX::late ) ],
          subs      => [ qw( has with ) ];

  Type constraints
    Type constraint strings are interpreted using Type::Parser, using the type
    constraints defined in Types::Standard. This provides a very slight
    superset of Moose's type constraint syntax and built-in type constraints.

    Any unrecognized string that looks like it might be a class name is
    interpreted as a class type constraint.

  Subclassing
    MooX::late is designed to be reasonably easy to subclass. There are
    comments in the source code explaining hooks for extensibility.

BUGS
    Please report any bugs to
    <http://rt.cpan.org/Dist/Display.html?Queue=MooX-late>.

SEE ALSO
    `MooX::late` uses Types::Standard to check type constraints.

    `MooX::late` uses Sub::HandlesVia to provide native attribute traits
    support.

    The following modules bring additional Moose functionality to Moo, beyond
    what MooX::late offers:

    *   MooX::Override - support override/super

    *   MooX::Augment - support augment/inner

    MooX allows you to load Moo plus multiple MooX extension modules in a
    single line.

AUTHOR
    Toby Inkster <tobyink@cpan.org>.

COPYRIGHT AND LICENCE
    This software is copyright (c) 2012-2014, 2019 by Toby Inkster.

    This is free software; you can redistribute it and/or modify it under the
    same terms as the Perl 5 programming language system itself.

DISCLAIMER OF WARRANTIES
    THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
    WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
    MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.