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.

Sign up for GitHub

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

Jump to bottom

API: is a defer or value suitable? #5

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

API: is a defer or value suitable? #5

ruv opened this issue Jun 9, 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 9, 2020 •
edited

In Recognizer v4 API, the recognizer that the system uses is set by using TO.

This decision is inappropriate. A Forth system might want to perform additional internal actions on changing its recognizer. And it is difficult if this recognizer is switched via IS or TO.

A separated word should be used, as in the case of SET-PRECISION and PRECISION (or SET-CURRENT).

See also a discussion re Minimalistic core API for recognizers.
@ruv ruv added api An API method semantics consideration v4-review Related to the proposal v4 by Matthias Trute labels Jun 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api An API method semantics consideration v4-review Related to the proposal v4 by Matthias Trute
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ruv