Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Firstly , Thanks for input!

I'm adjusting some settings regarding to the program that I want to start both before it's started and afterwards - when its up and running. It's a GUI-program, so I would like users not to see the console window at all, but that is not highest priority.

You say quote:
"Actually perl internally parses your command to know what to run and which arguments to pass. Hence difference when you add extra quotes."

What does this mean regarding to the console window that won't be killed (or the console windows (not) appearing)? It seems that when I use

my $prg= ' "c:/winnt/notepad.exe" ';


exec $prg ;

in the child process there is some other process starting up, which keep the perl program from ending (and thus closing the console window)?! Tom

In reply to Re: Re: WIN32 exec mystery by major tom
in thread WIN32 exec mystery by major tom

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.