From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: document macro support
Date: Tue, 14 May 2002 13:17:00 -0000 [thread overview]
Message-ID: <20020514201828.GA1851@daikokuya.demon.co.uk> (raw)
In-Reply-To: <npelgezecb.fsf@zwingli.cygnus.com>
Jim Blandy wrote:-
> > Is there any progress on using libcpp, or is that on the back burner?
>
> Well, first libcpp needs to be disentangled from GCC. Right now it
> shares its configury and build files with GCC, and lives in the `gcc'
> directory. All of this makes it rather difficult to share libcpp
> between the gcc and sourceware repositories. Zack W. has volunteered
> to disintegrate libcpp, but apparently the 3.2 release process hinders
> this.
>
> I'll be posting GDB tests for the macro support in the next few days.
> They will include tests for the bugs you pointed out in my macro
> expander, so the issues with token marking won't be forgotten.
OK, great. IIRC Zack indicated he might be able to move CPP before
3.2, but let's see. I have no idea if he has time.
Neil.
next prev parent reply other threads:[~2002-05-14 20:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 16:35 Jim Blandy
2002-05-13 23:49 ` Neil Booth
2002-05-14 13:03 ` Jim Blandy
2002-05-14 13:17 ` Neil Booth [this message]
2002-05-14 14:17 ` Eli Zaretskii
2002-05-14 14:57 ` Jim Blandy
2002-05-14 14:15 ` Jim Blandy
2002-05-14 14:26 ` Andrew Cagney
2002-05-14 14:51 ` Eli Zaretskii
2002-05-15 15:51 ` Jim Blandy
2002-05-15 22:44 ` Eli Zaretskii
2002-05-16 13:42 ` Jim Blandy
2002-05-17 0:31 ` Eli Zaretskii
2002-05-17 11:00 ` Jim Blandy
2002-05-14 14:31 ` Eli Zaretskii
2002-05-15 15:51 ` Jim Blandy
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=20020514201828.GA1851@daikokuya.demon.co.uk \
--to=neil@daikokuya.demon.co.uk \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.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