In html-parse, the following case near line 449 is missing the \
in '\"' -- it comes out as '"' and, as such, causes some compilers to
barf.
case AC_S_QUOTE1:
assert (ch == '\'' || ch == '\"');
Bill Bumgarner <[EMAIL PROTECTED]> writes:
> In html-parse, the following case near line 449 is missing the \ in
> '\"' -- it comes out as '"' and, as such, causes some compilers to
> barf.
Could you name an actual compiler that barfs on it? The constant '"'
is perfectly legal in C, and I'm pos
Certainly:
[localhost:/tmp] bbum% cc -v
Reading specs from /usr/libexec/gcc/darwin/ppc/2.95.2/specs
Apple Computer, Inc. version gcc-926, based on gcc version 2.95.2
19991024 (release)
On Monday, June 25, 2001, at 05:54 PM, Hrvoje Niksic wrote:
> Bill Bumgarner <[EMAIL PROTECTED]> writes:
>
Bill Bumgarner <[EMAIL PROTECTED]> writes:
> Certainly:
>
> [localhost:/tmp] bbum% cc -v
> Reading specs from /usr/libexec/gcc/darwin/ppc/2.95.2/specs
> Apple Computer, Inc. version gcc-926, based on gcc version 2.95.2
> 19991024 (release)
Interestingly, Gcc 2.95.2 works perfectly for me. It's
Here is the assert.h from OSX-- I'm assuming this is the source of the
assert definition. And, of course, the stringification would cause the
problem
/* Allow this file to be included multiple times
with different settings of NDEBUG. */
#undef assert
#undef __assert
#ifdef NDEBUG
#de
On Tue, 26 Jun 2001 10:45:42 -0400, Bill Bumgarner <[EMAIL PROTECTED]>
wrote:
>On Tuesday, June 26, 2001, at 04:27 AM, Hrvoje Niksic wrote:
>
>> Bill Bumgarner <[EMAIL PROTECTED]> writes:
>>
>>> Certainly:
>>>
>>> [localhost:/tmp] bbum% cc -v
>>> Reading specs from /usr/libexec/gcc/darwin/ppc/2.9
Ian Abbott <[EMAIL PROTECTED]> writes:
> ch == '\'' || ch == '"'==> "ch == '\\'' || ch == '\"'"
> ch == '\'' || ch == '\"' ==> "ch == '\\'' || ch == '\\\"'"
>
> Also, both versions of the character constant '"' and '\"' are
> valid, so if the compiler barfs on any of the above it must
On 26 Jun 2001 21:02:21 +0200, Hrvoje Niksic <[EMAIL PROTECTED]>
wrote:
>Ian Abbott <[EMAIL PROTECTED]> writes:
>
>> ch == '\'' || ch == '"'==> "ch == '\\'' || ch == '\"'"
>> ch == '\'' || ch == '\"' ==> "ch == '\\'' || ch == '\\\"'"
>>
>> Also, both versions of the character constant
Ian> Also, both versions of the character constant '"' and '\"' are valid,
Ian> so if the compiler barfs on any of the above it must be faulty. I
Ian> suggest a bug report to the maintainers of this compiler is in order.
The problems not with the compiler. Indeed, the Mac OS X compiler is gcc. Th
