mirror of
https://github.com/fverdugo/XM_40017.git
synced 2025-12-29 10:18:31 +01:00
build based on b7db8f1
This commit is contained in:
@@ -8046,7 +8046,7 @@ a.anchor-link {
|
||||
</div>
|
||||
<div class="jp-InputArea jp-Cell-inputArea"><div class="jp-InputPrompt jp-InputArea-prompt">
|
||||
</div><div class="jp-RenderedHTMLCommon jp-RenderedMarkdown jp-MarkdownOutput" data-mime-type="text/markdown">
|
||||
<h3 id="Useful-macro:-@spawnat">Useful macro: <code>@spawnat</code><a class="anchor-link" href="#Useful-macro:-@spawnat">¶</a></h3><p>You have provably realized that in order to use <code>remotecall</code> we have written auxiliary anonymous functions. They are needed to wrap the code we want to execute remotely. Writing these functions can be tedious. Happily, the macro <code>@spawnat</code> generates an auxiliary function from the given block of code and calls <code>remotecall</code> for us. For instance, the two following cells are equivalent.</p>
|
||||
<h3 id="Useful-macro:-@spawnat">Useful macro: <code>@spawnat</code><a class="anchor-link" href="#Useful-macro:-@spawnat">¶</a></h3><p>You have probably realized that in order to use <code>remotecall</code> we have written auxiliary anonymous functions. They are needed to wrap the code we want to execute remotely. Writing these functions can be tedious. Happily, the macro <code>@spawnat</code> generates an auxiliary function from the given block of code and calls <code>remotecall</code> for us. For instance, the two following cells are equivalent.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -8946,7 +8946,7 @@ d) 32</code></pre>
|
||||
</div>
|
||||
<div class="jp-InputArea jp-Cell-inputArea"><div class="jp-InputPrompt jp-InputArea-prompt">
|
||||
</div><div class="jp-RenderedHTMLCommon jp-RenderedMarkdown jp-MarkdownOutput" data-mime-type="text/markdown">
|
||||
<p>We have activated the current folder. Now let's see which is the active project in another process, say process 2. You will see that process 2 is provably still using the global package environment.</p>
|
||||
<p>We have activated the current folder. Now let's see which is the active project in another process, say process 2. You will see that process 2 is probably still using the global package environment.</p>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user