Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Best teaching methodology for Forths? Date: Thu, 24 Mar 2016 19:24:36 -0700 Organization: A noiseless patient Spider Lines: 11 Message-ID: <87a8lnz44b.fsf@jester.gateway.pace.com> References: <7eacb66d-c762-416a-abbf-2e01a5d596cb@googlegroups.com> <56f3e1fd$0$5911$e4fe514c@news.xs4all.nl> <87mvpnztd5.fsf@jester.gateway.pace.com> <56f48c3c$0$5889$e4fe514c@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx02.eternal-september.org; posting-host="560a36ee31cc4bcf69e115b311f0cc5c"; logging-data="1392"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/PpKov8CToTVizKVeq7jdR" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:HHJsJ2lQ/qkWQLztY6KmOlQ37dc= sha1:4t1TLffmSiAZKXijf7u3Yj09tgg= Xref: csiph.com comp.lang.forth:46201 Albert van der Horst writes: > Basically REGRESS does the interpret action of \ (nice speak) > when your application is finished. > Under development the part between REGRESS and S: is executed, > then the part between S: and the end of the line. > If the stack results are different, an exception is thrown. I see, it's for in-line unit testing. Nice. I'm not familiar with the Hopkins system but sometimes use the gforth assert( word, or just write some testing words and leave them in the program to be run during test runs (or during all runs, if they don't break things).