From a quick survey of my machine, I got this list:
Extensions:

*.pod
*.pot
*.la
*.po
*.ix
*.a
*.so
*.bs
[download]

autosplit.ix
LICENSE
SIGNATURE
AUTHORS
ChangeLog / CHANGES
CREDITS
[download]

Thanks for the additions.

I'm not really proposing anything. It is just going to be a dictionary. If someone else wants to do something else, more power to them.

--
brian d foy <bdfoy@cpan.org>

I used this code

#! perl -slw
use strict;
use File::Find;

my %extns;

find( sub{ $extns{ lc($1) }++ if -f _ and m[\.([^\.]+?)$]; }, @ARGV );

print "$_ => $extns{ $_ }" for sort keys %extns;
[download]

to produce this list. I omitted the src directories, but include my packages directory where I build modules not available via PPM.

Thanks for the code. :)

The trick here is to know what those things mean, and although I'm not a Windows person, I'm guessing that most of those extensions are not interesting in this case. Extensions like zip, xpm, xbm, wmf, tar, sh, and many more off of my screen at the moment probably have their usual, non-perl significance.

I would certainly appreciate any Windows user who could pick out the file names and extensions particular to that OS, though.

--
brian d foy <bdfoy@cpan.org>

My idea is that someone might look in this dictionary to see what a file is and how it was created. Some files one might see in a distribution and wonder what is does (e.g. test.pl), might show up as a developer snapshot (e.g. MANIFEST.SKIP), or might be a particular sort of file in a perl lib directory (e.g. the .al files that AutoSplit creates).

I'm documenting special file names, file extensions, and such that a Perl user may run into. I learn about these things by looking at source or watching things run, but I don't think everyone should have to do that.

--
brian d foy <bdfoy@cpan.org>

Your list is missing XS (and related) files: this is what's in my tree when I build an xs module:

Module.xs  xs source file
Module.c   generated from Module.xs
Module.o   generated from Module.c (?)
Module.so  generated from Module.o (?)
Module.bs  some 0 sized file
Module.h   C header file for Module (can also have other name)

typemap    conversion code from C datastructures to Perl and back
ppport.h   backward portability routines for the C API
           (generated by Devel::PPPort)
[download]

And then there's man pages: *.1p (for scripts) and *.3pm (for modules) that are usually generated from pod.

and pm_to_blib and .exists files that I think are there as markers for make.