Req #75000 [Com]: getcwd() does not raise error when it fails

Edit report at https://bugs.php.net/bug.php?id=75000&edit=1 ID: 75000 Comment by: spam2 at rhsoft dot net Reported by: marco dot agnoli at me dot com Summary: getcwd() does not raise error when it fails Status: Not a bug Type: Feature/Change Request Package: *General Issues Operating System: OS X PHP Version: 7.1.7 Block user comment: N Private report: N New Comment: and how would a warning help here? sorry but the way you argue I highly recommend refrain from developing at all because when you refuse to understand that it is idiotic not to check return values and your last post is just dumb only an idiot is using system() all the time only an idiot is using getcwd() instead __FILE__ to build a path only an idiot allows system() and friends on production servers only an idiot continues to refuse check return values frankly put your fingers away from software - people which argue and write code like you do are the reason for the bad reputation of PHP because every monkey is able to write and publish some crap code and refuses to learn doing it right Previous Comments: ------------------------------------------------------------------------ [2017-08-15 02:02:21] marco dot agnoli at me dot com I have thought about this issue once again and actually getcwd can do some serious damage if used incorrectly. I'm aware that it is unlikely for getcwd() to fail but consider the following piece of code: <?php $path = \getcwd().'/bin/'; system('rm -rf '.\escapeshellarg($path)); ?> Since PHP converts false to an empty string the folder we attempt to remove would be "/bin" and we wouldn't even know about it! ------------------------------------------------------------------------ [2017-07-28 10:02:54] spam2 at rhsoft dot net because it would a stupid design when i have to wrap every piece in additional checks or use @ to supress errors which has a large performance impact when a return value you can check is so much more clean Returns the current working directory on success, or FALSE on failure what the hell would you gain when that below triggers a random warning? what you have here is a proper error handling - no thans - i don't want the need to spit @getcwd() all around the code and yes we run error_reporting EALL | E_STRICT for 15 years in production on some hundret customers and the admin group receives every 30 minutes a mail with the current state of the global php error-log - so what you don't want is random warnings with no benefit in a proper environment $cwd = getcwd(); if($cwd !== false) { // do something } else { // properly handle the error } ------------------------------------------------------------------------ [2017-07-28 09:33:01] marco dot agnoli at me dot com I know that it is expected behaviour, but why? Can you tell me the reasoning behind it? ------------------------------------------------------------------------ [2017-07-28 09:12:53] kalle@php.net Both these cases are expected behavior for realpath() and getcwd() to be silent and return false. There are potential other functions that mimic similar behaviors, but in the end it is up to the end user to test the return value of these functions ------------------------------------------------------------------------ [2017-07-28 06:12:40] marco dot agnoli at me dot com Same can be said for the realpath function: ``` <?php error_reporting(E_ALL); var_dump(realpath('non-existing-path')); ?> ``` realpath() expects a valid path, so why not raise an error when no valid path was specified? ------------------------------------------------------------------------ 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 https://bugs.php.net/bug.php?id=75000 -- Edit this bug report at https://bugs.php.net/bug.php?id=75000&edit=1