STANDING ON THE SHOULDERS OF ...

This module was inspired by MooseX::StrictConstructor, and includes some implementation details taken from it.

SUBVERTING STRICTNESS

There are two options for subverting the strictness to handle problematic arguments. They can be handled in "BUILDARGS" or in "BUILD".

You can use a "BUILDARGS" function to handle them, e.g. this will allow you to pass in a parameter called "spy" without raising an exception. Useful? Only you can tell.

   sub BUILDARGS {
       my ($self, %params) = @_;
       my $spy = delete $params{spy};
       # do something useful with the spy param
       return \%params;
   }

It is also possible to handle extra parameters in "BUILD". This requires the strictness check to be performed at the end of object construction rather than at the beginning.

    use MooX::StrictConstuctor -late;
    sub BUILD {
        my ($self, $params) = @_;
        if ( my $spy = delete $params->{spy} ) {
            # do something useful
        }
    }

When using this option, the object will be fully constructed before checking the parameters, and a failure will cause the destructor to be run.

Inheritance

A class that uses MooX::StrictConstructor but extends a non-Moo class will not be handled properly. This code hooks into the constructor as it is being strung up (literally) and that happens in the parent class, not the one using strict.

A class that inherits from a Moose based class will discover that the Moose class's attributes are disallowed. Given sufficient Moose meta knowledge it might be possible to work around this. I'd appreciate pull requests and or an outline of a solution.

Interactions with namespace::clean

MooX::StrictConstructor creates a "new" method that namespace::clean will over-zealously clean. Workarounds include using namespace::autoclean, using MooX::StrictConstructor after namespace::clean or telling namespace::clean to ignore "new" with something like:

  use namespace::clean -except => ['new'];