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?

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

I know that it is expected behaviour, but why?

Can you tell me the reasoning behind it?

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!

sorry, but when someone don't stop argue nonsense and has nothing better to do than construct examples how nobody ever should write code *because* of the result it makes me terrible angry

PHP has not to spit out warnings all the time and in fact there a way too much places where it does (file_exists and freinds trying access a file outside openbasedir as example should just return false and be silent)

PHP would be just unusable when it acts like the reporter want it to act