view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

 1.03 2020.10.12 - Relicensed under MIT License. Maintainer updated. Build
                   configs updated. Set min version of Perl to 5.6. Added
                   'use warnings'. Misc file permissions updated. Added
                   GitHub repo to metadata.

 1.02 2008.05.17 - Permissions fixes for build tools and added more examples

 1.01 2008.05.16 - Fixed minor permissions problem

 1.00 2008.05.13 - Initial public release.

lib/Acme/Sub/Parms.pm  view on Meta::CPAN

                die("Syntax error in BindParms spec: $raw_spec\n");
            }
        } else {
            die("Syntax error in BindParms spec: $raw_spec\n");
        }
    }
    return $spec_tokens;
}

###############################################################################
# bind_spec is intentionally a a non-POD documented'public' method. It can be overridden in a sub-class
# to provide alternative features.
# 
# It takes two parameters: 
#
#  $raw_spec             - this is the content of the [....] block (not including the '[' and ']' block delimitters)
#  $field_name           - the hash key for the field being processed
# 
# As each line of the BindParms block is processed the two parameters for each line are passed to the bind_spec
# method for evaluation. bind_spec should return a string containing any Perl code generated as a result of
# the bind specification.

lib/Acme/Sub/Parms.pod  view on Meta::CPAN

 1.03 2020.10.12 - Relicensed under MIT License. Maintainer updated. Build
                   configs updated. Set min version of Perl to 5.6. Added
                   'use warnings'. Misc file permissions updated. Added
                   GitHub repo to metadata.

 1.02 2008.05.17 - Permissions fixes for build tools and added more examples

 1.01 2008.05.16 - Fixed minor permissions problem

 1.00 2008.05.13 - Initial public release.

=head1 ERRORS

Syntactic errors using Acme::Sub::Parms will generally cause
compilation errors near (but probably not exactly at) the line
containing the error. When you see that kind of error, look for a
syntax error in the declaration.

=head1 BUGS