Your arguments are moot, the same arguments could be used to say objects are better than php+, for example my argument would be "objects are better than frames, cuz in an object design stuff like changes better, but with php+ you gotta add a new frame sometimes". Not a very good argument huh?
PHP+ functions.
These functions simulates the behaviour of XVCL tags. So far, we have implemented
the XVCL commands <adapt>, <break>, <insert>, <insert-before>, <insert-after>,
<set>, <value-of>, and <remove>. We describe the corresponding PHP implementations
below. Loops and
ow control statements are handled by PHP language construct
How is that not just another rambunction of the GOTO construct?
All the benefits listed in the white paper could be said about spaghetti code
7.2 Advantages
The main advantage of PHP+ solution is that PHP is already a widespread language, especially
for web development. We noted that web applications usually have a high number of clones;
thus, web developers will stand to benet from PHP+. With PHP+, we eliminate the language
learning curve associated with XVCL for people who already know the language as PHP+
utilizes normal PHP constructs with a few additional functions from PHP+ Library. Developers
may then focus on grasping the concept of clones, clone extractions, and adaptation of similar
codes instead. Furthermore, PHP+ will be very intuitive to learn for non-PHP programmers
as PHP is very similar to many other mainstream programming languages like Java, C# and
C++. Hopefully, the language advantage of PHP will increase the take up rate of PHP+.
Furthermore, PHP+ is very
exible. Developers are encourage to experiment with PHP+
constructs to come up with novel ideas. For example, developers may utilize the built-in PHP
variables in addition to PHP+ variables. Developers may also perform arithmetic calculations
or call PHP functions during generation. The possibilities are almost limitless.
All moot to me.
Frames
Below are two informal descriptions, followed by a more precise definition and explanation.
1. A frame is an adaptable component on an automated software assembly line. Imagine an auto factory where, instead of having specific bumpers, fenders, and other parts to suit the specifics of each car model, we have just one generic bumper, one generic fender, and so on. Now imagine that these generic parts could be cloned and shaped to fit each car model as it came down the line. Such a fantasy would revolutionize manufacturing; and while impossible for physical parts, this is what frames do for software[13].
Sounds like an abstract class.
2. A frame is a recipe for "cooking up" a (program) text. Its instructions say how to blend its ingredients -- chunks of frame-text within itself -- with the ingredients from other frames. The “chef” is a frame processor that carries out the instructions, i.e. the frame commands, which alter (add, modify, delete) ingredients as necessary, to suit the main recipe.
Sounds like a class definition
Formally, a frame is a procedural macro