[Catalyst-dev] [Catalyst] Major (for me) problem fixed!

[Jonathan Rockway]

> That's a horrible approach, I really don't think it's the answer.
> It'll fail miserably when the package name doesn't match the
> filename, for a start - which is generally inadvisable but perfectly
> valid.

Yup, and M::P::O's unit tests pick it up: t/16different_extension chokes
because the package is MyTest::Plugin::Quux::Foo but the file is
ExtTest::Plugin::Quux::Foo.  Nasty.  (I admit I was thinking of Java
when I wrote my post.  How embarrassing on my part :)

> A better plan seems to be to put together a selection of dumbass
> filenames as provided by version control tools and editors and to
> exclude those; then we can build that into the default config passed
> to Module::Pluggable (or even get it submitted back as a patch to
> Module::Pluggable itself) and forget about it.


Yeah.  For some value of better, anyway.  I guess I'll stick with my
regex for now :( 

What do other editors pollute the filesystem with?  I'm only familiar
with emacs (and subversion; which has its nice .svn/Foo.pm.base files).

I'd like to fix this for all future editors and all future M::P::O
users, but  unfortunately allowing for broken things like t/16 breaks
our attempts to detect brokeness. :) I wonder what real apps are using
the functionality in t/16?

Regards,
Jonathan Rockway