Re: [RFC] Safe Casting Functions

Hi! > Yes, that’s still merely an implementation detail. If HHVM decides to > make explode() into an opcode, it’s not a language change. It is not > any different if PHP does the same. If HHVM decides to introduce new type handling rules, however, it is. Even if they are going to be called using ( and ). >> You propose to add completely new type conversion rules into the >> engine, in addition to ones already present and used there. It's >> not the same as merely changing how the engine internally runs >> pre-existing code. The new rules are definitely becoming major part >> of the language, not an implementation detail of some random >> function like str_pad. > > No, they’re just a set of new validation functions. No, they are not. They are new engine primitives for handling type conversions. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/