Hi Riley,

Didn't have time yesterday to generate the patch, but here it is.
Some of the build changes only make sense if you aren't installing
in the default locations as root.

As a refresher, it adds #elif support, #warning support (for
non-continued lines), asm() at file scope, limited support for
recursive #define (#define stdin stdin), and more complete exclusion
of the floating point related code when floats are disabled.  This
lets you build bcc for elks.  As I mentioned earlier, it looks like
the preprocessor works but it dies when trying to do code generation.

On Tue, Jul 16, 2002 at 07:27:21AM +0100, Riley Williams wrote:
> Unfortunately, that's not actually true. It's very easy to prove that
> bcc uses SIGNED chars if the unsigned keyword isn't specifically given.
> Robert also states that bcc does not correctly handle signed chars, so
> this default rather worries me.

Can you send me a simple test app to illustrate this?  Thanks.

> As it happens, I emailed a patch to Robert back on 6th June 2002 that
> added and correctly implemented the signed keyword in the declspec
> function, thus dealing with most of the problem. There may be a few
> corner cases left where signed will cause problems, but I haven't seen
> any of them yet. I've attached a gzip'd copy of that patch to this email
> for reference...

I'm looking forward to trying out your patch in a few days when things
slow down for me.

Manuel