Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: "Rod Pemberton" Newsgroups: comp.lang.forth Subject: Re: Recommendation of a Forth to embed in C Date: Mon, 21 Apr 2014 20:39:19 -0400 Organization: Aioe.org NNTP Server Lines: 20 Message-ID: References: <85ca46a5-03d8-41ad-ab7e-8e5c3b781e48@googlegroups.com> <88c99e6b-9fb4-45fb-a724-eb03a673ceec@googlegroups.com> NNTP-Posting-Host: CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; 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:29757 On Sun, 20 Apr 2014 17:02:08 -0400, wrote: > On Saturday, 19 April 2014 09:55:05 UTC+1, Rod Pemberton wrote: >> A byte by definition is exactly 8-bits. Bytecode uses only one byte to >> represent all instructions. With a 1:1 mapping of instructions to >> integer >> values, how can you have more than 256 words using only 8-bits per > >> instruction? > > No, a byte is not by definition 8 bits (though I agree people often talk > as if it were, which can be confusing) > > Now if we were talking about 'octet-code', that might be different... > Sorry, I overlooked your post. See my reply below rickman for the history of a byte. RP