ok, it only true for non-blocking php streams ...

but still this should be mentioned on the fread() page

here was my code:

$f=fopen("./foo","r"); 
while($c=fgetc($f)){
 ...
  }

...and the 'while' loop was quit long before EOF was reached.
After examination, it was quit when a character 0 was read
(thus confusion between 0 and EOF.......)

Try this code instead:

$f = fopen("./foo","r");
while (false !== ($c = fgetc($f))) {
    ...
}

As this is really what you want to do ;)  The documentation for fgetc() really needs to mention this as most others that might encounter this 0==false do (such as readdir).

A documention problem is to do the following to the fgetc docs:

a) Add an example that keeps in mind false vs 0
b) Implement the &return.falseproblem; entity.

i prefere the 

while(!feof($f)) {
  $c=fgetc($f);
  ...
}

style ...

True.  How about using feof() in the example and including the falseproblem entity in the docs.

I have problems with below code too... It stops to read in the middle even for 10 KB files.

$fd= fread(fopen("http://something.com/index.php", "r"), 100000000000); if (!($fd)) {echo "Error in loading page. Please try again later.";}

$orgfile=Substr($fd,0, 100000000000);   echo $orgfile;   die;

That's unrelated, read the fread() docs for why.

This bug is now closed and will show up in the next manual build, thanks for the report :)  I chose not to use feof() as to more clearly demonstrate the 'false problem' and because it just means an extra function call for every character.

http://cvs.php.net/cvs.php/phpdoc/en/reference/filesystem/functions/fgetc.xml