From: Tom Tromey <tromey@redhat.com>
To: Joost van der Sluis <joost@cnoc.nl>
Cc: gdb@sourceware.org, Pierre Free Pascal <pierre@freepascal.org>
Subject: Re: Calling class-methods in pascal (fpc)
Date: Wed, 05 Oct 2011 18:04:00 -0000 [thread overview]
Message-ID: <m3ipo3jowr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1316461626.3660.12.camel@feddie.cnoc.lan> (Joost van der Sluis's message of "Mon, 19 Sep 2011 21:47:06 +0200")
>>>>> "Joost" == Joost van der Sluis <joost@cnoc.nl> writes:
I didn't see a response to this.
Joost> Now to be able to fix this properly, I need to know what the function of
Joost> parse_expression() is compared to evaluate_expression()? To me it looks
Joost> like it that parse_expression is not needed at all.
parse_expression parses a string and yields an expression object (struct
expression).
evaluate_expression evaluates a struct expression.
Basically you want this split so that you can parse some expressions
once, then evaluate them many times. E.g., breakpoint conditions work
this way.
Tom
prev parent reply other threads:[~2011-10-05 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 19:47 Joost van der Sluis
2011-10-05 18:04 ` Tom Tromey [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=m3ipo3jowr.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=joost@cnoc.nl \
--cc=pierre@freepascal.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).