#!/usr/bin/perl -l

use strict;
use warnings;
use Term::ReadKey;

while (1) {
    print "Enter something:";

    ReadMode(4);
    my $x = <STDIN>;
    print "Entering...";
    sleep 3;

    ReadMode(0);
    print "You entered: $x";
    last;
}
[download]

Thanks. This thread is solved.

If you are building standalone executable files, then there is a big overhead to get Perl itself to begin with (there is a minimum size). The incremental growth rate depends upon how much source code that you include for Perl to compile and work with. That includes your code and modules that you "use".

This is not a "compile", it is more like packaging the Perl executable engine and the code that you need together as one unit so that it does not require Perl to already be resident. It is not platform independent like a Java jar file.

when you compile a script with pp ...

pp does not compile perl code. It wraps (hopefully) all required modules, the main script, and the perl interpreter into a single binary. Think of it as a self-extracting archive that automatically starts the main script after unpacking, using the embedded perl interpreter.

... is it decompilable?

Yes. See Uncool Use Of Perl: perl2exe. decompile quick steps, Re: Protection for Perl Scripts, Re^2: best way to store login information for a perl script?, Re^2: Where should I have configuration information in a file or database. Last but not least, pp clearly documents that it uses PAR as its archive format, which is a renamed, unprotected ZIP file.

(And if it is not is it platform-independent?)

No. Compiled binaries are never platform-independent. Typically, it works only on the same platform. Some platforms have ways to execute code written for older platforms (e.g. most Linux x64 systems can run Linux x86 executables, same for Win16 on Win32 and Win32 on Win64, MacOS classic apps on PowerPC MacOS X versions) or for other platform (FreeBSD can emulate the Linux API, Linux can run some Windows executables using wine). But you can't expect any compiled binary to run on any platform.

Also pp compiled perl seems to have an overhead. Is it a one time only overhead or does it get bigger the more code you have?

Since pp must contain all required code, the final executable grows bigger and unpacking takes more time.

Alexander

++ for formating the code correctly... but - - - in part for posting at least two unrelated questions in the same SOPW... and for the pointless, overstated or ambiguous use of "nasty" in part 1 of question 1.

But the real reason for the (offsetting¹ downvote is the hope that it will prod you to read On asking for help and How do I post a question effectively? and to start familiarizing yourself with the perldocs available on your own machine. Run perldoc perltoc there are see perltoc. And, not just BTW, googling this site with appropriate keywords related to your question will often spare you the wait for an answer.

You've received very decent answers to your questions; you'll continue to get those here as you progress to more complex issues... if you show a bit more effort before asking others to dedicate their time to your problems.

¹ IOW, no upvote or downvote cast; mentioned as instructional points, only.

#!/usr/bin/perl -w
use strict;

while(1) {
    while(<>) {
        s/\W//g;
        print;
    }
}
[download]

Yes. Please explain the s/\W//g; part

actually it does not work very well. \W means match non-word character, opposite of \w. See http://perldoc.perl.org/perlre.html. You may want to look at http://search.cpan.org/~jstowe/TermReadKey-2.30/ReadKey.pm too. There may be other models on CPAN that may do what you are looking for. So search CPAN. Or most likely another monk will have the right answer.