|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Request #31424 Make mode optional on mkdir
Submitted: 2005-01-06 03:07 UTC Modified: 2018-03-10 13:55 UTC
From: Assigned:
Status: Open Package: Directory function related
PHP Version: 5CVS-2005-01-06 (dev) OS:
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
Solve the problem:
26 - 1 = ?
Subscribe to this entry?

 [2005-01-06 03:07 UTC]
As all but the first parameter of mkdir are optional and non sequential, it makes sense to be able to pass NULL to each if a later param is required.

E.g. mkdir('some/path/foobar', null, true);

Reproduce code:
This patch adds this functionality:

Included in the report:

--- \repository\php-src\ext\standard\file.1.395.c	Mon Dec 13 10:21:53 2004
+++ \repository\php-src\ext\standard\file.c	Thu Jan 06 12:29:41 2005
@@ -1372,7 +1372,7 @@
 	char *dir;
 	php_stream_context *context;
-	if (zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, "s|lbr", &dir, &dir_len, &mode, &recursive, &zcontext) == FAILURE) {
+	if (zend_parse_parameters(ZEND_NUM_ARGS() TSRMLS_CC, "s|!lbr", &dir, &dir_len, &mode, &recursive, &zcontext) == FAILURE) {


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2018-03-10 13:55 UTC]
-Package: Feature/Change Request +Package: Directory function related
 [2018-03-10 13:55 UTC]
I fail to see why `NULL` would be preferable to the more explicit
`0777` here.  IMHO: won't fix.
PHP Copyright © 2001-2019 The PHP Group
All rights reserved.
Last updated: Sat Oct 19 08:01:28 2019 UTC