From: Aleksandar Ristovski <aristovski@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: cp-name-parser.y
Date: Fri, 29 Feb 2008 19:32:00 -0000 [thread overview]
Message-ID: <47C85859.2030403@qnx.com> (raw)
In-Reply-To: <20080229185513.GA2793@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Fri, Feb 29, 2008 at 01:22:00PM -0500, Aleksandar Ristovski wrote:
>> Hello,
>>
>> If you could, let me know how mature is that code there and can it be used.
>
> What would you like to use it for?
>
I am looking at that since right now something like this:
-var-create - * "(anonymous namespace)::foobar"
will not work since c_parse doesn't know anything about '(anonymous namespace)'.
I guess it wouldn't be too hard to hack around this particular case, but a
proper solution would be preferable.
I see that language_defn for c++ uses c_preprocess_and_parse but there should
probably be something like cp_preprocess_and_parse, sharing the macro handling
part but calling cpname_parse instead of c_parse. Or maybe calling cpname_parse
if c_parse fails.
The issue is evident when using IDE (CDT). IDE will call
ptype foobar
which prints type (correctly) something like this: '(anonymous
namespace)::FooBar' and then IDE uses this string as argument to -var-create,
but unfortunately, this doesn't work.
next prev parent reply other threads:[~2008-02-29 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 18:39 cp-name-parser.y Aleksandar Ristovski
2008-02-29 19:09 ` cp-name-parser.y Daniel Jacobowitz
2008-02-29 19:32 ` Aleksandar Ristovski [this message]
2008-02-29 19:49 ` cp-name-parser.y Daniel Jacobowitz
2008-02-29 20:15 ` cp-name-parser.y Aleksandar Ristovski
2008-02-29 21:49 ` cp-name-parser.y Daniel Jacobowitz
2008-03-03 17:02 ` cp-name-parser.y Aleksandar Ristovski
2008-03-03 17:22 ` Daniel Jacobowitz
2008-03-03 18:33 ` cp-name-parser.y Aleksandar Ristovski
2008-03-03 20:05 ` cp-name-parser.y Daniel Jacobowitz
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=47C85859.2030403@qnx.com \
--to=aristovski@qnx.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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