#28371 [Opn->Fbk]: Different behaviour of fopen depending on r+,w+,a+

ID: 28371 Updated by: vrana@php.net Reported By: rc at opelgt dot org -Status: Open +Status: Feedback Bug Type: Documentation problem Operating System: MacOSX 10.3 PHP Version: 4.3.4 New Comment: Tell us what's wrong or missing mainly in the table "A list of possible modes for fopen() using mode". The behavior of the modes is explained well there IMHO. Previous Comments: ------------------------------------------------------------------------ [2005-03-23 11:53:50] rc at opelgt dot org I have written all things that should be mentioned. Please read it carefully and if you do not understand it, ask me again ;-) ------------------------------------------------------------------------ [2005-03-23 01:00:04] phpdoc at lists dot php dot net No feedback was provided for this bug for over a week, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2005-03-15 14:24:05] vrana@php.net Please tell us what exactly is not documented. In my eyes, everything works exactly as described on fopen page, mainly in the table "A list of possible modes for fopen() using mode". ------------------------------------------------------------------------ [2005-02-03 05:05:56] sniper@php.net reclassified ------------------------------------------------------------------------ [2004-05-13 15:19:46] rc at opelgt dot org Yes, my sent script runs identically for all modes under Linux and MacOSX. Its different among the modes. The mode options in fopen() for my understanding should have only effect for the start: position of pointer, content of file, file creation if nessessary or not. Sure, read or write or both ways of access should remain until fclose(). ;-) 'r' and 'w' need clearstatcache() but 'a' doesnt. That is the unexpected and in the manual not mentioned difference. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/28371 -- Edit this bug report at http://bugs.php.net/?id=28371&edit=1