这个方法让我们不需要手动复制语法树中没有变更的部分。
This method removes the need to manually copy the unchanged portions of the syntax tree.
除了这样，我们其实还可以直接复制旧的语法。
但是请注意，所复制的语法仅包含方法名称和空括号，因此必须记得参数或者必须返回内容帮助或reference面板。
Note, however, that copied syntax contains only the method name followed by empty parentheses, so you must remember the parameters or return to content assist or the reference pane.
此方法中的解析代码是从前一教程复制过来的，并稍微进行了一些修改，以获得更类似Groovy的语法。
Conf files; the parsing code from this method is copied from the previous tutorial and modified slightly to use a more Groovy-like syntax.
为创建EventSource断言的[syntax]部分，我们要先复制规范的9.1节中展示的语法，如下所示。
To create the [syntax] section for the EventSource assertion we will first copy the syntax as shown in section 9.1 of the specification, reproduced below.
但是，这种说法并不正确，因为该选项只复制窗口布局和工作集，而不复制语法高亮显示的颜色、字体大小模板等内容。
However, this is a misnomer because the option only copies the window layouts and working sets and not things like colors of syntax highlighting, font-size templates, etc.
想要做出改变，我们需要复制语法树，并替换需要变更的部分。
Changes are made by making copies of the syntax tree, replacing portions as one goes along.
使用该工具，您甚至可以通过特殊的语法(相应地称为gst -launch语法)构建复制的管道，如清单2中所示。
Using it, you can construct even complex pipelines using a special syntax, appropriately called gst-launch syntax, as shown in Listing 2.
同时还对词法分析、语法分析、预处理技术进行了讨论，并且提出一种同步复制的机制。
Meanwhile, other techniques, like word analysis, parsing, and pretreatment technology are discussed in this paper and a real-time synchronization method is presented.
同时还对词法分析、语法分析、预处理技术进行了讨论，并且提出一种同步复制的机制。
Meanwhile, other techniques, like word analysis, parsing, and pretreatment technology are discussed in this paper and a real-time synchronization method is presented.
应用推荐