Skip to content

Most recent definition #19

@ruv

Description

@ruv

The notion of "most recent definition" has the following problems:

  1. It is used in the standard in two variants: "the most recent definition" and "the most recently compiled definition" (see 16.3.3). Perhaps they both mean the same thing.
  2. There is no formal definition for this notion. Without a formal definition it is confusing (see also a discussion).

Probably, it makes sense to distinguish between the notions of "current definition" and "most recent definition" so that one Forth definition cannot be both of them in the same time (note that the former is defined in 2.1 Definitions of terms, but not the later).

Then, in some cases wording should be updated accordingly. For example, in 6.1.1250 DOES>.

Note that the following program should be ambiguous even if change-the-latest unambiguously changes the execution semantics of foo:

: change-the-latest ( -- ) does> @ ;
create foo 123 ,
:noname  foo [ change-the-latest ] foo ; execute

Metadata

Metadata

Assignees

No one assigned

    Labels

    clarificationSomething needs to be clearer or more accurateinconsistencySomething is inconsistent with something else

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions