From owner-freebsd-current Mon Dec 21 00:41:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA23222 for freebsd-current-outgoing; Mon, 21 Dec 1998 00:41:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from newsguy.com (smtp.newsguy.com [207.211.168.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA23215 for ; Mon, 21 Dec 1998 00:41:44 -0800 (PST) (envelope-from dcsobral@newsguy.com) Received: (from dcsobral@localhost) by newsguy.com (8.9.1a/8.9.1) id AAA07194; Mon, 21 Dec 1998 00:41:02 -0800 (PST) Date: Mon, 21 Dec 1998 00:41:02 -0800 (PST) Message-Id: <199812210841.AAA07194@newsguy.com> X-Mailer: Direct Read Email by Newsguy News Service To: mike@smith.net.au From: "Daniel C. Sobral" Subject: Re: BootFORTH - demo floppy Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sun, 20 Dec 1998 16:23:48 -0800, you wrote >> >> 2) Could someone please add the 30-years old traditional >> "ok" prompt in interpreting mode? > >The prompt is fully configurable; set it yourself if that's what you >want. Ok. I did not know the prompt was configurable. >> 3) I noticed "evaluate" is working with null-ended string, ignoring >> completely the count on the stack. Not good. > >Is this an implementation feature? Does the count on the stack ever >not match the length of the string? I'm not sure what do you mean with the first question. As for the second question... sure. Forth string operators are all count based. The null will not appear on the end of the string unless you put it there yourself. Now, adding nulls to the end of the string is very easy with count based strings (as long as you are not working with a substring), and I have nothing against doing it. But having "evaluate" operate on null-terminated strings is the same as having strncmp operate on null-terminated strings: it's against standard and intent. -- Daniel C. Sobral dcs@newsguy.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message