Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • This is ... already a solved problem. Sartak's plan outlined here [blogspot.com] allows you to basically lint the code to catch this sort of thing, without running into the huge problem you've just caused of LETTING A RANDOM ROLE SUDDENLY FUCK OVER YOUR CLASS.

    I mean, a MetaRole type thing that made it an error on a class by class basis would be great. What you've just done is randomly added compile time errors at a distance, without warning. I can see this as being perhaps acceptable for internal codebases, but I'd strong

    • I mean, a MetaRole type thing that made it an error on a class by class basis would be great.

      That seems like the best option. Only at the point of role composition does a maintainer know enough about the use of the role to understand what's appropriate and what's not.

      ... unexpected exceptions just because a module's author disagrees with the module's user about semantics really just aren't in the spirit of perl.

      Or roles, which exist to decouple the declaration of semantics from the mechanisms of implem