Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.stack.nl!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: FORTH LITE TUTORIAL based on MPE VFX Date: Wed, 25 Jun 2014 18:52:13 -0400 Organization: Aioe.org NNTP Server Lines: 34 Message-ID: References: <2d2eba75-5d44-422a-8a3f-751702d8cea6@googlegroups.com> <5be1ebb2-75e3-433a-bb83-542f3763acb1@googlegroups.com> <45f5f8f9-e2c0-42f1-8640-8108c55d397f@googlegroups.com> <1ad192b0-6c5b-462c-8d19-cad563dbf974@googlegroups.com> <557e2d7a-6003-42af-803b-5d21a00315bd@googlegroups.com> <87ceaa31-134f-4503-8a49-e07b4061b301@googlegroups.com> <29b02601-d43c-4f76-8f3a-02bb4855a09a@googlegroups.com> <31f28699-46bc-4f5b-a1f2-565d663dfd3e@googlegroups.com> <2cb5ef69-0e06-4a07-8594-5f65b3d2a714@googlegroups.com> <4e5d1063-b6f1-4cd8-ae53-be0435e372ee@googlegroups.com> <96e20bcc-9f13-4212-9959-6fa4765b40c1@googlegroups.com> <243713a6-b8b2-4053-bb59-6249ebf6b7f5@googlegroups.com> <39b481fe-3c92-44bc-aee7-b344fa9d523d@googlegroups.com> NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: Opera Mail/12.16 (Linux) X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.lang.forth:31852 On Wed, 25 Jun 2014 16:19:56 -0400, wrote: > In my language, I will not have any limit on the size of the strings, Just how do you intend to do that? ... You said you're not going to use nul-terminated strings (below), but integers have a limited range. So, if you use counted strings, your strings will be limited to the maximum representable value for the integer used to store the strings' length. I.e., 65535 for unsigned 16-bit, 4294967295 for unsigned 32-bit, etc. 32-bits is huge, but it's still a fixed size, not unlimited as you've claimed. > and I will not have a zero terminator either That's doable. It's what Forth already does. > (because this prevents sub-strings from being processed in place). That's not true. C has nul-terminated strings and C's strtok() processes sub-strings in place. > Also, I will have UTF-8 strings. Ok. I don't see the point of using UTF-8 for words in the dictionary, but emitting UTF-8 strings for display might be useful. I'd stay with the ASCII portion of UTF-8 for word names. Rod Pemberton