Also I remember creating this Calendar object with Period based on an article from your team 😀
gist.github.com/nyamsprod/c1...

I did this for the Period package and it works like a charm
github.com/thephpleague...

I hope theses examples explain the goal. To have total control over the functions behaviour.

That what does it wraps them

`fopen` returns false on error ... so fopen is a code smell is that what you are saying 🤔 and that's the case for most php internal functions. so the solution is for a known behaviour of PHP not for userland code where I do not expect developer to use E_USER_WARNING + false but rather exceptions

because the method already return false why would I want to know twice that there's a error ... If the function was returning an Error like a ValueError I would not have to suppress anything. I already know I have false returned it's twice the same information for no real added value.

A code smell ? Why ?