It was a mistake in C++ too, fixed with the explicit keyword.

It’s not fixed since it still occurs by default. That you can work around it if you remember to is not a fix.

Indeed. My point was that it’s something also found in other widely used languages, and not a PL/1 pecularity.

> My point was that it’s something also found in other widely used language

where it is also generally considered

> an extraordinarily bad idea.

so it seems like a rather useless point?