Grand, that works beautifully. I would not have opened
Win32API::File on my own. Just to wrap it up, it looks like this, once fit to my program:
my $hPipe = createFile( $PIPE_NAME, "rwe" )
or die "Can't read from [$PIPE_NAME]: $^E\n";
$^E = 0; # Clear possibly misleading errors out.
no strict 'subs';
OsFHandleOpen( PIPE, $hPipe, "rw" )
or die "Can't associate Perl handle: $! ($^E)\n";
use strict 'subs';
The 'e' portion of the "rwe" arg to
createFile() causes an error if the file doesn't already exist, which is the behavior I want. If the pipe server isn't running, I need to know.
I expect there's a better way to quiet the complaint about the filehandle being a bareword, too.
Since I'm not reporting $^E unless there's an error, is it necessary to clear it ahead of time?
Thanks for the prompt answer to something that turned out trickier than I thought.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.