Is this something you are still interested in seeing?

Personally this looks nonsensical; objects aren't integers and so you need to do any conversion yourself.

Wow, it's been a while since I posted this. It's more consistent with other type casting operations to type cast to the traditional expected value if applicable (even integers as an ordinal value). However, to obtain this consistency it would hurt backwards compatibility. I would be gracious if there was a release of PHP that focused on consistency issues that have been neglected for reasons of backwards compatibility, which would likely entail a new major version. If that's not the direction that the PHP developers are interested in, you can go ahead and close this or otherwise assign it to a new larger version number.

1. AFAIK when casting something that is neither a string nor a number into an integer it can only be 0 or 1 and are you really looking for chr(0) when calling strpos(foo, FALSE)? I'd say a warning would be much better than casting. Anyways...

2. Objects have no ways to be cast into an integer however they may have a way to be cast into a string so instead of trying to cast integer which can only fail why not try to cast into string? This would be a very small BC break because previously this emitted an error message so probably it is not in any code.

I totally agree with the initial poster.

objects implementing __toString() should be converted to a string automatically when used for parameters which are expected to be string.

my example is:

<?php

class stringable {
    function __toString() {
        return "abc";
    }
}

$s = new stringable();

// AS EXPECTED: converts the object into a string executes the replace in the same fashion with a plain php string
var_dump(str_replace('a', 'x', $s)); // print xbc

// both of the following lines emit a warning but are expected to use the given object as a string and proceed
// both emit: Notice: Object of class stringable could not be converted to int
var_dump(strpos('abcd', $s));
var_dump(stripos('abcd', $s));

see https://3v4l.org/Bf3Ah

> I would be gracious if there was a release of PHP that focused
> on consistency issues that have been neglected for reasons of
> backwards compatibility, which would likely entail a new major
> version.

That would be PHP 8.0, where the issue at hand has been resolved,
see <https://3v4l.org/7X8QE>.