2021-12-27 05:36:12 <neuro_sys_  > swissChili: I saw your comment on CSV parsing. Here's a string tokenizer which may be useful in parsing CSV: https://github.com/neuro-sys/forth-lib/blob/main/string.test.fs#L26-L32
2021-12-27 09:55:23 <crc         > swissChili: http://forth.works/share/5cb2a070c1212bf1e619ce2309e2f3a9 is an implementation of a solution for the csv parsing in retroforth
2021-12-27 11:22:53 <joe9        > @crc, that is beautiful.
2021-12-27 11:23:27 <swissChili  > crc: very nice solution, it reads pretty much how I would do it in C, so intuitive even for a forth layman like me
2021-12-27 11:24:30 <swissChili  > neoru_sys: your string processing code is nice, I'll read through the rest of it today, I'm curious how you go about managing string memory
2021-12-27 11:25:56 <swissChili  > psf: to be honest your code was tricky for me to understand, I think largely due to all the stack manipulation. I'll try to study it in some more detail and figure out how it works. Thanks everyone for the solutions, a great learning resource!
2021-12-27 11:57:56 <neuro_sys__ > swissChili: I don't manage the memory. :) The idea is to mark the DP before starting, and reset it once you're done after your execution context finishes. In your CSV example, it could be after each time you process a line.
2021-12-27 13:19:05 <joe9        > what is the difference between # and #s?
2021-12-27 13:19:10 <joe9        > or #S
2021-12-27 13:23:20 <psf         > It is interesting to see some nice solutions that use string libraries.  Mine is using only what is in ANS Forth, so it is very primitive.
2021-12-27 13:35:36 <neuro_sys__ > joe9: # holds one digit, #s all the rest (until remainder is zero).
2021-12-27 14:58:59 <MrMobius    > speaking of these string problems, does gforth have a malloc equivalent?
2021-12-27 15:07:22 <lispmacs[work]> MrMobius: yes
2021-12-27 15:08:08 <lispmacs[work]> allocate, free, and resize, §5.7.3