|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #75836 fwrite() should accept null for chunk size
Submitted: 2018-01-17 16:48 UTC Modified: 2018-01-18 23:50 UTC
From: Assigned:
Status: Open Package: Streams related
PHP Version: 7.2.1 OS:
Private report: No CVE-ID: None
Have you experienced this issue?
Rate the importance of this bug to you:

 [2018-01-17 16:48 UTC]
This is a follow-up of bug #74719, which didn't address `fwrite()`.

See for an example where this is annoying.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2018-01-17 18:57 UTC]
Additional filesystem functions that have the same or similar problems:

Optional $context arg emits warning when explicit NULL is passed to all of: copy(), mkdir(), rename(), rmdir(), unlink()

fgetss(), fgets() - NULL passed to $length is cast to int(0), emits warning
file_get_contents() - NULL passed to $maxlen results in empty string returned
 [2018-01-18 17:13 UTC]
> fwrite() should accept null for chunk size

That would constitute a BC break, though.

> for an example where this is annoying.

  $written = @\fwrite($stream, $data, $chunkSize ?: $length);
 [2018-01-18 20:09 UTC]
How would that be a BC break?
 [2018-01-18 23:50 UTC]
> How would that be a BC break?

Presently, passing NULL as third parameter to fwrite() causes
nothing to be written.  If I understand you correctly, you want
that to change so that the whole $string is written instead.
 [2018-01-19 08:04 UTC] spam2 at rhsoft dot net
bad idea - the param is defined as int which means in weak mode it will be casted and NULL becomes 0 (what you don't want) while with strict_types it is a fatal error to pass NULL - that is the expected behavior from each and every function and should stay consistent
PHP Copyright © 2001-2020 The PHP Group
All rights reserved.
Last updated: Mon Oct 26 10:01:22 2020 UTC