language extension

The key difference among the AOP tools when it comes to build environment integration is whether the tool uses a language extension.

Metadata can be used for language extension purpose.

This may be rectified in future by a Java language extension; see the sidebar entitled " Metadata and JSR 175" for more on this.

Create a text file with the appropriate language extension for each example that you want to compile.

What are the build integration trade-offs of language extension?

The first uses a language extension, _at_, to specify where a variable should be located.

Similar mechanisms as AspectJ without the language extension.

Language extension requires the use of an extended compiler and related tools.

But that makes using that XML in a language extension, like E4X, much harder to do.

Call a script language extension function.

Do yourself a favor and check out this language extension.

This is one area where the downsides of language extension crop up.

See Resources to learn more about the different AOP implementations and Java language extension.

Language extension or versioning, on the other hand, the state is unchanged, but the way that data is represented has changed.

In this section, I've outlined the main trade-offs of AspectJ's language extension approach from the perspective of build integration