|Using AOP for writing compilers. email@example.com (Oliver Wong) (2006-03-14)|
|Re: Using AOP for writing compilers. firstname.lastname@example.org (2006-03-22)|
|Date:||22 Mar 2006 23:38:35 -0500|
|Posted-Date:||22 Mar 2006 23:38:35 EST|
Yes, AOP can bring lots of benefits for compiler writing. Please check
out the paper
"Separation of Concerns in Compiler Development Using
I believe that is exactly what you are looking for.
Oliver Wong wrote:
> Given that Aspect Oriented Programming seems to mainly be about
> separating cross-cutting concerns, it seems like an ideal paradigm for
> compiler writing. However, after several Google searches, I was unable
> to find any documentation or references on any attempts to use AOP for
> compiler writing other than this essay on TreeCC:
> The essay is rather short and light, and a lot of the problems the
> author mentions about the other approaches that drove him/her to AOP
> simply weren't big issues for me.
> I guess what I'm getting at is that while it might be interesting
> to try an AOP approach, the benefits (for example in clarity or
> modularity of source code) do not seem to be so great as to be worth,
> for example, rewriting an existing compiler.
> Are there any other papers out there on using AOP for compiler
> writing? Preferably ones which specifically look at what benefits AOP
> brings to the table?
> - Oliver
Return to the
Search the comp.compilers archives again.