Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62513
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mindplay.dk from 209.85.212.42 cause and error)
MIME-Version: 1.0
Date: Sun, 26 Aug 2012 13:51:57 -0400
Message-ID: <CADqTB_gJR_qR7CXqaysJ0Qt9iriqZhjscemNoKOh-MmS-8hAxg@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=20cf3079c0968001d804c82edd6c
Subject: Re: [PHP-DEV] Aspect Oriented Programming in PHP
From: rasmus@mindplay.dk (Rasmus Schultz)

--20cf3079c0968001d804c82edd6c
Content-Type: text/plain; charset=ISO-8859-1

>
> On Thu, Aug 23, 2012 at 7:36 AM, Peter Nguyen <peter@likipe.se> wrote:
> I know very little about AOP and don't pretend to know a lot, but how
> would we benefit
> from directly adding it into core instead of taking the approach FLOW3 did?


as I see it, the problem with AOP in PHP is the same as with any other
technique that requires code-generation, in some form or another,
including code-manipulation, pre-processing, transpilers, and so
forth: traceability of errors.

languages that are popular as intermediary languages generally support a
directive that makes it possible to trace errors back to their source.

I raised this issue on the list recently, and no one seemed to react with
any interest...

--20cf3079c0968001d804c82edd6c--