From: Neil Jerram <neil@ossau.uklinux.net>
Cc: bug-guile@gnu.org, guile-devel@gnu.org
Subject: Re: Can't make a stack from a continuation
Date: Fri, 24 Dec 2004 23:05:25 +0000 [thread overview]
Message-ID: <41CCA0B5.2070107@ossau.uklinux.net> (raw)
In-Reply-To: <ljmzw59gcn.fsf@troy.dt.e-technik.uni-dortmund.de>
Marius Vollmer wrote:
> Marius Vollmer <marius.vollmer@uni-dortmund.de> writes:
>
>
>>Neil Jerram <neil@ossau.uklinux.net> writes:
>>
>>
>>>And one more problem ... the same problem exists in CVS head, but a
>>>similar patch doesn't fix it ... still investigating.
>>
>>I'm looking into this as well, now. The fix you did for 1.6 looks
>>good, although I don't understand it completely yet. I will try to
>>come up with my own patch to CVS head.
>
>
> Here it is. I have already applied it to CVS. I think a similar
> scheme can be used for 1.6, too: i.e., move the offset calculation
> into scm_make_continuation.
>
> Neil, do you want to fix 1.6 yourself?
>
> [patch]
This change (calculating and storing the offset in
scm_make_continuation) makes sense, but I'd like also to understand
where the bug was in my version (using offset = (SCM_CONTREGS (stack) ->
stack) - SCM_BASE (stack);) and why my code worked in 1.6 but not in
head. Would you mind explaining?
Thanks,
Neil
PS. Merry Christmas!
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2004-12-24 23:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41A23580.6070702@ossau.uklinux.net>
2004-11-25 19:43 ` Can't make a stack from a continuation Neil Jerram
2004-12-17 1:42 ` Neil Jerram
2004-12-23 14:24 ` Marius Vollmer
2004-12-23 15:36 ` Marius Vollmer
2004-12-24 23:05 ` Neil Jerram [this message]
2004-12-24 23:11 ` Neil Jerram
2004-12-24 23:22 ` Marius Vollmer
2004-12-25 10:51 ` Neil Jerram
2004-12-27 23:23 ` Neil Jerram
2004-12-24 23:21 ` Marius Vollmer
2004-12-25 10:50 ` Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41CCA0B5.2070107@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=bug-guile@gnu.org \
--cc=guile-devel@gnu.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).