From: Daniel Jacobowitz <drow@false.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/testsuite] compiler.cc, compiler.c: work with old hp acc
Date: Wed, 30 Jun 2004 13:11:00 -0000 [thread overview]
Message-ID: <20040630131057.GA12658@nevyn.them.org> (raw)
In-Reply-To: <20040630075939.64DDD4B104@berman.michael-chastain.com>
On Wed, Jun 30, 2004 at 03:59:39AM -0400, Michael Chastain wrote:
> After some experimentation and cursing, it looks like their compiler
> does aggressive string concatenation. If the last token in the line is
> a string, then the preprocessor eats the newline in order to merge with
> the first token on the next line, in case that token is a string.
THANK you! I ran into this recently and couldn't figure out what the
problem was.
There's also some option you can pass to aCC to stop it from doing this
- there's an ANSI and a non-ANSI preprocessor and you can explicitly
specify the ANSI one.
> ! /* Note the semicolon at the end of this line. Older versions of
> ! hp c++ have a bug in string preprocessing: if the last token on a
> ! line is a string, then the preprocessor concatenates the next line
> ! onto the current line and eats the newline! That messes up TCL of
> ! course. That happens with HP aC++ A.03.13, but it no longer happens
> ! with HP aC++ A.03.45. */
> !
> ! set compiler_info "unknown" ;
>
> #if defined (__GNUC__)
> #if defined (__GNUC_PATCHLEVEL__)
>
I saw this with A.03.37.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-06-30 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 7:59 Michael Elizabeth Chastain
2004-06-30 13:11 ` Daniel Jacobowitz [this message]
2004-06-30 16:52 Michael Elizabeth Chastain
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=20040630131057.GA12658@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
/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