djerius
djerius
Isn't this a fundamental issue with using `overload`? Perl's `overload` is for unary and binary operators, whereas `substr` is a function, not an operator. My understanding of the gist of...
Thanks for the clarification; I overlooked overloading those functions. So we have a bucket (CORE) of functions where some may be treated as operators because they accept one parameter (and...
As they're all operators, and thus should be treated uniformly in terms of overloading, my suggestion of a second pragma dealing with entities with more complex calling signatures breaks that...
> People like you also enjoyed: [Perl::Critic::Policy::BuiltinFunctions::RequireBlockMap](https://metacpan.org/pod/Perl::Critic::Policy::BuiltinFunctions::RequireBlockMap) Not as much as I enjoy block-less map!
[doc] perlapi: documentation for croak_xs_usage has an undefined "diag_listed_as" tag in the example
There's also a comma missing between `"ouch"` and `"awk"`.
[doc] perlapi: documentation for croak_xs_usage has an undefined "diag_listed_as" tag in the example
Including it in the example confuses the reader. Examples should be reasonably cut'n'paste, and doing so with this example would not compile (apart from the C syntax error, which passes...
[doc] perlapi: documentation for croak_xs_usage has an undefined "diag_listed_as" tag in the example
Thanks!
If the warning message is retained, can it be tweaked to be a little less mysterious? Instead of `Use of uninitialized value in subroutine entry` emit `Use of uninitialized value...
> > If the warning message is retained, can it be tweaked to be a little less mysterious? > > Instead of > > `Use of uninitialized value in subroutine...