Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: quick review of References: <0LednZCfW8pHNHzPnZ2dnUVZ_rWdnZ2d@supernews.com> <2014Jan25.161819@mips.complang.tuwien.ac.at> <2014Jan27.164026@mips.complang.tuwien.ac.at> NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; 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:28146 On Mon, 27 Jan 2014 17:00:16 -0500, Bernd Paysan wrote: > The definition of RECURSE therefore is a simple > > ' noop Alias recurse > > [...] > > IMHO this is both the smallest possible and the most > general implementation of RECURSE. Is that even worth pointing out, if the typical RECURSE definition is something like this: : RECURSE LATESTXT @ COMPILE, ; IMMEDIATE Why does it matter that yours is smallest and more general? Rod Pemberton