# With vs. Block scoping of parameters for Plot

A very basic question..

Why does Block work, but not With, to specify value of a parameter for a function to be plotted?

Example:

    f[x_] := c Cos[x]

Block[{c = 2}, Plot[f[x], {x, 0, \[Pi]}]] With[{c = 2}, Plot[Evaluate[f[x]], {x, 0, \[Pi]}]]
(* no graph plotted *) • I do realize that I could make the parameter an additional argument to the function, that is, use f[x_, c_] := c Cos[x], but in the actual, much more complicated situation I face (namely, using ParametricPlot3D), that seems awkward. Sep 30 '18 at 20:59
• Have you seen this? Pay attention to what is called lexical scoping in Leonid's answer. Sep 30 '18 at 21:01
• You may be interested in this great answer (also by Leonid ) Sep 30 '18 at 21:03
• By the time when With operates, Plot is still left unevaluated, which means that With only sees f[x] - it doesn't see c, which is why this doesn't work. Actually, yes, as the others pointed out, this is exact dupliate of this. Sep 30 '18 at 21:04
• Whereas With[{c = 2}, Plot[c Cos[x], {x, 0, Pi}]] does work. Sep 30 '18 at 21:06

Reproducing my old SO answer to a nearly identical question here, per request of WReach

Your question is not so much about Plot as it is about how the scoping constructs work. The main confusion here is due to the differences between lexical and dynamic scoping. And the main culprit is this definition:

f[x_] := c Cos[x]


The problem with it is that it makes f implicitly depend on the global symbol (variable) c. I am very much against this sort of constructs, since they lead to infinite confusion. Now, what happens can be illustrated with the following example:

In:= With[{c = 2}, f[x]]

Out= c Cos[x]


To understand why this happens, one must understand what the lexical scoping means. We know that With has a HoldAll attribute. The way it works is that it looks are what is literally inside it, and substitutes variables found literally in the body with their values from the declaration list. This happens during the variable-binding stage, and only then it lets the body to evaluate. From this, it is clear that the following will work:

In:= With[{c = 2}, Evaluate[f[x]]]

Out= 2 Cos[x]


This worked because Evaluate overrides the "part" of HoldAll attribute of With, forcing the body to evaluate before anything else (variable binding, and subsequent body evaluation). Therefore, it would be completely equivalent to use just With[{c = 2}, c Cos[x]] above, as you can see with Trace. The next part of the puzzle is why

With[{c = 2}, Plot[Evaluate @ f[x], {x, 0, Pi}, AxesOrigin -> {0, 0}]]


does not work. This is because this time we do not evaluate the body first. The presence of Evaluate affects only f[x] inside Plot, but not the evaluation of Plot itself inside With. This is illustrated by

In:= With[{c = 2}, q[Evaluate @ f[x]]]

Out= q[c Cos[x]]


Moreover, we do not want Plot to evaluate first, since then the value of c will not be defined. However, all that With sees is f[x], and since the parameter c is not literally present in there (lexical scoping, remember), no substitution will be made. Should we use Block here, and things will work, because Block uses dynamic scoping, meaning that it redefines values in time (part of the execution stack if you wish), rather than in place. Therefore, using Block[{c = 2}, ff[x]] where ff implicitly depends on c is (roughly) equivalent to c = 2; ff[x] (with the difference that c resumes its global value after the Block scope is left). So,

In:= Block[{c = 2}, q[Evaluate @ f[x]]]

Out= q[2 Cos[x]]


To make the With version work, you'd have to inject the expression for f[x] (r.h.s), for example like so:

In:= Unevaluated[With[{c = 2}, q[f[x]]]] /. DownValues[f]

Out= q[2 Cos[x]]


Note that this won't work:

In:= With[{fx = f[x]}, With[{c = 2}, q[fx]]]

Out= q[c Cos[x]]


But the reason here is quite subtle: while outer With evaluates before the inner one, it spots the variable name conflicts and renames its variables. Rules are much more disruptive, they don't respect inner scoping constructs.

EDIT

If one insists on nested With-s, here is how one can fool the name conflict resolution mechanism of With and make it work:

In:= With[{fx = f[x]}, With @@ Hold[{c = 2}, q[fx]]]

Out= q[2 Cos[x]]


Since outer With can no longer detect the presence of inner With (using Apply[With, Hold[...]] makes the inner With effectively dynamically generated), it does not make any renamings, and then it works. This is a general trick to fool lexical scoping name resolution mechanism when you don't want renaming, although the necessity to use it usually indicates a bad design.

END EDIT

But I digressed. To summarize, making your second method work is quite hard and requires really weird constructs like

Unevaluated[With[{c = 2}, Plot[Evaluate@f[x], {x, 0, Pi},
AxesOrigin -> {0, 0}]]] /. DownValues[f]


or

With[{fx = f[x]},
With @@ Hold[{c = 2},
Plot[Evaluate @ fx, {x, 0, Pi}, AxesOrigin -> {0, 0}]]]


Once again: all this is because With must "see" the variables explicitly in the code, to make replacements. In contrast, Block does not need that, it replaces values dynamically at the moment of evaluation, based on their modified global values, as if you made assignments, this is why it works.

Now, the real culprit is your definition of f. You could have avoided all these troubles should you have defined your f with explicit parameter-passing:

ff[x_, c_] := c Cos[x]


Now, this works out of the box:

With[{c = 2},
Plot[Evaluate @ ff[x, c], {x, 0, Pi}, AxesOrigin -> {0, 0}]]


because the parameters are explicitly present in the function call signature, and so are visible to With.

To summarize: what you observed is a consequence of the interplay between lexical and dynamic scoping. Lexical scoping constructs must "see" their variables explicitly in the code at the variable-binding stage (before evaluation), or they won't be effective. Dynamic scoping effectively modifies values of symbols, and is in this sense less demanding (the price you pay is that the code using lots of dynamic scoping is harder to understand, since it mixes state and behavior). The main reason for trouble is the function definition that makes implicit dependencies on global symbols (that are not in the formal parameter list of the function). It is best to avoid such constructs. It is still possible to make things work, but this is considerably more complicated (as was demonstrated above), and, at least for the case at hand, for no good reason.

• Leonid, I edited it a bit so that the example matches the OP. I hope you do not mind. Oct 1 '18 at 17:49
• @J.M.issomewhatokay. Thanks. Surely I don't mind. Oct 1 '18 at 18:37