It looks like you don't know perl, so it is bad idea to write in perl when you don't know it. So either learn it, or ask someone to write the code that you need.

What? You must be kidding. Writing Perl code is certainly and by far the most important step to learn the language. Using tutorials and books is certainly very important, but the only right way to learn a language (whether a spoken language or a programming language) is to practice it.

Consider what Larry Wall is writing in the final section of the first chapter of the Camel Book (Programming Perl):

What You Don't Know Won't Hurt You (Much)

Finally, allow us to return once more to the concept of Perl as a natural language. Speakers of a natural language are allowed to have differing skill levels, to speak different subsets of the language, to learn as they go, and generally, to put the language to good use before they know the whole language. You don't know all of Perl yet, just as you don't know all of English. But that's Officially Okay in Perl culture. You can work with Perl usefully, even though we haven't even told you how to write your own subroutines yet. We've scarcely begun to explain how to view Perl as a system management language, or a rapid prototyping language, or a networking language, or an object-oriented language. We could write entire chapters about some of these things. (Come to think of it, we already did.)

To the OP: yes, by all means, write Perl code, even if it is what is sometimes called "baby Perl" at first. Most (if not all) of us have started this way, using first a small subset of the language and then gradually expanding the language knowledge.