Path: csiph.com!usenet.pasdenom.info!news.chainon-marquant.org!nntpfeed.proxad.net!proxad.net!feeder1-2.proxad.net!193.252.117.184.MISMATCH!feeder.news.orange.fr!not-for-mail Message-ID: <4F5D0C59.1050508@nospam.com> Disposition-Notification-To: Jean-Bernard Faucon Date: Sun, 11 Mar 2012 21:34:33 +0100 From: Jean-Bernard Faucon User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.27) Gecko/20120216 Thunderbird/3.1.19 MIME-Version: 1.0 Newsgroups: comp.lang.forth To: Josh Grams Subject: Re: Question on CHAR and [CHAR] References: <4f5cdcba$0$19178$882e7ee2@usenet-news.net> In-Reply-To: <4f5cdcba$0$19178$882e7ee2@usenet-news.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Lines: 26 Organization: les newsgroups par Orange NNTP-Posting-Date: 11 Mar 2012 21:34:34 CET NNTP-Posting-Host: 195.146.241.52 X-Trace: 1331498074 reader.news.orange.fr 21480 195.146.241.52:2701 X-Complaints-To: abuse@orange.fr Xref: csiph.com comp.lang.forth:10010 Le 11/03/2012 18:11, Josh Grams a écrit : > Rod Pemberton wrote: >> However, the three ANS Forths I tried *also* support the following usage: >> >> : T CHAR 'A' . ; >> T 65 > > You should get in the habit of checking whether your definitions leave > stack junk -- CHAR is redundant there: > > T B . 65 66 > > The character literal syntax isn't in any standard; it's just a > common-sense thing which some Forth systems support. IIRC gforth > supported 'A but not 'A' for a while... > > --Josh : T CHAR . ; t a 97 ok t b 98 ok t n 110 ok t t 116 ok t u 117 ok