Re^5: RFC: feature proposal re code in @INC

[perrin]

What I worry about is that someone else may do something bizarre in their CPAN module (like putting something bizarre in @INC) which will break my code elsewhere (like code to check modules in @INC for changes under mod_perl). If all the magical things in perl could be safely ignored by people who choose not to use them, this would be less of an issue. For a real world example, see the recent problems on the Catalyst mailing list with YAML, which uses Spiffy and apparently modifies the way 'use base' works in other modules.

[chromatic]

That's a very good point. Perl 5 does have more than a few unhygenic corners.

(I was under the impression that Catalyst's biggest problem is multiple inheritance. What do you mean plugin method names collide? Who could possibly have seen that coming...)

[sri]

Surprisingly that never happened, and we already have over 100 plugins. :)

Btw. Devel::Nextalyzer is a great tool to visualize multiple inheritance (and in turn prevent collisions).

[diotalevi]

That's just ingy. Most people produce code saner than that.