Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Alex Newsgroups: comp.lang.forth Subject: Re: Really? Date: Fri, 10 Feb 2017 08:33:15 +0000 Organization: A noiseless patient Spider Lines: 47 Message-ID: References: <1239a88b-a574-401b-9454-50ac7e000049@googlegroups.com> <5899a408.386236853@news.eternal-september.org> <87shnqw989.fsf@nightsong.com> <589a303c.422128955@news.eternal-september.org> <01fb25bd-7975-4ca5-b9e6-1024cb772c7a@googlegroups.com> <1207313c-ffcd-4640-a619-f1424dcf75cc@googlegroups.com> <2bca6ead-46b4-41b3-b40f-fbb550196acb@googlegroups.com> <1ffb1cf7-aff3-4777-b924-2e4445d255bd@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 10 Feb 2017 08:31:28 -0000 (UTC) Injection-Info: mx02.eternal-september.org; posting-host="8c003550790cf8e4018a9adce90f2e90"; logging-data="20327"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1++H8gKs1IXR7TOZHgSOnXRFfKa6a78yq8=" User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 In-Reply-To: <1ffb1cf7-aff3-4777-b924-2e4445d255bd@googlegroups.com> Cancel-Lock: sha1:bsUYYJMPtvNy7CVYQZJ5tKFCgfM= Xref: csiph.com comp.lang.forth:54766 On 2/9/2017 22:36, hughaguilar96@gmail.com wrote: > On Thursday, February 9, 2017 at 1:56:25 AM UTC-7, Alex wrote: >> On 2/9/2017 06:39, hughaguilar96@gmail.com wrote: >>> ANS-Forth actually has several problems that come from using the >>> same memory for different things. This has been discussed >>> before: >>> https://groups.google.com/forum/#!topic/comp.lang.forth/uGAKvs8baQk%5B26-50%5D >>> >>> >>> On Friday, December 9, 2016 at 8:11:08 AM UTC-7, hughag...@gmail.com >>> wrote: >>>> On Thursday, December 8, 2016 at 11:23:05 PM UTC-7, >>>> hughag...@gmail.com wrote: >>>>> ANS-Forth is confusing! I was testing my words under VFX just >>>>> now and came to this: >>>>> >>>>> 12345.6789e engineering ok-2 type 12.345679e32 ok >>>>> >>>>> WTF??? Does my code have a bug??? Then I tried this: >>>>> >>>>> 12345.6789e engineering type 12.345679e3 ok >>>>> >>>>> This works. I realized then that the problem was not in my >>>>> code, it was in ANS-Forth --- the outer-interpreter uses the >>>>> same memory location for multiple purposes --- my >>>>> is using the buffer that <# #> uses, and this >>>>> buffer gets clobbered by the outer-interpreter before the >>>>> TYPE gets done on the next line. >> >> Yes, your code has a bug, since the behaviour you're describing is >> covered by the standard. ... It's a bug, since your >> word doesn't work. > > There is no bug in my --- the ANS-Forth cult's strategy > seems to be repeatedly to denounce my novice package as having bugs > without offering any evidence --- this is so ANS-Forth programmers > won't use my STRING-STACK.4TH etc. because they believe that the > whole package is full of bugs, and they continue using PAD etc. > instead because that is "standard." > Am I to assume that all your code is bug-free, even when its author says it doesn't work? -- Alex