From owner-freebsd-current  Mon Dec 21 01:59:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA00861
          for freebsd-current-outgoing; Mon, 21 Dec 1998 01:59:13 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA00853
          for <current@FreeBSD.ORG>; Mon, 21 Dec 1998 01:59:12 -0800 (PST)
          (envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1])
	by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id BAA81124;
	Mon, 21 Dec 1998 01:59:00 -0800 (PST)
To: "Daniel C. Sobral" <dcs@newsguy.com>
cc: mike@smith.net.au, current@FreeBSD.ORG
Subject: Re: BootFORTH - demo floppy 
In-reply-to: Your message of "Mon, 21 Dec 1998 01:25:21 PST."
             <199812210925.BAA09284@newsguy.com> 
Date: Mon, 21 Dec 1998 01:59:00 -0800
Message-ID: <81120.914234340@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> see I case here. It's not "tradition". It is the ANS Forth standard. If you
> want an evaluate which works with null-terminated strings, go ahead and defin
e
> evaluate0 or something. But needlessly making it incompatible with a publishe
d
> standard is, well, it is stupid.

Which is what I hopefully communicated in my other message.  Mike is
not a forth programmer, so he simply does not always know the
distinction between something which is a standard core word and
something which is an optional (and perhaps egregious) forth-ism.

- Jordan

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message