From: Robert de Bath <robert$@mayday.cix.co.uk>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: More dev86 changes (0.16.7)
Date: Fri, 2 Aug 2002 21:18:22 +0100 (BST) [thread overview]
Message-ID: <bdd32ab4f9e0460f@mayday.cix.co.uk> (raw)
Rather than joining in this discussion I've been adding about a thousand
lines of new code (and another of old) to dev86. The result is a nice
shiny new CPP. My problem now is that I've run out of bugs in it and need
your help to find some more. ;-)
Advantages:
The new CPP is fully ansi capable including '#' '##' and '??='.
It's also a proper K&R preprocessor if you want.
My next step will be to rip the old CPP out of bcc completely, hopefully
making it lots smaller and so small enough to easily fit in an ELKS a.out.
This version uses the new cpp by default, -e will make it fall back to
the old one (for the moment).
With this version __STDC__ is now defined as "1" not "0" as it was before
because cpp is now fully ansi compliant (crosses fingers).
--
Rob. (Robert de Bath <robert$ @ debath.co.uk>)
<http://www.cix.co.uk/~mayday>
next reply other threads:[~2002-08-02 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 20:18 Robert de Bath [this message]
2002-08-02 20:24 ` More dev86 changes (0.16.7) Manuel Novoa III
2002-08-03 10:17 ` More dev86 changes (0.16.7) [About the optimiser] Harry Kalogirou
2002-08-03 11:01 ` Robert de Bath
2002-08-03 11:31 ` Robert de Bath
2002-08-03 12:24 ` Harry Kalogirou
2002-08-10 19:36 ` More dev86 changes (0.16.7) Manuel Novoa III
2002-08-10 20:28 ` Robert de Bath
2002-08-11 1:06 ` Manuel Novoa III
2002-08-11 16:44 ` dev86-0.16.8 cpp bugs Manuel Novoa III
2002-08-11 19:19 ` Robert de Bath
2002-08-11 20:01 ` Manuel Novoa III
-- strict thread matches above, loose matches on Subject: below --
2002-08-03 5:21 More dev86 changes (0.16.7) Ken Martwick
2002-08-03 6:12 ` Robert de Bath
2002-08-03 17:07 Ken Martwick
2002-08-03 17:14 ` Paul Nasrat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bdd32ab4f9e0460f@mayday.cix.co.uk \
--to=robert$@mayday.cix.co.uk \
--cc=linux-8086@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox