Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: A non-simultaneity of evaluation

10 views
Skip to first unread message

Paavo Helde

unread,
Nov 18, 2018, 2:10:02 AM11/18/18
to
On 18.11.2018 3:56, Stefan Ram wrote:
> Supersedes: <evaluation-2...@ram.dialup.fu-berlin.de>
>
> An expression is an entity of the source-code model.
> It sits right there in your code and consists of
> characters you typed.
>
> At run-time, there are no expressions; they have been
> lost during the translation. They are not part of the
> run-time model. For example, a program usually cannot
> print its expressions.
>
> Yet, we use the term "to evaluate an expression". E.g.,
>
> |The postfix expression before the dot or arrow is evaluated;
> n4762
>
> . But an evaluation happens at /run time/. How is an
> evaluation which happens at run time supposed to evaluate
> an expression which only exists until compile-time?

Because the object code for evaluating the expression has been prepared
at compile time, doh.

This is the same how we can have chicken soup for dinner even though no
chicken exists in the supermarket.



0 new messages