On 14/04/16 08:52, André Rømcke wrote: > * https://wiki.php.net/rfc/propertygetsetsyntax-v1.2
This actually summarises many of the problems all of these 'extras' are creating for very little gain. 'Seconds' is a 'Traditional Property' so is untyped and if accessed as a value from some OS's will be a floating point number while others will be working with a 32bit or 64bit integer. Simply adding a 'type' to this traditional property does not address a number of potential bugs in using 'Seconds' as a simple variable. 'Hours' is now an object in it's own right, so how is it really any different to 'TimePeriod' it is essentially a class with a set of associated functions, and all of baggage to make it work. 'Final' is just another function to be added to the 'Hours' object? I keep banging on about this, but in addition to 'Final', set, get, isset, unset, and all of the trait/reflection functions to define/inspect why would you not expect facilities also to validate the range of a number, it's accuracy limits if a float, and the sizes of the object if it's a string? The second you move beyond the basic variable as found in PHP4 have you not simply upgraded to an object and all the baggage that is essential to make that work. Even 'null' is simply a state that the object takes since it's not something that can be assigned as a value in the 'register' that is being used to store it's value? I don't see how the idea of 'optimizing' the compiled code has any bearing on handling a 'typed property' when one has to have an object to contain even the simple of type information? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
