Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: gdb-patches@sourceware.org
Subject: [0/5] FYI: fix typename parsing bugs
Date: Fri, 06 Jul 2012 14:36:00 -0000	[thread overview]
Message-ID: <87k3yhot2g.fsf@fleche.redhat.com> (raw)

This series fixes the typename parsing regressions I introduced, and
also the other typename bugs I tripped across:

    (gdb) whatis int *(*)()
    type = int (**)()

... my regression

    (gdb) whatis int (*)(double)
    type = int (*)()

Argument types dropped.

    (gdb) whatis char (*(*)())[23]
    type = char (**)())[23]

Bad parse.

    (gdb) whatis int(*)(const int *, ...)
    A syntax error in expression, near `...)'.

Doesn't understand varargs.

    (gdb) whatis const int * (*)(const int *)
    type = const int ()

"*" mysteriously dropped.


There is still one more bug remaining that I know of, but I didn't think
it was important enough to bother with right now:

    (gdb) whatis int & &
    type = int &&

A reference to a reference doesn't make sense.
Maybe I'll fix this later; it wasn't immediately clear to me exactly
where this ought to error out.

Tom


             reply	other threads:[~2012-07-06 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-06 14:36 Tom Tromey [this message]
2012-07-07 12:58 ` Still regressing, now: Too few arguments in function call [Re: [0/5] FYI: fix typename parsing bugs] Jan Kratochvil
2012-07-09 14:20   ` Tom Tromey

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=87k3yhot2g.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@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