Sara Golemon wrote:
Imho HHVMs syntax has the massive flaw that you cannot use docblocks on
those properties anymore, which is not the case with this RFC. All other
things equal, this is why this RFC should clearly be favored.
Inclined to agree on the matter of getters/setters (though I regard
the docblock issue as trivially solvable, and the typehint/verbosity
issue as a non-issue).
Having 10+ years of legacy code which is built on a base of previous PHP4 code, docblock is central to my own work practices. PHPEclipse simply picks up these and provides annotation from them but is still a little behind on the 'newer' changes which are now causing problems with third party libraries. I did have a look at HHVM and failed because of the legacy code, but that was a little while ago and I've not reviewed it recently. However I'm sure that there is probably as much work moving the code to HHVM as there is remaining still to move it forward toPHP5.5. It is all these little incremental changes which unless one spends time actually clearing things each version update, eventually catch up to the point where even PHP will not run code, let alone being cross compatible with things like HHVM?
Making even simple PHP code runnable everywhere is a little of a pipe dream at the moment. Even if you know how to configure the ini file to enable legacy code to run, you then have to find the correct versions of third party libraries to run with it.
--
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