some gossip
First of all, the original intention of this writing. I've got a blueprint document for Zend Engine 2.0 for some time now (you can also go to the address in the Resources section to download it back to see), after reading the impulse to write a comment-because the document describes the next generation of PHP (as the current mainstream development language) Will be a language that is more in line with existing object-oriented development habits, at least by being more endowed with object-oriented features. But the problem with this is whether the language of PHP, the current mainstream development language, is an initial target for web rapid development. This question seems to need some comment articles to discuss, and I would like to make my own point of view. But then some busy things will this impulse a little bit back to the belly, until the recent period of time to think again, so I read a few times design blueprint document, hence this article. (When I got this English document, I also have the plan to translate this blueprint document into Chinese, but considering that one is not the final blueprint, the second is that we should cultivate the habit of reading the original text directly, and the third is that translation will inevitably bring some obscure places, so I have to give up temporarily. However, when written in this article, or decided to "risk" translation once, can not accurately convey the place also ask you to correct. ）
The second is an explanation of the focus of this discussion-in this commentary I will review the object-oriented features that are greatly enhanced in future PHP, which is now the mainstream development language. If you are a developer of PHP (as the current mainstream development language), then I suppose you should be aware of some of the object-oriented features of PHP (as the mainstream development language of today), but because of the general PHP (which is now the mainstream development language) for "extreme rapid development environment" (This is my own sporogenous of a word, indicating that some customer-oriented development of the site, characterized by a very short duration and customer requirements are not very clear), so the real mass use of its object characteristics of developers and development projects are not many; In addition, the existing PHP (as the mainstream development language now) The object model is less vulnerable than C + + and Java, and also limits the use of this feature. But in future versions of PHP, which is now the mainstream development language, the focus is on the object-oriented model of the language, perfecting many of the bad features in the existing version and adding other features. So the future of discussing PHP, which is now the mainstream development language, is focused on the object-oriented nature of PHP, which is now the mainstream development language.
Okay, let's get to the point and see what's new with Zend Engine 2.0.
inductive zend Engine 2.0 Design Blueprint (draft)
It is clear from the blueprint (draft) that the next generation Zend engine is based on a new object-oriented model. If you've ever used the object-oriented nature of the existing PHP 4, which is now the mainstream development language, you might find it a bit awkward at the same time finding some sense of Java or C + +-not only in the lack of object-oriented syntax, And sometimes they get unexpected results-all because of the less elegant object-oriented model of Zend Engine 1.0, which currently supports PHP 4 as the current mainstream development language.
In short, the next generation of Zend engine will move closer to Java, drawing heavily on its object-oriented model. From the type of improved features, it should be divided into three categories: the first class is the improvement and enhancement of the existing object-oriented model, including the definition of builders and destructors, the addition of private member variables, static member variables, multiple inheritance, overload and other object-oriented features, the second is to control the flow of changes and additions and deletions, such as the addition of the form of try/catch/throw violation of the mechanism; the third class is about function modification and additions and deletions, such as the increment function for the string offset. (For each class of improvement details, you can refer to the documentation listed in the Resources section.) It can be seen that, through the first and second classes of improvements, PHP (as the current mainstream development language) is gradually refining itself into a language with object-oriented features.
But the problem is precisely the result:
On the positive side, the language of object-oriented features is more popular in today's programming world (even though the language itself is not built on an object-oriented basis, but by increasing the number of defined objects so that the language does not fall behind the tide)-in this sense, Zend Engine 2.0 makes PHP (now the mainstream development language) of object-oriented support will be from the current exploratory contact to the future of comprehensive advocacy, it seems more in line with the trend of programming language development, and in the construction of enterprise-class applications (which is the current mainstream development language is now often criticized) , an object-oriented approach to modeling and implementation is already a de facto standard, and the improvement of PHP, which is now a mainstream development language, may cater to this need and address the weaknesses of the language itself.
On the negative side, it doesn't seem to make sense to dedicate a new version of PHP, which is now a mainstream development language, to developers. PHP (as the mainstream development of the current language) is widely used for reasons, in addition to source code disclosure and cross-platform, and so on, to adapt to the Internet station construction of simple, fast Web programming features I am afraid it is also important. Very short study time, friendly language style (especially if you are familiar with C) and a large number of expansion of the class library function is strong enough to prove it, but if the next version of such a language is transformed into a similar object-oriented language, not only will the original large number of developers in a short period of time, And it's very bad for attracting new developers-since there's a language like Java, why learn PHP (as the mainstream development language now)?
http://www.bkjia.com/PHPjc/509142.html www.bkjia.com true http://www.bkjia.com/PHPjc/509142.html techarticle Some of the first is the original intention of this paper. I've got a blueprint document for Zend Engine 2.0 for some time now (you can also go to the address in resources to download it back ...)
