Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!rt.uk.eu.org!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: PICK changed from 1-based to 0-based? Date: Sun, 29 Dec 2013 22:32:42 -0500 Organization: Aioe.org NNTP Server Lines: 20 Message-ID: References: <7xvby8f6md.fsf@ruckus.brouhaha.com> <52bff96e$0$2861$e4fe514c@news2.news.xs4all.nl> 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:27517 On Sun, 29 Dec 2013 08:45:41 -0500, Andrew Haley wrote: > Hans Bezemer wrote: >> Forth-83 is where Forth IMHO went wrong. [ ... ] >> Turning "true" into an "all bits set" value [...] > > [...] but what possible damage did "all bits set" do? > It doesn't do any damage. In fact, it helps. Using "all bits set" for a TRUE flag allows a high-level language to have both logical and binary operations, while only needing the processor to support simple binary operations, such as AND OR XOR. This, of course, is in the context of zero being logical false and non-zero being logical true. Rod Pemberton