Re: Integer operations are implementation-defined

Hi! > This wouldn’t close the door to them IMO, it just means that PHP > can’t have them for 5.6, and I think that’s reasonable. I suppose you OK, if we follow 5.6, and I think it makes sense to, then indeed we should write what 5.6 does, and if we change it in 7.0 we can update the spec to version 2.0 just as other languages do :) > In summary, arbitrary-precision integers don’t make any sense when > most code relies on integers being fixed-size, and without changing > what the operators do. We can always change what they do in a later > iteration of the specification. I don't think this is such a big deal, but once we've agreed to follow 5.6 this would be off topic anyway :) So let's follow 5.6 unless there's a very good reason not to (e.g. some behavior that is kept around only for BC or other like reasons and that we actually don't like so we want to allow others to get rid of it). -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/