Re: Word name storage quirk in VAX fig-Forth

Liste des GroupesRevenir à cl forth 
Sujet : Re: Word name storage quirk in VAX fig-Forth
De : dxforth (at) *nospam* gmail.com (dxf)
Groupes : comp.lang.forth
Date : 17. Apr 2025, 02:34:05
Autres entêtes
Organisation : i2pn2 (i2pn.org)
Message-ID : <d3fe9fefe19bb5b981145c44acba345e16dd6032@i2pn2.org>
References : 1 2 3 4
User-Agent : Mozilla Thunderbird
On 17/04/2025 9:31 am, David Meyer wrote:
It occurred to me that another factor in this is that the VAX-11 OS used
7-bit ASCII as its character set, so perhaps terminals and printers of
that time would just print the character indicated by the lower 7 bits
of each byte they were sent, ignoring the high bit. So I am seeing
munged characters because I'm using equipment that looks at all 8 bits
for character codes?

This got me interested.  In FigForth for CP/M-80 bit 7 is *not* cleared.
Thus the full 8 bits is sent to the BIOS console output with the expectation
bit 7 will is cleared in the BIOS.  DRI's spec for BIOS CONOUT appears to
require this.  OTOH I know BIOS's that didn't do that as it would restrict
console capability.

Ideally FigForth should allow 8-bit EMITs and ID. rewritten to use a
127 AND EMIT loop instead of TYPE .


Date Sujet#  Auteur
16 Apr 25 * Word name storage quirk in VAX fig-Forth5David Meyer
16 Apr 25 `* Re: Word name storage quirk in VAX fig-Forth4Anton Ertl
17 Apr 25  `* Re: Word name storage quirk in VAX fig-Forth3David Meyer
17 Apr 25   `* Re: Word name storage quirk in VAX fig-Forth2dxf
17 Apr 25    `- Re: Word name storage quirk in VAX fig-Forth1David Meyer

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal