Re^3: I want you to convince me to learn Perl

[Marshall]

I find myself write less and less C as I can do almost anything in perl, and write it over ten times as fast in code that is easier to maintain. Some projects however still need perl: the code cannot be shared by law and perl has no good code-hiding feature.

I think that we are on the same page here.
I am not so sure about the lack of a "code-hiding" feature.

I use the Active-State Compiler and this thing is pretty hard to "decode". Many years ago, a massive power failure took out my Power Supply and 3 HD's. That trashed my Perl source code for one project, but not my .exe. The .exe code still runs over 5 years with no reported defects - so I am happy about that! If somebody can help me recover the source code, I would appreciate it. But I am skeptical. It is not as easy as one might think.

I love Perl. A wonderful language.

A new school quarter started Monday and I'm going to be working with an assembly class. I like it. Perl can kick butt vs this stuff except in very high performance situations.

[bulk88]

I assume you are referring to PerlApp by AS. Use a C debugger, set a breakpoint in eval_pv() or something similar (I dont remember anymore) (finding eval_pv in the process will be the painful part), once the AS decompresser/obfuscator decrypts it into memory, it will be passed as 1 big string to the perl5**.dll which will be in a temp dir somewhere on disk.

The other choice is to RE the PerlApp obfuscator algorithm Re: Security, is it to much to ask?. Its been published a couple times in history, for example A real challenge and Decompile PerlApp but AS changes it constantly for obvious reasons.