autodie | Make functions succeed or die in Perl | Command Line Interface library

Instead of this in mwe.pm:

There are various ways to handle these things, but each technique depends on what the prompt wants.

• Some commands have options so you don't have to answer questions. For example, rm -f may do what you want.
• The yes command is an endless list of "yes": yes | rm *.txt
• likewise, if you know what the answers to the questions are, you can have its input ready, some_command < input.txt.
• Closing STDIN before you start the command may handle some cases.
• Some things use environment variables to answer questions, such as PERL_MM_USE_DEFAULT in ExtUtils::Makemaker.
• Perl has some modules that can handle some of these cases. IPC::Run, for instance, allows you to mix reading and writing to a process. Other options such as IPC::Open3 don't work so well in those cases because the buffer either fills up or the exchange blocks.

There are probably lots of other techniques too.

As @Ed Sabol pointed out, the problem was with file characters, and how the files were being read.

the key line to change is readdir $dh to decode_utf8(readdir $dh) this allows Perl to handle the non-Latin (Cyrillic) filenames. The Encode library should also be loaded: use Encode 'decode_utf8';

This uses another map instead of the x operator, but it does give you copies:

It's not grep but the aliasing of the values in your hash slice that causes this.

This has the same effect:

It seems that you can get very close if you export the entire symbol rather than one slot in the glob,

This is a result of the constant folding inside of Perl. This can be demonstrated with the following example from haarg on irc.freenode.net/#perl,

The Segmentation fault (core dumped) message you sometimes see in the terminal is not produced by the process you launch but by the shell that launched this process.

When it launches a process, the shell waits for it with a system call similar to man 3 waitpid. Such a system-call tells if the process exited successfully (with return or _exit()) or was killed by a signal. In this last case, the shell displays a message specific to the signal that caused the early termination (man 3 strsignal).

In your specific case, this is not the shell that launches the process you wrote in C, but the perl interpreter. Your process being killed does not make perl be killed too, so your shell does not display such a message.

I cannot write perl but I'm certain that you can replace system $compiled_code; by something that does the equivalent of fork()/exec()/waitpid()/strsignal().

Using the end of this page, I think you can try this at the end of your script.