Content deleted Content added
P.maistrenko (talk | contribs) A formal definition of expression is added and referenced, minor edits |
No edit summary |
||
(21 intermediate revisions by 19 users not shown) | |||
Line 1:
{{Short description|Syntactic entity in a programming language with a determinable value}}
In simple settings, the [[return type|resulting value]] is usually one of various [[primitive data type|primitive types]], such as
▲In simple settings, the [[return type|resulting value]] is usually one of various [[primitive data type|primitive types]], such as numerical, [[string (computer science)|string]], [[boolean expression|boolean]], [[complex data type]] or other types.
▲Expression is often contrasted with [[Statement (computer science)|statement]] - a syntactic entity, which has no value (an instruction.)
==Examples==
==Void as a result type==
Line 15:
</ref>
Values of type void cannot be used, so the value of such an expression is always thrown away.
==Side effects and elimination==
In many programming languages, a function, and hence an expression containing a function, may have [[Side effect (computer science)|side effects]]. An expression with side effects does not normally have the property of [[referential transparency]]. In many languages (e.g. [[C++]]), expressions may be ended with a semicolon (<code>;</code>) to turn the expression into an expression [[Statement (programming)|statement]]. This asks the implementation to evaluate the expression for its side-effects only and to disregard the result of the expression (e.g.
===Caveats===
Another class of side effects are changes to the concrete state of the computational system, such as loading data into [[cache memory|cache memories]]. Languages
Furthermore, the elapsed time evaluating an expression (even one with no other apparent side effects), is sometimes essential to the correct operation of a system, as behaviour in time is easily visible from outside the evaluation environment by other parts of the system with which it interacts, and might even be regarded as the ''primary'' effect such as when performing [[Benchmark (computing)|benchmark testing]].
It depends on the particular programming language specification whether an expression with no abstract side effects can [[Program optimization|legally be eliminated]] from the execution path by the processing environment in which the expression is evaluated.
==See also==
* [[Evaluation strategy]]
|