Re^2: Passing array pointer through script input

There are three places along the path where stringification is forced, but none are related to pipes.

`...` is a form of string literal. A string is created from its contents. `...` is the same thing as readpipe("...").
If the shell is required, then the "..." in "`...`" is a shell command, which can only be a string.
Arguments are passed to the child via a variant of the exec system call, which only accepts strings.

Comment on Re^2: Passing array pointer through script input Select or Download Code

Replies are listed 'Best First'.
Re^3: Passing array pointer through script input by moritz (Cardinal) on Aug 21, 2008 at 21:26 UTC
Arguments are passed to the child via a variant of the exec system call, which only accepts strings. That's where I thought the pipes where involved - to read the output of the exec'ed command, perl has to open a pipe to it, which I thought would replace the exec call altogether. But my C fu is rusty to inexistent...	[reply]
Re^4: Passing array pointer through script input by ikegami (Patriarch) on Aug 21, 2008 at 22:14 UTC
The problem is with the arguments, not the output.	[reply]