I'm not exactly a Perl <--> C expert, but this doesn't look like one of those situations. What you're doing is running a program from inside your perl script via system. That launches a new process, with a new perl interpreter, with no shared memory between them. Running a script via system is not anywhere near the same thing as running perl code via do, use, or require. It starts of brand new and fresh.
What you probably want to do is embed cryzone in your application (via use), or possibly share some memory (IPC::Shareable, perhaps), or fork (but not exec). Not really sure what is suitable for your situation from your original post.
In reply to Re: embedding perl
by Tanktalus
in thread embedding perl
by rocketboy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |