Some of us have rather large bodies of code written over 10-12 years that make significant use of calling $this from "incompatible contexts" (i.e. we know it's compatible, but php doesn't).
Most consider such use a sin. Could there be a compromise that would allow us evildoers to continue in our evil ways without identifying and changing every use? Perhaps "implements allowStaticCallsFromIncompatibleContexts" or somesuch? I can imagine replacing every "class ..." with "class ... implements ...", but identifying and changing every place we use an incompatible context will be very, very unpleasant. We can figure out the places that are hit most frequently using the logs, but that isn't necessarily a complete list. If this were a security issue, I'd understand making everyone go through the pain. The RFC indicates the rationale is helping users find bugs. It would be nice if those of us who would rather avoid a BC break than easily find those bugs could do so. Thanks for your consideration. - Todd -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
