Re: Epic failure (was Epic Fail)

From	Bernd Paysan <bernd.paysan@gmx.de>
Newsgroups	comp.lang.forth
Subject	Re: Epic failure (was Epic Fail)
Date	2014-11-30 17:22 +0100
Organization	A noiseless patient Spider
Message-ID	<m5fg85$mrr$1@dont-email.me> (permalink)
References	<f357fc56-c996-4d72-a53d-194a13e276ec@googlegroups.com> <m5d9cn$o3s$1@dont-email.me> <c9e7f2f8-2214-43db-81d6-285593dbbcfd@googlegroups.com> <53212bbf-bb4d-4531-b784-20452bd0eddb@googlegroups.com> <abca6c7a-56b2-4157-94b0-6bed847e02ad@googlegroups.com>

Show all headers | View raw

mhx@iae.nl wrote:

> On Sunday, November 30, 2014 9:04:59 AM UTC+1, m...@iae.nl wrote:
>> On Sunday, November 30, 2014 2:41:52 AM UTC+1, Julian Fondren wrote:
>> > On Saturday, November 29, 2014 2:13:29 PM UTC-6, WJ wrote:
>> > > Now struggle to program the equivalent in Forth.
>> > 
>> [..]
>> > And he doesn't clear CHIST at any point because he knows he's
>> > going to run HIST once :-)
>> [..]
>> Actually that is a bug (iForth is still printing stars), because
>> chist could be/will be filled with trash the first time it is run.
>> 
>> create chist $100 cells allot chist $100 cells erase
>> fixes that, in the way you describe (run once).
> 
> I am assuming that buffer: doesn't initialize its contents to zero,
> its behavior when initially discussed.

Yes, a standard-conforming program is responsible for initializing this 
region - though I would expect that on a reasonable operating system all 
this freshly allocated content is zeroed out anyways.  I would probably make 
a separate word to clear the historgram, as it might be useful to 
incrementally feed strings into the historgram function and look at the 
overall statistics.

-- 
Bernd Paysan
"If you want it done right, you have to do it yourself"
http://bernd-paysan.de/

Thread

Re: Epic failure (was Epic Fail) "WJ" <w_a_x_man@yahoo.com> - 2014-11-29 20:13 +0000
  Re: Epic failure (was Epic Fail) C G Montgomery <cgm@physics.utoledo.edu> - 2014-11-29 17:15 -0500
  Re: Epic failure (was Epic Fail) Pablo Hugo Reda <pabloreda@gmail.com> - 2014-11-29 14:20 -0800
  Re: Epic failure awegel@arcor.de (Alexander Wegel) - 2014-11-29 23:35 +0100
  Re: Epic failure (was Epic Fail) Bernd Paysan <bernd.paysan@gmx.de> - 2014-11-30 00:31 +0100
  Re: Epic failure (was Epic Fail) Julian Fondren <julian.fondren@gmail.com> - 2014-11-29 17:41 -0800
    Re: Epic failure (was Epic Fail) mhx@iae.nl - 2014-11-30 00:04 -0800
      Re: Epic failure (was Epic Fail) mhx@iae.nl - 2014-11-30 00:09 -0800
        Re: Epic failure (was Epic Fail) Bernd Paysan <bernd.paysan@gmx.de> - 2014-11-30 17:22 +0100
  Re: Epic failure (was Epic Fail) "WJ" <w_a_x_man@yahoo.com> - 2014-11-30 02:13 +0000
    Re: Epic failure (was Epic Fail) Julian Fondren <julian.fondren@gmail.com> - 2014-11-29 18:55 -0800
    Re: Epic failure (was Epic Fail) albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-11-30 16:50 +0000
      Re: Epic failure (was Epic Fail) Bernd Paysan <bernd.paysan@gmx.de> - 2014-12-01 01:22 +0100
        Re: Epic failure (was Epic Fail) Melzzzzz <mel@zzzzz.com> - 2014-12-02 06:00 +0100
          Re: Epic failure (was Epic Fail) Melzzzzz <mel@zzzzz.com> - 2014-12-02 06:37 +0100
            Re: Epic failure (was Epic Fail) albert@spenarnc.xs4all.nl (Albert van der Horst) - 2014-12-02 12:28 +0000
            Re: Epic failure Paul Rubin <no.email@nospam.invalid> - 2014-12-02 18:03 -0800
        Re: Epic failure (was Epic Fail) the_gavino_himself <visphatesjava@gmail.com> - 2014-12-05 10:10 -0800
          Re: Epic failure (was Epic Fail) rickman <gnuarm@gmail.com> - 2014-12-05 16:23 -0500
            Re: Epic failure (was Epic Fail) Jason Damisch <jasondamisch@yahoo.com> - 2014-12-05 13:46 -0800
    Re: Epic failure (was Epic Fail) "WJ" <w_a_x_man@yahoo.com> - 2014-12-01 07:54 +0000
      Re: Epic failure awegel@arcor.de (Alexander Wegel) - 2014-12-01 14:02 +0100
        Re: Epic failure hughaguilar96@gmail.com - 2014-12-01 15:04 -0800
          Re: Epic failure awegel@arcor.de (Alexander Wegel) - 2014-12-02 04:54 +0100

csiph-web