2 ms·
> It's neither a "pre-compiler" nor an "optimiser" for the Zend VM. Nobody claimed otherwise.
by Someone1234 12y ago
> It's neither a "pre-compiler" nor an "optimiser" for the Zend VM.
Nobody claimed otherwise.
- masklinn 12y ago> Nobody claimed otherwise. You provided HHVM as an example[0] of "PHP pre-compilers and other optimisers". [0] that's literally what 'e.g.' means, it's an abbreviation for "exempli gratia", latin for "for example"
- Someone1234 12y agoIndeed I did, and indeed it is. You tacked on "for the Zend VM." Which was not something I said. I said: > PHP pre-compilers and other optimisers absolutely exist and are readily used (e.g. HipHop). You then said: > HHVM is a completely separate VM which does not use (or consume, or care for in any way) the Zend bytecode produced by the Zend VM. HHVM has its own separate and incompatible bytecode format called HHBC[1]. It's neither a "pre-compiler" nor an "optimiser" for the Zend VM. Which is really answering a point nobody made. It is just completely out of the blue. My post literally does not contain the term "Zend." Nor does it make any claim to what OPCode formats different things use (and really the only reason you could even talk about HipHop was that it was given as a unqualified example). So to this: > It's neither a "pre-compiler" nor an "optimiser" for the Zend VM. Is answering a point nobody made. It is like me saying, "You're wrong, the White House isn't blue, it is white!" When no claims to the blueness of the White House were made by yourself.