11  

knitr evaluates all chunks in a common environment (returned by knit_global()). This is by design; just like all code in a source file runs in the same environment, all chunks are executed in a common environment. The same applies to child documents because they are (in principle, not technically) just a part of the main document, externalized to another file.

knitr評估公共環境中的所有塊（由knit_global（）返回）。這是設計的;就像源文件中的所有代碼都在同一環境中運行一樣，所有塊都在公共環境中執行。這同樣適用於子文檔，因為它們（原則上，在技術上）不僅僅是主文檔的一部分，而是外部化到另一個文件。

This does not necessarily lead to spaghetti code: Nothing prevents users from using functions and other objects to organize code/data in knitr documents. But probably few users do so …

這並不一定會導致意大利面條代碼：沒有什么能阻止用戶使用函數和其他對象來組織knitr文檔中的代碼/數據。但可能很少有用戶這樣做......

So the reason why there are no encapsulation mechanisms for chunks/child documents is that they are supposed to share a common environment as they are part of one (main) document.

因此，沒有用於塊/子文檔的封裝機制的原因是它們應該共享公共環境，因為它們是一個（主）文檔的一部分。

However, it is possible to include child documents in a way that gives the user control over the objects child documents and the main document share. The solution is based on the function knit_child() which is very similar to the chunk option child. The advantage of calling knit_child() directly (vs. implicitly via the child option) is the possibility to set the envir argument which defines "the environment in which the code chunks are to be evaluated" (from ?knit).

但是，可以以允許用戶控制對象子文檔和主文檔共享的方式包括子文檔。該解決方案基於函數knit_child（），它與塊選項子元素非常相似。直接調用knit_child（）（通過子選項隱式調用）的優點是可以設置envir參數，該參數定義“評估代碼塊的環境”（來自？knit）。

Around knit_child(), I wrote the wrapper IsolatedChild to simplify matters:

圍繞knit_child（），我編寫了包裝器IsolatedChild來簡化問題：

IsolatedChild <- function(input, ...) {

  evaluationEnv <- list2env(x = list(...), parent = as.environment(2))
  cat(asis_output(knit_child(input = input, envir = evaluationEnv, quiet = TRUE)))
  return(evaluationEnv)
}

Arguments passed to ... will be available in the child document. (Name them, see example below.) The function returns the environment in which the child document has been evaluated.

傳遞給...的參數將在子文檔中提供。 （將它們命名，請參見下面的示例。）該函數返回已評估子文檔的環境。

Specifying parent in list2env is crucial and I chose as.environment(2) according to this answer. Otherwise parent would default to parent.frame(), thus exposing objects in knit_global() to the child document.

在list2env中指定parent是至關重要的，我根據這個答案選擇了as.environment（2）。否則，parent將默認為parent.frame（），從而將knit_global（）中的對象暴露給子文檔。

assign can be used to make objects returned from IsolatedChild available in the global environment.

assign可用於使從IsolatedChild返回的對象在全局環境中可用。

Note the cat(asis_output()) construction around knit_child which ensures that the output from the child document is correctly included in the main document, regardless of the results setting in the current chunk.

請注意knit_child周圍的cat（asis_output（））構造，它確保子文檔的輸出正確包含在主文檔中，而不管當前塊中的結果設置如何。

Before turning to the example, two final remarks:

在轉到示例之前，最后兩個評論：

• If the child and the main document are not supposed to share any objects, this approach is overly complex. Simply knit the child document and use \include{} to include it in the main document.
• 如果孩子和主文檔不應該共享任何對象，這種方法過於復雜。只需編織子文檔並使用\ include {}將其包含在主文檔中。
• This approach might come with some pitfalls. Especially the enclosing environment of the "isolated child" needs caution because the search path might look different than expected. Note that main and child document share knitr options. Besides, both documents could interact via side effects (options(), par(), opened devices, ...).
• 這種方法可能會帶來一些陷阱。特別是“孤立的孩子”的封閉環境需要謹慎，因為搜索路徑可能看起來與預期的不同。請注意，主文檔和子文檔共享knitr選項。此外，兩個文檔都可以通過副作用（options（），par（），打開的設備，......）進行交互。

Below a complete example / demo:

下面是一個完整的示例/演示：

• The chunk inputNormal does nothing special, it's just a demonstration of the normal behavior. inputHidden demonstrates the use of IsolatedChild(), passing two variables to the child document.
• 塊inputNormal沒有什么特別之處，它只是對正常行為的演示。 inputHidden演示了IsolatedChild（）的使用，將兩個變量傳遞給子文檔。
• IsolatedChild() returns these two values along with a third object created in the child.
• IsolatedChild（）返回這兩個值以及在子項中創建的第三個對象。
• check demonstrates that the objects passed to/created in the "isolated child" do not pollute the global environment.
• check表明傳遞給“隔離子”的對象/創建的對象不會污染全局環境。
• import shows how assign can be used to "import" an object from the "isolated child" to the global environment.
• import顯示了如何使用assign將對象從“孤立子”導入到全局環境。

main.Rnw:

main.Rnw：

\documentclass{article}
\begin{document}

<<setup>>=
library(knitr)

objInMain <- TRUE

IsolatedChild <- function(input, ...) {

  evaluationEnv <- list2env(x = list(...), parent = as.environment(2))
  cat(asis_output(knit_child(input = input, envir = evaluationEnv, quiet = TRUE)))
  return(evaluationEnv)
}

@

<<inputNormal, child="child_normal.Rnw">>=
@

<<inputHidden, results = "asis">>=

returned <- IsolatedChild(input = "child_hidden.Rnw",
                          passedValue = 42,
                          otherPassedValue = 3.14)
cat(sprintf("Returned from hidden child: \\texttt{%s}",
            paste(ls(returned), collapse = ", ")))
@

<<check, results = "asis">>=
cat(sprintf("In global evaluation environment: \\texttt{%s}",
            paste(ls(), collapse = ", ")))
@

<<import, results = "asis">>=
assign("objInChildHidden", returned$objInChildHidden)
cat(sprintf("In global evaluation environment: \\texttt{%s}",
            paste(ls(), collapse = ", ")))
@
\end{document}

child_normal.Rnw:

child_normal.Rnw：

<<inChildNormal>>=
objInChildNormal <- TRUE # visible in main.Rnw (standard behaviour)
@

child_hidden.Rnw:

child_hidden.Rnw：

Text in \texttt{child\_hidden.Rnw}.

<<inChildHidden>>=
objInChildHidden <- TRUE

print(sprintf("In hidden child: %s",
              paste(ls(), collapse = ", ")))


# Returns FALSE.
# Would be TRUE if "parent" weren't specifiet in list2env().
exists("objInMain", inherits = TRUE)
@

main.pdf:

main.pdf：