Re: Pipes (for interprocess communication)

Here is a simple example:

pipe(my $reader, my $writer);    # Create a pipe

if (my $pid = fork()) {
    # In parent: read one line from the pipe and print it
    print "Message from child: ".<$reader>;
}
else {
    # In child: print a line of text to the pipe
    print $writer ("Hello, parent!\n");
}
[download]

Comment on Re: Pipes (for interprocess communication) Download Code

Replies are listed 'Best First'.
Re^2: Pipes (for interprocess communication) by penguin_asylum (Sexton) on Dec 09, 2005 at 19:36 UTC
Sorry, one more question. Why is it that "print ''.<$reader>" works, but not just "print <$reader>" ?	[reply]
Re^3: Pipes (for interprocess communication) by Celada (Monk) on Dec 09, 2005 at 21:06 UTC
`.<$reader>` forces scalar context while `<$reader>` uses the context supplied by the `print`, which is array context. In array context, the `<>` operator sucks in the whole rest of the file. Why does this not work? Because it is going to wait indefinately the the end of the file to come. On pipes, the end of file comes when the other end of the pipe is closed. In robin's example, the pipe is never closed. Mostly for this reason, the usual paradigm is this: Create the pipe fork in the parent, close the reader and use only the writer in the child, close the writer and use only the reader. or, of course, Create the pipe fork in the parent, close the writer and use only the reader in the child, close the reader and use only the writer. Trying to use both the reader and the writer end of the same pipe in the same process leads to deadlock. See the documentation of things like IPC::Open2 for how this can occur with a longer chain of pipes too.	[reply] [d/l] [select]
Re^2: Pipes (for interprocess communication) by penguin_asylum (Sexton) on Dec 09, 2005 at 18:46 UTC
Thanks And the parent could also write to $writer with the child reading from $reader, right?	[reply]
Re^3: Pipes (for interprocess communication) by robin (Chaplain) on Dec 09, 2005 at 18:54 UTC
Right. Update: I should have been more specific. Unless you really know what you're doing, you should choose a direction (i.e. parent -> child or child -> parent) and use the pipe only in that direction. If you want to communicate both ways, just make two pipes.	[reply]