Proposal: Wording: declare undefined interpretation semantics for locals

Informal

This proposal has been moved into this section. Its former address was: /standard/locals/bColon

This page is dedicated to discussing this specific proposal

ContributeContributions

ruvavatar of ruv Wording: declare undefined interpretation semantics for localsProposal2020-03-08 15:18:59

Problem

We have the "name Execution:" section for the locals, but don't have a "name Interpretation:" section. Hence, name has default interpretation semantics according to 3.4.3.2, that conflicts with an explicitly declared ambiguous condition in the "name Execution:" section.

Proposal

Add the following section:

name Interpretation:

Interpretation semantics for name are undefined.

Remove from the "name Execution:" section the following sentence:

An ambiguous condition exists when name is executed while in interpretation state.

ruvavatar of ruv

The same proposal is applied to (LOCAL), taking into account that there another wording is used: "local Execution:". Perhaps we should also harmonize these specifications with each other.

ruvavatar of ruv

In the general case, "name is executed while in interpretation state" can be achieved via : foo {: name :} name ; 1 foo — and nothing wrong with that. So the corresponding sentence is even incorrect by its own.

Reply New Version