a few things to note...

first, perlcc can compile perl source code into a binary:  perlcc perl_source.pl -o perl_bin_executable - and there's no offending C source involved. unfortunately, it's also less than stable (i get terrible errors with it on 5.6.1, when i use map{}, and have had no luck making it play nicely with Socket.pm)

secondly, if you know a teensy bit of C (or are good at faking it <g>) you can always shove your very own perl interpreter into a .c file, and include the code in a char'd string (see perlman:perlembed for oodles of information on that ((: )

now, i agree with the many others who have said that compiling perl scripts won't protect the source.. but as far as i could tell, that wasn't what all this was about, was it?

Being able to write a decent snippet, one-liner, or full- fledged program in perl, and then distribute it to those who -don't- have some/any/all of the following:

• some perl module or another
• a perl interpreter! (:
• any programming knowledge whatsoever

installed would be, at times, infinitely helpful. i myself have lost track of ho w many times i've wished i had something as simple as a 'comment cutter' (eg.  map{print if not m/^(#|$)/;} <fh>;) on a dos/win32 platform.

lastly, if you need help on this project, i'd be more than happy to help (assuming the need isn't already filled by the mega-experienced perl adepts and gods who haunt the monastery) (:

Good Luck,
strfry()