Newsgroups: comp.lang.forth
Path: utzoo!utgpu!cunews!csi.uottawa.ca!news
From: cbbrowne@csi.uottawa.ca (Christopher Browne (055908))
Subject: Re: Control characters
Message-ID: <1991May30.002016.22178@csi.uottawa.ca>
Keywords: n
Sender: news@csi.uottawa.ca
Nntp-Posting-Host: prgc
Organization: CSI Dept., University of Ottawa
References: <9105291726.AA13700@ucbvax.Berkeley.EDU>
Date: Thu, 30 May 91 00:20:16 GMT

In article <9105291726.AA13700@ucbvax.Berkeley.EDU> Mitch.Bradley%ENG.SUN.COM@SCFVM.GSFC.NASA.GOV writes:
>>       If you want your program to be really portable, you better figure
>>       out how to write the source code with printable characters.
>
>Obviously, I meant "without", not "with".
>
>Mitch.Bradley@Eng.Sun.COM

No, I think you DID mean that you want to write source code WITH printable
characters - It's kind of hard to read source code that doesn't have any
printable characters :-).  (Wrote this one too late at nite?)

Anyway, the KEY/EKEY compromise seems MOSTLY ok.  I worry about the
dependencies tho - most parts of a "Standard" system will use KEY for
input, which means that it may be difficult to use standard/core words
to do input of odd characters.  I thinking that it may be a neat
idea to use vectored execution, and perhaps swap between use of KEY and
EKEY within applications.  Or maybe that makes life even more complicated.
-- 
Christopher Browne
cbbrowne@csi.uottawa.ca
University of Ottawa
Master of System Science Program