Services & Resources / Wolfram Forums / MathGroup Archive

MathGroup Archive 2010

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: The side-effects of mixing TraditionalForm inside expressions.

  • To: mathgroup at
  • Subject: [mg110836] Re: The side-effects of mixing TraditionalForm inside expressions.
  • From: Andrzej Kozlowski <akozlowski at>
  • Date: Thu, 8 Jul 2010 03:14:50 -0400 (EDT)

On 7 Jul 2010, at 20:42, AES wrote:
> Help Browser says:
>  Unevaluated[expr]
>        represents the unevaluated form of expr when it appears as
>        the argument to a function.
> So, what does Unevaluated[expr] do when it is NOT the argument to a
> function? 

It does nothing. You could have checked it yourself:

In[69]:== Unevaluated[1]

Out[69]== Unevaluated[1]

> (The previous statement I'd say clearly implies that there are times
> when Unevaluated[expr] does appear as an arg to function, and therefore
> times when it does not -- and both need to be defined.)
> So, if Unevaluated[expr] is entered all by itself in a cell, is it then
> "the argument to a function"?

> If the cell contains 1 + Unevaluated[expr] as above, does that make the
> Unevaluated[expr] an argument to a function -- or not?
1+Unevaluated[1] is actually Plus[1,Unevaluated[1]] so Unevaluated1] is here an argument to a function.
Also here

In[71]:== Identity[Unevaluated[1]]

Out[71]== 1

Unevaluated[1] is again an argument to an explicit function.

In my opinion the documentation is perfectly clear and correct in this particular case. Of course it is always possible to misunderstand or fail to understand anything, however clear, if one tries hard enough.

Andrzej Kozlowski

  • Prev by Date: Displaying cylinders
  • Next by Date: Re: Problem with a diagram
  • Previous by thread: Re: The side-effects of mixing TraditionalForm inside expressions.
  • Next by thread: Re: FindRoot with parameterized interpolated function