That's why I thnk the extension is superior to all other solutions, because
it doesn't require code generation in userland. Also, it will be possible
to backtrace to the declaration of the aspects.
2012/8/26 Rasmus Schultz
> >
> > On Thu, Aug 23, 2012 at 7:36 AM, Peter Ngu
FYI, there is already namespace support in the extension, and you can also
use type hinting on the pointcuts with interfaces/traits besides class
names.
Anthony,
2012/8/24 Anthony Ferrara
> Peter,
>
> On Fri, Aug 24, 2012 at 2:36 PM, Peter Nguyen wrote:
>
>> This is exactly the "problem" that AOP solves. I think the decorator
>> pattern is just a solution for the shortcoming of the language itself.
>
>
>
>> AOP is the future and a very awesome complement to OOP. It is a shame that
>> very few are doing it and I think this would attract some good attention
>> to
>> PHP after traits (both are horizontal reuse mechanisms).
>>
>> On Fri, Aug 24, 2012 at 2:01 AM,
s executed...
Another option is not to use wildcards and define the joint point
explicitly.
2012/8/24 Sebastian Krebs
> 2012/8/24 Peter Nguyen
>
> > Your argument is a general issue when refactoring code. Whenever you
> > change the name of a method/class, you need to change it in all
a on pastebin ;) But I have no idea how it could look
> like
>
> Regards,
> Sebastian
>
>
> Am 23.08.2012 16:36, schrieb Peter Nguyen:
>
> Hi,
>>
>> AOP
>> (http://en.wikipedia.org/wiki/**Aspect-oriented_programming<http://en.wikipedia.org/wiki
/8/23 William Betts
> On Thu, Aug 23, 2012 at 7:36 AM, Peter Nguyen wrote:
> > Hi,
> >
> > AOP (http://en.wikipedia.org/wiki/Aspect-oriented_programming) when used
> > correctly, can make your application really modular. I've seen several
> > implementat
Hi,
AOP (http://en.wikipedia.org/wiki/Aspect-oriented_programming) when used
correctly, can make your application really modular. I've seen several
implementations but they all require compiling of code beforehand. There is
however a PECL extension now (https://github.com/AOP-PHP/AOP) that enable
