function exhibits bizarre behavior in Windows XP

[ppowell]

function getResponse() {
  $responseID = @fopen('php://stdin', 'r') or die('Cannot read from stdin');
   while (($response = @fgets($responseID, 1024)) !== false) {
     @fclose($responseID);
     return $response;
   }
}

This function works just fine if using CLI PHP in a Unix platform. But this same function is required to be used in an application that is housed within a Windows XP platform, and in that platform, this function seems to ignore user input and returns null every time.

Does anyone have any idea why this would specifically happen only in Windows XP using CLI PHP and nowhere else? Is there some issue involving XP's version of stdin?

Thanks
Phil

[LoganK]

Actually yes. I don't know anything about PHP CLI, but I saw a thread a day or two ago dealing with PHP CLI, and they had constructed a method of fixing something to do with STDIN. Sorry I can't be of any more help - all I can do is confirm that there is some issue.

[Weedpacket]

One question: what's with the loop?
I'm not near an XP machine right now, but I don't recall having any problems with php://stdin

[Oersoep]

So the fopen doesn't work?

Ditch the @. It might tell you what's wrong then.

[Oersoep]

And why bail out immediately?

function getResponse() { 
  $responseID = @fopen('php://stdin', 'r') or die('Cannot read from stdin'); 
   // do while there's something:
   while (($response = @fgets($responseID, 1024)) !== false) { 
     // if there's anything the first time: quit
     @fclose($responseID); 
     return $response; 
   } 
}  

Try this:

function getResponse() { 

   $responseID = fopen('php://stdin', 'r') or die('Cannot read from stdin'); 

   $response = "";

   while( !feof( $responseID ) )
       $response .= fgets( $responseID, 1024 );

   @fclose($responseID); 
   return $response; 

}