Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: dan@cgsoftware.com
Cc: gdb@sources.redhat.com
Subject: Re: Cast to a struct in expressions
Date: Fri, 27 Apr 2001 10:41:00 -0000	[thread overview]
Message-ID: <6137-Fri27Apr2001204221+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <m2eluev01g.fsf@dynamic-addr-83-177.resnet.rochester.edu>

> From: Daniel Berlin <dan@cgsoftware.com>
> Date: 27 Apr 2001 11:23:55 -0400
> 
> >   A parse error in expression, near `long foo; unsigned bar} *)foobar
> > 
> > Seems like the parser chokes on the struct declaration?
> Yes.
> >   Am I missing something?
> Yes, I think. The parser only handles expressions, nothing more.
> This is why it's c-exp.y, and not c.y.
> :)
> 
> If you have a real struct already defined, of course, and di
> 
> p/x *(sturct foostruct *)foobar
> 
> then *that* should work.

No, there's no such struct, otherwise I wouldn't be opting for this
complication ;-)

I'm still missing something, because I don't see how "*(struct foo *)x"
differs from "*(struct {long foo; unsigned bar;} *)x".  Both are valid
C expression syntax, so the parser should be able to parse them both.

I guess someone just stopped short of making this part of the parser,
because it looks like "struct <name>" is the only syntax it accepts.
Right?

Anyway, thanks for the feedback.


  reply	other threads:[~2001-04-27 10:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27  1:10 Eli Zaretskii
2001-04-27  8:24 ` Daniel Berlin
2001-04-27 10:41   ` Eli Zaretskii [this message]
2001-04-27 12:30     ` Daniel Berlin
2001-04-28  1:08       ` Eli Zaretskii
2001-04-28  2:12         ` Paul Hilfinger
2001-04-28 11:30           ` Daniel Berlin
2001-04-28 11:09         ` Daniel Berlin
2001-04-28 23:47           ` Eli Zaretskii
2001-04-28 23:52             ` Daniel Berlin
2001-04-29  0:20               ` Eli Zaretskii

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=6137-Fri27Apr2001204221+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=dan@cgsoftware.com \
    --cc=gdb@sources.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