Deutsch English Français Italiano |
<v8ssth$1hnbh$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Ruvim <ruvim.pinka@gmail.com> Newsgroups: comp.lang.forth Subject: Re: Alternative for long parsing words Date: Tue, 6 Aug 2024 14:12:00 +0400 Organization: A noiseless patient Spider Lines: 46 Message-ID: <v8ssth$1hnbh$1@dont-email.me> References: <a1aab44ee3b1b56c2f54f2606e98d040@www.novabbs.com> <23a44aa0445a30c0fc782819f48463f9@www.novabbs.com> <nnd$685d2a62$7d072f38@c2a291bc8c0eb1cd> <v8nrb0$3vbpv$3@dont-email.me> <nnd$4ced6d91$68fcde58@19347b2874c81786> <v8qnhv$n39d$1@dont-email.me> <2024Aug5.163310@mips.complang.tuwien.ac.at> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 06 Aug 2024 12:12:02 +0200 (CEST) Injection-Info: dont-email.me; posting-host="0f501129dc6d814bf30f81dba05a8b8e"; logging-data="1629553"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+cvxGkIgPwnAOqlIS4m/Ns" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:243TMZ2TNNI4dCw+m818ZEcoCek= Content-Language: en-US In-Reply-To: <2024Aug5.163310@mips.complang.tuwien.ac.at> Bytes: 2467 On 2024-08-05 18:33, Anton Ertl wrote: > Ruvim <ruvim.pinka@gmail.com> writes: >> I meant the word `[IF]` by itself, without connection with `WANT`. > > Not necessarily a parsing word. Could also be treated as something > like another state (i.e., the text interpreter does the parsing, but > does something different with the words than interpretation state or > compile state. > In every case, the interaction with other features is > problematic; e.g., consider: > > 0 [IF] > ... > \ .... > \ [ELSE] > \ .... > cr .( you should see this according to the standard) > [THEN] > > (and the systems I tested actually comply with the standard requirements) > > This behaviour might surprise users, especially in connection with > nested [IF]s. However, there have been few complaints, so it > obviously is only a minor issue. This problem is not endemic to Forth. It takes place in many other programming languages too. For example, in "C++": /* // /* comment */ puts("you should see this"); // the above command takes effect despite the line comment /* other comment */ A rule of thumb: the one who gains control first wins. -- Ruvim