Module::Build proper, on the other hand, seems much more lenient:

Module::Build proper uses a bespoke argument parser that includes heuristics to guess if it should take the argument (e.g. ./Build --verbose 1 test). Module::Build::Tiny just uses Getopt::Long like a normal Perl program. There are actually more behaviors that Module::Build's argument parser allows that Module::Build::Tiny doesn't do. MBT always went for a subset of behaviors because the full set was too large and unpredictable.