unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: bug-guile@gnu.org, guile-devel@gnu.org
Subject: Re: Can't make a stack from a continuation
Date: 25 Dec 2004 00:21:35 +0100	[thread overview]
Message-ID: <87652rqo3k.fsf@zagadka.de> (raw)
In-Reply-To: <41CCA0B5.2070107@ossau.uklinux.net>

Neil Jerram <neil@ossau.uklinux.net> writes:

> 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?

Hmm, I didn't really try to debug your patch.  I followed its idea of
also relocating dframe->vect and made the changes that seemed right.

Using offset = SCM_CONTREGS (stack)->stack - SCM_BASE(stack) looks
right.  The bug is probably elsewhere...

> PS. Merry Christmas!

Thanks and Merry Christmas from me to everyone as well!

(I got a high-tech electric iron in transparent iMac design from my
mom! :-)

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


  parent reply	other threads:[~2004-12-24 23:21 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
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 [this message]
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=87652rqo3k.fsf@zagadka.de \
    --to=mvo@zagadka.de \
    --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).