Perhaps you could get the C++ application to call the Perl script using wperl.exe instead of perl.exe. I personally have not used wperl.exe before, so I don't know if that might introduce other issues.

• wperl.exe vs perl.exe
• How do I start perl without having a "cmd.exe" window

It is internally called by C++ application.

Does the C++ app have a GUI?

Yes its a windows application.

its a windows application.

I suspect that that the window you are seeing is being created when the C++ app spawns Perl; rather than when Perl calls system; and unless you have access to the sources of the C++ and can modify it; you may be stuck.

The only suggestion I have that might fix it without modifying the C++ app is to swap your call to system, for a call to Win32::Process, and try using the CREATE_NO_WINDOW flag.

If that doesn't work, see above.

---

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!