My original code, the one with the problem, was 

Win32::API->Import(
   'kernel32',
   'BOOL PeekNamedPipe(
      HANDLE  hNamedPipe,
      LPVOID  lpBuffer,
      DWORD   nBufferSize,
      LPDWORD lpBytesRead,
      LPDWORD lpTotalBytesAvail,
      LPDWORD lpBytesLeftThisMessage
   )',
);

[download]

There's no way to pass NULL when using that syntax. Using that syntax is what sets has_proto. I may not have found the optimal *workaround*, but that doesn't mean the bug isn't there. I didn't use LPLPPP because I assumed it was buggy too.

More depression when I see people proffering this kind unnecessary complexity:

If you think LPLPPP is shorter... 

BEGIN {
   # BOOL WINAPI PeekNamedPipe(
   #    __in       HANDLE hNamedPipe,
   #    __out_opt  LPVOID lpBuffer,
   #    __in       DWORD nBufferSize,
   #    __out_opt  LPDWORD lpBytesRead,
   #    __out_opt  LPDWORD lpTotalBytesAvail,
   #    __out_opt  LPDWORD lpBytesLeftThisMessage
   # )

   my $f = Win32::API->new('kernel32', 'PeekNamedPipe', 'LPLPPP', 'L')
      or die $^E;

   sub PeekNamedPipe {
      my $vBuffer           = defined($_[1]) ? $vBuffer          : 0;
      my $nBytesRead        = defined($_[3]) ? pack('L!', $_[3]) : 0;
      my $nTotalBytesAvail  = defined($_[4]) ? pack('L!', $_[4]) : 0;
      my $nBytesLeftThisMsg = defined($_[5]) ? pack('L!', $_[5]) : 0;

      my $rv = $f->Call(
         $_[0],
         $vBuffer,
         $_[2],
         $nBytesRead,
         $nTotalBytesAvail,
         $nBytesLeftThisMsg,
      );

      $_[1] = $vBuffer                         if defined $_[1];
      $_[3] = unpack('L!', $nBytesRead       ) if defined $_[3];
      $_[4] = unpack('L!', $nTotalBytesAvail ) if defined $_[4];
      $_[5] = unpack('L!', $nBytesLeftThisMsg) if defined $_[5];

      return $rv;      
   }
}

[download]

That's why I prefer to use the prototype approach. It's much simpler. It handles packing pointers. It just doesn't handle NULL.

I agree with you. Avoiding this complexity would be much better, but a bug is preventing me.

In reply to Re^8: ... (Proof!) by ikegami
in thread Non-blocking Reads from Pipe Filehandle by cbudin

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.