Content deleted Content added
Santropedro (talk | contribs) mNo edit summary |
No edit summary |
||
(27 intermediate revisions by 23 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
Expressions are often contrasted with [[Statement (computer science)|statement]]s—[[syntactic]] entities that have no value (an instruction).
▲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|logical]], [[complex data type]] or many others.
==Examples==
For example, <code>2+3</code> is an arithmetic and programming expression which evaluates to <code>5</code>. A variable is an expression because it denotes a value in memory, so <code>y+6</code> is an expression. An example of a relational expression is <code>4≠4</code>, which evaluates to <code>false</code>.<ref>[https://developer.mozilla.org/en/Core_JavaScript_1.5_Guide/Expressions Javascript expressions, Mozilla] Accessed July 6, 2009</ref><ref>[https://www.cs.drexel.edu/~rweaver/COURSES/ISTC-2/TOPICS/expr.html Programming in C] Accessed July 6, 2009</ref>▼
▲
==Void as a result type==
Line 14 ⟶ 18:
==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 [[
===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]]
|