Thank you. The comment about the filename was just there to remind me that I have renamed it temporarily to avoid having such a deep directory tree as the "Regexp::CharClasses::Thai" would require. I'm just testing, and am not actually "installing" the module on my machine, so the test script must be told where to find the file, and, yes, the file, as named in the test script, exists there.

Regarding the "&IsThaiLCons" versus "IsThaiLCons()" -- I've tried them both, and both produce the same error.

Yes, the module should be exporting that subroutine. I've tweaked that several times, sometimes having it export specifically that one function for testing purposes...and I've even tried commenting out the entire "Exporter" code block to force everything to be available to the calling script by default. Nothing seems to change the irritating log messages. Maybe I should just restart the entire server! The errors/bugs I spend the most time on are the ones I have the least idea where something could even possibly be wrong--as fits this situation. I don't see much wrong with any of the code. When this happens to me, sometimes I end up spending entire days trying to fix the issue.

It reminds me of some years ago when the problem might have been an invisible BOM mark as the first character in the file!

Apache is running the Perl scripts somehow. I guess it does so via the "modperl" feature. Perhaps there is some better way? One begins to wonder.