I would have to agree, that if you want to use license codes to turn on/off functionality, I'd suggest going with a pre-compiled version, either with perl2exe or perlapp. Either way, you're looking at a greater level of support, considering that these may not always run properly on all platforms (and certain platforms, for sure, are automatically excluded). They will, however, hide your code from all but the dedicated. I wouldn't expect to get perfect protection from any route, we've seen how much money and effort big-named software companies spend on copy-protection schemes using everything from simple codes to hardware dongles, and yet, you can still find cracked versions of the most expensive stuff out there.
That being said, a simple hash-based key and pre-compiling your source in some way (although, really, perl2exe and perlapp just include the source and the perl interpreter together, for the sake of discussion, I'll call it 'compiled') will be inoccuous enough to say that someone mightj ust buy it (if they like it).
!c
