public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/5] Add d_main_name to dlang.c
Date: Fri, 10 Jan 2014 19:36:00 -0000	[thread overview]
Message-ID: <CABOHX+cyN-3SxWKQYG_kvuSEaNU_SVXJOZuA0BXjSVKJ0feRBw@mail.gmail.com> (raw)
In-Reply-To: <87y52n64xv.fsf@fleche.redhat.com>

On 10 January 2014 18:57, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Iain" == Iain Buclaw <ibuclaw@gdcproject.org> writes:
>
> Iain> So would you prefer that _Dmain were used here?
>
> It's fine as-is.
>
> In that note I was actually asking about the generic problem of
> specifying demangled D names to the linespec parser.  But since spaces
> don't generally appear there, there's no big issue.  This is kind of
> tangential to the patch at hand, just seeing that space made me wonder.
>

Currently all demangled symbols have to be 'quoted' because they are
in the format foo.bar.baz.  Incidentally, I was just looking into
writing a separate expression parser for D (d-exp.y).  I don't suppose
you'd know off the bat whether - if written properly - it would be
able to handle D demangled symbols without the need to quote them?

Thanks
Iain.

  reply	other threads:[~2014-01-10 19:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 13:09 Iain Buclaw
2014-01-09 18:18 ` Tom Tromey
2014-01-09 18:29   ` Iain Buclaw
2014-01-10 17:26     ` Iain Buclaw
2014-01-10 18:57       ` Tom Tromey
2014-01-10 19:36         ` Iain Buclaw [this message]
2014-01-10 19:47           ` Tom Tromey
2014-01-18 17:09   ` Iain Buclaw
2014-01-18 18:22     ` Iain Buclaw

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=CABOHX+cyN-3SxWKQYG_kvuSEaNU_SVXJOZuA0BXjSVKJ0feRBw@mail.gmail.com \
    --to=ibuclaw@gdcproject.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).