I guess were nuts, because thats how it works. Your PHP Scripts are redirected to the AOPHP Weaver, witch then takes your code, weaves in the aspects, and sends the new PHP w/ Advice added to PHP to be parsed as usual
the purpose of the aspect is essentially to be able to change the way the program executes with out changing the code. users should not have to register there functions to there advice, they should be able to simply code the advice in the aspect file and it automatically be weaved into the script, they should not have to make any modifications to the PHP script itself for aspects.
We have already spoken to Gregor Kiczales (the patent holder) about the AOPHP project and he was greatly interested in it. He has encouraged us to continue the development of this project, so i do not tihnk he will be trying to sue us.
Slashdot Mirror
I guess were nuts, because thats how it works. Your PHP Scripts are redirected to the AOPHP Weaver, witch then takes your code, weaves in the aspects, and sends the new PHP w/ Advice added to PHP to be parsed as usual
the purpose of the aspect is essentially to be able to change the way the program executes with out changing the code. users should not have to register there functions to there advice, they should be able to simply code the advice in the aspect file and it automatically be weaved into the script, they should not have to make any modifications to the PHP script itself for aspects.
In the Testing we have performed thus far, it appears to have no noticable impact on the speed of the execution of the scripts.
We have already spoken to Gregor Kiczales (the patent holder) about the AOPHP project and he was greatly interested in it. He has encouraged us to continue the development of this project, so i do not tihnk he will be trying to sue us.