Path: ...!eternal-september.org!feeder3.eternal-september.org!news.quux.org!news.nk.ca!rocksolid2!i2pn2.org!.POSTED!not-for-mail From: mhx@iae.nl (mhx) Newsgroups: comp.lang.forth Subject: Re: Fetch string from comment Date: Wed, 5 Mar 2025 07:57:24 +0000 Organization: novaBBS Message-ID: References: <687ff0eebad416a2f284ba186461c6d9c54d91cf@i2pn2.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: i2pn2.org; logging-data="2917538"; mail-complaints-to="usenet@i2pn2.org"; posting-account="J+nubxJRM7ncpF4l6KLO+OONWmFAYJHVJegfwQXJ8vc"; User-Agent: Rocksolid Light X-Rslight-Posting-User: 4e0dc1fdad1ead10b39e7eb5db19bf73d73e3ab3 X-Rslight-Site: $2y$10$/TkYCYVPfHAa0P2sisWJfe2V.9GAzYa7Axj.S52uhkviMr72iWdQu X-Spam-Checker-Version: SpamAssassin 4.0.0 Bytes: 1691 Lines: 13 For the past 30 years, I got by with having .~ in addition to ." . The word .~ does the same ." but uses `~` as its delimiter. Most of my uses are served by judicious switching between ." and .~ . I am not a fan of S\" TYPE as it tends to move the parsing and interpretation problems to parts of the code / library that may not be prepared for it, or where it would be quite an overhead to anticipate every present and future possibility. For instance, having a backspace in a string has no obvious meaning in most of the system code, and an application can simply redefine BS to have it do what is necessary. -marcel