Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API: token component locations #11

Open
ruv opened this issue Jun 12, 2020 · 0 comments
Open

API: token component locations #11

ruv opened this issue Jun 12, 2020 · 0 comments
Labels
api An API method semantics consideration v4-review Related to the proposal v4 by Matthias Trute

Comments

@ruv
Copy link
Collaborator

ruv commented Jun 12, 2020

Recognizer v4 API calls the entity "parsed data" that is called "token" here. And it doesn't specify where these data pieces may be located.

Token is a tuple of data objects (of the known data types). In general, the data objects can be located not only in the data stack or in the floating-point stack, but also in the memory.

An excerpt from the 3.1 Data types section:

A data type identifies the set of permissible values for a data object. It is not a property of a particular storage location or position on a stack. Moving a data object shall not affect its type.

If a program provides all required actions to work with a token, nothing prevents a program to use other locations beyond the standard stacks. So, some components of the token can be located, for example, in some user-defined stack.

But it is not compatible with some methods to create a token descriptor (see #10). And also, THROW will not discard the components beyond the standard stacks.

So, the question is: should the location of token components be tied to the standard stacks only?

If it should, — we have more approaches to create descriptors and handling tokens.

At the moment I think, it should.
Or can anybody provide a useful use-case for the loosely case?

@ruv ruv added api An API method semantics consideration v4-review Related to the proposal v4 by Matthias Trute labels Jun 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api An API method semantics consideration v4-review Related to the proposal v4 by Matthias Trute
Projects
None yet
Development

No branches or pull requests

1 participant