Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!sun-barr!ames!haven!uvaarpa!hudson!vivaldi.acc.Virginia.EDU!pmy
From: pmy@vivaldi.acc.Virginia.EDU (Pete Yadlowsky)
Newsgroups: comp.lang.forth
Subject: Re: 32-Bit FORTH
Keywords: cforth, cforth83, ansi, forth-83
Message-ID: <1674@hudson.acc.virginia.edu>
Date: 26 Jun 89 15:54:50 GMT
References: <865@pcsbst.UUCP> <12396@well.UUCP>
Sender: news@hudson.acc.virginia.edu
Reply-To: pmy@vivaldi.acc.Virginia.EDU.acc.Virginia.EDU (Pete Yadlowsky)
Organization: University of Virginia, Charlottesville
Lines: 21

In article <12396@well.UUCP> jax@well.UUCP (Jack J. Woehr) writes:

[ in response to someone asking about 32-bit forths ]

>	again, depends on your architecture. Usually 4 chars per 32 bits.
>of course, 8-bits-per-char in general is becoming passee, since *REAL*
>computer systems had better be able to handle japanese 16-bit chars.

Interesting. I wasn't aware that recognition of the Japanese character
set (kanji, I assume) was becoming an important issue in computerdom (yet),
outside Japan, that is. Can you say more about this?

>If you have an Amiga, try JForth, a JSR-Threaded 32-bit Forth.

Absolutely. You can't beat JForth with the proverbial stick.


Peter M. Yadlowsky		| "Pay no attention to that man
Academic Computing Center	|	behind the curtain!"
University of Virginia		|
pmy@Virginia.EDU		|