1·The pointcut required in these situations can get unwieldy, as you can see for yourself in the following example.
在这种情况下，所需要的切入点可能会变得很难处理，从下面的例子中就可看到。
2·This is correct because that's where the advice is; however in this situation the pointcut in the concrete aspect is controlling the application of advice, and it is that which is often of interest.
这样做是正确的，因为这就是通知所在的位置；但是在这种情况下，具体方面中的切入点控制着通知的应用，而这常常是一个很有趣的地方。
3·A couple of things that are missing -- including quick fixes in aspects and content-assist of certain things such as pointcut names -- will be addressed by future versions of AJDT.
也有一些事被遗漏，其中包括方面中的快速修复和某些事情的内容辅助（例如切入点名称），这些将由 AJDT 未来的版本解决。
4·Instead of using one subaspect for my whole system, I can use many subaspects -- one per subsystem -- making it possible to write a relatively stable pointcut.
不是在 整个系统中使用一个子方面，而是使用许多子方面 —— 每个子系统一个子方面，这使得编写相对稳定的切入点成为可能。
5·The more mature the pointcut language, the easier it is to write robust pointcuts.
切入点语言越成熟， 越容易编写健壮的切入点。