2022-01-30 12:54:47 <crc         > a88: http://www.forth200x.org/escaped-strings.html has a reference implementation of s\"
2022-01-30 12:58:26 <crc         > http://forth.works/share/dd3f2fe8773d1f41bce878f93c983b24 is the s:format word from my forth which is what I use for escape sequences in strings
2022-01-30 13:08:15 <veltas      > crc: Is it really \<space> and not \_ to produce an underscore?
2022-01-30 13:09:25 <veltas      > Oh I get why, because \_ in the string literal is \<space>
2022-01-30 13:09:36 <veltas      > Now it makes sense
2022-01-30 13:09:52 <crc         > My Forth replaces _ with space by default
2022-01-30 13:10:44 <veltas      > It makes more sense if you've actively using it probably
2022-01-30 13:33:31 <a88         > crc, great! thank you so much for the links, very useful
2022-01-30 15:26:10 <remexre     > how do people write stack notations that use quotations?
2022-01-30 15:26:41 <remexre     > My quotation syntax is {}, so I've been writing ( foo { bar -- baz} -- quux ) but idk if there's more common notation other people use
2022-01-30 16:39:16 <crc         > http://forth.works/share/391ef2c69889244bfa48cd05f1ab0dda is my general overview of stack diagrams in retroforth; I have a note near the end on quotations
2022-01-30 16:39:42 <crc         > your notation looks reasonable to me
2022-01-30 17:50:21 <a88         > anyone knows if there is simple tls (ssl) library implemented in forth?
2022-01-30 19:30:51 <kathe       > hello. :)
2022-01-30 21:25:10 <remexre     > a88: you might be able to use stunnel instead of building it into your program?
2022-01-30 21:26:06 <a88         > for some targets that will work, but not for the embedded ones where there is no stunnel; it is good for testing though, thanks for the tip1