Randy W. Sims wrote:
Steve Hay wrote:
>Randy W. Sims wrote:
, I finally got around to looking. The problem is where I
suspected: It's the quoting of the macros VERSIN & XS_VERSIN.
the command line you can type:

bcc32 -DVERSIN=\"1.01\" test.c

But we use response files for all compilers on Windows (GCC, BCC, &
MSVC), and the response files seem to require a different quoting
syntax that I haven't figured out yet.
[]

I've posted on one of the borland newsgroups see if anyone can help
there. If I can't find a quoting solution, I guess I can move macros
of the key=value form back onto the commandline, for bcc.
>>
>I get the same problems here. I found that you can use "configuration
>files" (like "response files", but they only contain compiler options,
>not filenames too) and that these work, but you can only seem to have
>one of them.
[]

>That just makes it all the more irritating that the same quoting
>doesn't work in response files.

Extremely irritating. I've received several responses to my query in the
Borland newsgroups, but no solution. I'm left with the alternative of
pulling them out of the response file for that compiler.

The attached patch is what I've checked into our repository. Tests now
pass.

Randy.

I've just applied this patch to bleadperl (#28597) to reduce the smoke
from Borland builds.