Mark W. Humphries

>O.T.: Mark, is your \! word (in your post, quoted below) in common usage (even if it's not adopted into any standard), with that name? I ask because I use...

>So now the discussion is going not about whether it is necessary or not, but about how to better implement it, and what API to choose. Recognizers, and similar proposals...

>What is your (as a Forth system user) way to add support for the floating point numbers, without recompiling the Forth system? Or the hex numbers in form 0x12DF4? What...

>>I prefer hex numbers in the form $ 12df4. >Yes, you just don't have another variant. I don't understand what you mean by that, one can make as many variants...

> [In reply to](#issuecomment-421534398) @rdrop-exit > > > > > I prefer hex numbers in the form `$ 12df4`. > > > > > > > Yes, you just don't...

> > > The only available standard variant is a prefix word. And this word either will be state-smart (bad), or will not work in some states (bad). > >...

> [In reply to](#issuecomment-421762131) @rdrop-exit > > > > > In the meantime, I have no state-smart issues with words like `$` in my Forth: > > > > `:...

> > > > I have no `state` variable in my Forth, the `interpreter` would execute the interpret-only one, the `compiler` would execute the directive one. > > > >...

> > > The following example will not work in your approach, but can work via resolvers: > > > ```forth > > > m: $ ($) tt-lit ; \...

> > Unfortunately I'm not really familiar with current standard compliant ways of doing such things, I can only show you how I would do it in my own Forth...