In addition, the following categories of kindless pointcuts are supported.
另外，也支持以下没有类型的切入点分类。
Figure 2: Pointcuts in the trace aspect.
图2：跟踪方面中的切入点。
Figure 6: Pointcuts for argument checking.
图6：用于检查实参的切入点。
Cool things you can do with AspectJ pointcuts
通过AspectJ切入点你能做的很棒的事情
Pointcuts, advice, and inter-type declarations.
切入点、通知和类型间声明。
The learning curve for using new pointcuts is pay as you go.
使用新切入点的学习曲线是随用随学。
Concise aspect declarations and static checking for pointcuts.
简洁的方面声明和切入点的静态检查。
Many aspects cannot be expressed without fine-grained pointcuts.
没有精细的切入点，许多方面就不能表达。
To understand pointcuts, you'll need to know what a join point is.
要理解Pointcut，必需知道joinpoint是什么。
In addition, the following categories of kindless pointcuts are supported
另外，也支持以下没有类型的切入点分类
Pointcuts can describe sets of join points by means of explicit enumeration.
切入点可以通过显式枚举方式描述连接点集合。
Pointcuts select join points and collect the context at selected join points.
切入点选择连接点，并收集所选的连接点处的上下文。
We were able to do this easily because both pointcuts have an Employee parameter.
因为每个切点都有一个雇员参数，因此，我们可以很容易地完成这项工作。
The more mature the pointcut language, the easier it is to write robust pointcuts.
切入点语言越成熟， 越容易编写健壮的切入点。
The first approach to resolving this is to develop robust pointcuts from the start.
解决这个问题的第一个方法是从一起开始就开发健壮的切入点。
Join points are encapsulated in quantifiable expressions (queries) called "pointcuts."
连接点被封装在被称作“pointcuts(横切点)”的可以计量的扩展(查询)之中。
Pointcuts are then used to define the join points at which advice in the aspect applies.
然后可以用切入点来定义将在其上应用方面中的通知的连接点。
Pointcuts are just the first step in a design approach that minimizes entangling assumptions.
切入点仅仅是减少重重假设的设计方法的第一步。
Trace defines three pointcuts; two of them are concrete and one abstract, as shown in Figure 2.
跟踪定义了三个切入点；其中的两个是具体的，一个是抽象的，正如图2所示。
Some primitive pointcuts match only join points of a specific kind (for example, method executions).
有些原生切入点只与特定类型的连接点匹配（例如，方法执行）。
Signature-based pointcuts cannot capture the join points needed to implement certain crosscutting concerns.
基于签名的切入点不能捕获实现某种横切功能所需要的连接点。
Using pointcuts, you can easily define situations in which a timestamped object should have its stamp updated.
使用Pointcut，您可以方便地定义环境，加上时间戳记的对象将在其中更新戳记。
Pointcuts and advice appear with their own icons, which indicate the kind of the advice (for example, before, after).
切入点和声明出现时有它们自己的图标，这些图标指出了通知的种类（例如：before、after 等）。
On the flipside, a broader set of pointcuts does have a pay-as-you-go property, as pointcuts can be learned as needed.
从反面来看，更广泛的切入点集合确实具备量入为出的属性，因为切入点可以边用边学。
The new types of nodes are aspects, pointcuts, advice, intertype declarations, and declare statements, as shown below.
对AspectJ新增的节点类型有aspect、pointcut、advice、intertypedeclaration以及declarestatement，如下图所示。
Pointcuts allow you to unambiguously reference multiple join points in the program code (method content and processes).
衡切点允许您明确的引用程序代码(方法内容和过程)中的多个连接点。
The above method for describing pointcuts has proved useful, but at present there is no analogous method for describing process pointcuts.
上述用于描述横切点的方法已经被证明是有效的，但是目前并没有一种类似的方法可以用来描述过程横切点。
There are certain advantages to annotation properties-based pointcuts, especially for compile-time checks and efficiency of static selection.
基于注释属性的切入点有某些好处，特别是对于编译时检查和静态选择的效率。
Pointcuts written using a template language rather than plain text could be fed to a process enactment engine in order to generate real-time process events.
横切点使用一个模板语言来撰写，而不是使用纯文本来撰写，以便生成实时的过程事件。
The within pointcut is similar to this(), except that ajc detects it entirely at compile time (most pointcuts can discriminate based on run-time information).
除了ajc在编译时彻底检测 withinPointcut 以外（大多数Pointcut可以根据运行时信息区别开来）， withinPointcut类似于this()。
应用推荐