Re: Split a string and characters
paul.ortais-WGBUbHxT2D9Wk0Htik3J/[email protected] Fri, 09 Dec 2022 01:16:48 +0100
| Newsgroups | gmane.comp.lang.forth.gforth |
|---|---|
| Message-ID | <[email protected]> |
Thank you very much Bernd, Food for thought Paul Le 2022-12-08 23:42, Bernd Paysan a écrit : > Am Montag, 5. Dezember 2022, 10:37:17 CET schrieb > paul.ortais-WGBUbHxT2D9Wk0Htik3J/[email protected]: > >> Dear all, >> >> Sadly enough for Hendursaga's request, FORTH already does this with >> the >> interpreter, and IMO should have done it, for decades, with an open, >> clear generic state machine that reacts to incoming characters in case >> it is treating an incoming file, so that any user has the ability to >> patch and arrange it for its own purpose, in the FOTH spririt. >> >> For obscure reasons this was never done, and kept bundled in the >> sealed >> set of words the interpreter/compiler uses, making the whole stuff the >> grey box in a system claiming to be transparent. It makes it >> unnecessarily complex to port FORTH to any new target. About the same >> burden as missing the half-dozen words in a PC to plot a pixel in some >> graphic pixel, the greatest lack in Forth. >> >> To remain compliant with say, ANS, traditional inner loop words would >> then be coded as pointers to the generic file parsing, FSM mode... > > That is what the recognizer proposal is for. So yes, it was done, and > it is > available in the development version of Gforth. > > https://forth-standard.org/proposals/minimalistic-core-api-for-recognizers#reply-892 > > -- > Bernd Paysan > "If you want it done right, you have to do it yourself" > net2o id: kQusJzA;7*?t=uy@X}1GWr!+0qqp_Cn176t4(dQ* > https://net2o.de/