Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.forth    |    Forth programmers eat a lot of Bratwurst    |    117,927 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 117,212 of 117,927    |
|    dxf to David Meyer    |
|    Re: Word name storage quirk in VAX fig-F    |
|    17 Apr 25 11:34:05    |
      From: dxforth@gmail.com              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 .              --- SoupGate-DOS v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca