On 09/02/15 23:47, Yasuo Ohgaki wrote: > The RFC draft is ready. > https://wiki.php.net/rfc/dbc2
> These contracts are evaluated development time only. Therefore, there is no > performance penalty with DbC. Sorry but that makes no sense to me at all. If this is something only to use with an IDE then why does it have to have anything that is visible at 'run time'? This seems to be going down the track of "we will be compiling this eventually" and that is just not what PHP *IS* about. These are more hints, but assume that at runtime what they define is not relevant? ALL of this discussion on type hinting how ever it is handled is simply sidestepping the major plus on PHP with associative arrays. I see no point expanding every database record read to 'magic access functions' for multiple variables and it *IS* the scalar values stored in these arrays that needs the 'hint/constraint' control. I am getting even more confused about just what all the different factions are trying to achieve. Yes I know I can totally ignore all of it, but with my current tools losing traction because of all the 'better ways of working' what in my opinion IS the best way to allow different factions to add their own pet style is drowning simple clean solutions such as docblock. -- 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
