From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: Async function calls
Date: Thu, 20 Mar 2008 16:23:00 -0000 [thread overview]
Message-ID: <frtksl$htu$1@ger.gmane.org> (raw)
In-Reply-To: <20080320121019.GA6677@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Thu, Mar 20, 2008 at 10:44:46AM +0300, Vladimir Prus wrote:
>> Maybe, somebody have bright ideas?
>
> Could we pick out the inferior function calls and evaluate them first,
> with continuations? Except that could change order of evaluation;
> we'd have to read the values of variables at the same time.
Will it help? Say, we do:
print foo()
then to do it async way, we have to do the function call, and then
'print' should get back to action and print the value. Right now,
print_command has no continuations, so we'll have to add it.
And likewise, it seems that every command that can call a function
will have to be converted to use continuation.
- Volodya
next prev parent reply other threads:[~2008-03-20 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-20 12:10 Vladimir Prus
2008-03-20 12:22 ` Daniel Jacobowitz
2008-03-20 16:23 ` Vladimir Prus [this message]
2008-03-20 17:01 ` Daniel Jacobowitz
2008-03-20 17:24 ` Daniel Jacobowitz
2008-03-20 17:35 ` Michael Snyder
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='frtksl$htu$1@ger.gmane.org' \
--to=ghost@cs.msu.su \
--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