From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: gdb-patches@sources.redhat.com
Subject: Re: Resend: [RFC] p-exp.y enhancements.
Date: Thu, 16 May 2002 02:44:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020516114040.00a74118@ics.u-strasbg.fr> (raw)
In-Reply-To: <4.2.0.58.20020502144659.02489e38@ics.u-strasbg.fr>
As no strong objection was rasied against this
patch, I committed it today.
At 14:48 02/05/2002 , Pierre Muller a écrit:
>(Second posting with the patch attached,
>this way you should have less problems to
>apply the patch).
>
>This patch has several benefits:
>
>1) it adds support for S[exp] if S is a pascal string.
>I must admit that this only works for Free Pascal Compiler
> for now, because GPC uses BITSTRING type
>for the array containg the chars which confuses GDB.
>I informed the GPC developper team, but their answer
>seems to be that they didn't really directly change any code
>regarding debug information output for pascal...
>
>2) it adds support for case insensitive searches of record
>(pascal struct) fields.
>
>3) It prepares to a more simple RFC
>about the enhancement to the completer for
>structure field that I sent some time ago. See
>http://sources.redhat.com/ml/gdb-patches/2002-04/msg00774.html
>
>The way current_type is treated in my patch is
>not completely correct, in the sense that
>current_type is often non NULL when it should be NULL
>(like for instance after an operator like '+' or '*',
>but this has no influence on its functionallity, so I did not
>add all the rules that would reset current_type
>(which would have made the patch much bigger).
>
>If I get no observations about this patch, I will commit it
>in the next days.
>
>
>2002-05-02 Pierre Muller <muller@ics.u-strasbg.fr>
>
> * p-exp.y (current_type): New static variable.
> Carries the type of the expression at the position that is parsed.
> (push_current_type, pop_current_type): Two new functions. Used
> to store/restore current_type in expression on specific tokens.
> (search_filed): New static variable. Set to one after parsing a point as
> at that point only a FIELDNAME token should be searched.
> (FIELDNAME): New token. After a point only a token belonging to
> current_type type definition is allowed.
> (all over token rules): reset and change current_type according
> to rules.
> (exp '[' rule): insert implicit array index field if exp is a pascal string type.
>
>
>
>Pierre Muller
>Institut Charles Sadron
>6,rue Boussingault
>F 67083 STRASBOURG CEDEX (France)
>mailto:muller@ics.u-strasbg.fr
>Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07 Fax : (33)-3-88-41-40-99
prev parent reply other threads:[~2002-05-16 9:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 5:50 Pierre Muller
2002-05-02 11:06 ` Michael Snyder
2002-05-03 0:49 ` Pierre Muller
2002-05-03 10:40 ` Michael Snyder
2002-05-16 2:44 ` Pierre Muller [this message]
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=4.2.0.58.20020516114040.00a74118@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=gdb-patches@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