I think a more fundamental question here is: what benefit do you think is being created by keeping the perl source code hidden? This is obviously not a benefit for the end user -- the only conceivable benefit would be to satisfy some perception you have (or your employer has) about the importance of retaining exclusive ownership of the code and not allowing anyone else to view it.

So this raises two additional questions:

• Are you really confident that the benefits of exclusive ownership outweigh the competing advantages of feedback from peer review and informed users that could improve your code?

• Might there be some other method to gain the perceived benefits of exclusive ownership, without having to conceal the source code?

If exclusive protection of source code is unavoidably essential to you, maybe you should just re-implement the perl script in a compiled language.

Apart from that, your idea of having a C program do system( "perl -e 'eval{hugestring}'" ) might work if your perl source code is tweaked with this idea in mind: don't use single-quotes anywhere in the perl source code. (Perl gives you plenty of ways to avoid using single-quotes.)

UPDATE: Having just seen this reply from dave_the_m, I should say that this approach "works" in the sense that it will probably run -- not that it will actually protect your source code from exposure. (/update)

Changing the perl source code just to support that sort of application is admittedly a kluge, and might raise maintenance issues later on ("oops! when that new function was added, we forgot about avoiding apostrophes..."), but if you are stuck in the mindset of hiding the source code, some folks would tend to expect that there are bound to be kluges, because there's no way to prove otherwise.

If the "protection" of source code is a matter of trying to preserve your "market share", you should understand that eventually you are bound lose market share to anyone who finds a way to address the same task but doesn't care about hiding their source code.

If the source code protection is a matter of preserving particular data from unauthorized viewers, that's a different matter: just separate the data from the source code, and encrypt the data, not the source code.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.