Sujet : Re: 80386 C compiler
De : mutazilah (at) *nospam* gmail.com (Paul Edwards)
Groupes : comp.lang.cDate : 26. Nov 2024, 22:30:21
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vi5elj$3kdmr$1@dont-email.me>
References : 1 2 3 4
User-Agent : Microsoft Outlook Express 6.00.2800.1106
"Keith Thompson" <Keith.S.Thompson+
u@gmail.com> wrote in message
news:875xo9ln93.fsf@nosuchdomain.example.com...True, but I don't know of anyone who's interested in a C 90 compiler
with this kind of extension. Paul Edwards has made it clear he's only
interested in unextended C90, and anyone else can just use a more modern
compiler.
While not a "compiler" per se, there is one extension to
C90 I might add, which is to have formal names like:
ESC_CHAR '\x1b'
ESC_CHAR_STR "\x1b"
that would allow me to support ASCII and EBCDIC in
my "starter suite".
Microemacs and msged need them.
I probably need names for the control keys too for microemacs.
I'll need to revisit the code to be sure.
But that's what my expectations are for a minimal close-to-C90
standard are - something that will allow a portable implementation
of the basic tools.
It wasn't obvious to me when I started that that was even possible.
Note that this assumes the pre-existence of something like a
BIOS (similar to UEFI), which I call a pseudo-bios. That is
not expected to be portable.
And although I am not expecting the C library to be portable,
to my surprise it is in fact portable other than setjmp/longjmp.
BFN. Paul.