From: P Pareit <pieter.pareit@planetinternet.be>
Subject: Re: problem becouse scm_tc7_contin is not defined
Date: Tue, 10 Sep 2002 13:57:22 +0200 [thread overview]
Message-ID: <200209101357.22695.pieter.pareit@planetinternet.be> (raw)
In-Reply-To: <20020910103210.30704.32477.Mailman@monty-python.gnu.org>
On Tuesday 10 September 2002 12:32 pm, Marius Vollmer wrote:
>
> P Pareit <pieter.pareit@planetinternet.be> writes:
> > By doing a grep on scm_tc7_contin in the source tree of guile I
> > found out that scm_tc7_contin is no longer supported and I have to
> > use SMOB continuation for rootcont instead.
>
> Scwm is digging into the innards of Guile, and we don't really support
> code like scm_internal_cwdr_no_unwind. Scm_internal_cwdr_no_unwind is
> essentially a copy of Guile's scm_internal_cwdr with some bits
> removed. There is a reason why it is called scm_*internal*_cwdr. ;-)
>
> However, scwm has probably a real need for
> scm_internal_cwdr_no_unwind, and we do want to support something like
> it officially in the future so that scwm does not need to provide its
> own hack.
>
> You might consider fixing scwm's hack like this
>
> SCM
> scm_internal_cwdr_no_unwind (scm_catch_body_t body, void *body_data,
> scm_catch_handler_t handler, void
> *handler_data, SCM_STACKITEM *stack_start)
> {
> SCM answer, old_winds;
> old_winds = scm_dynwinds;
> scm_dynwinds = SCM_EOL;
>
> answer = scm_internal_cwdr (body, body_data, handler, handler_data,
> stack_start); /* changed to stack_start */
>
> scm_dynwinds = old_winds;
> return answer;
> }
Tried and failed, it does compile but I get a segment fault at startup and
scm_internal_cwdr_no_unwind shows up in the backtrace. So I think this is the
problem.
>
> This will _only_ work when HANDLER does not do a non-local exit (via
> longjmp, or similar). If you want to support that (which I
> recommend), you need to defer running HANDLER (with the same trick
> that scm_internal_cwdr uses) until scm_dynwinds has been restored.
>
> The above code should be more resilient against changes to the
> internals of Guile, but it is still a hack. We have a proposal to fix
> this for real. See workbook/extension/dynamic-roots.text in CVS.
>
> You might also try to just scm_internal_cwdr instead of
> scm_internal_cwdr_no_unwind. That should work as well, but at a
> slight performance loss.
>
> Could you bring this up with the scwm developers so that we might find
> a solution that makes everyone happy?
Yes, will do. I'm afraid that for the moment guile-1.4.* will still be used
and development is not very active for the moment. I hope that with the way
guile is going at the moment, scwm will soon follow.
pieter;
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next parent reply other threads:[~2002-09-10 11:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020910103210.30704.32477.Mailman@monty-python.gnu.org>
2002-09-10 11:57 ` P Pareit [this message]
2002-09-10 19:04 ` problem becouse scm_tc7_contin is not defined Marius Vollmer
2002-09-11 10:01 ` P Pareit
2002-09-11 18:16 ` Marius Vollmer
2002-09-16 0:04 ` Steve Tell
2002-09-16 5:00 ` Rob Browning
2002-09-16 19:57 ` Marius Vollmer
2002-09-20 1:55 ` 1.4 vs. 1.5.x vs 1.6 snarfingdefined Steve Tell
2002-09-09 9:18 problem becouse scm_tc7_contin is not defined P Pareit
2002-09-09 18:08 ` Marius Vollmer
2002-09-09 18:10 ` Marius Vollmer
2002-09-09 18:43 ` Marius Vollmer
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=200209101357.22695.pieter.pareit@planetinternet.be \
--to=pieter.pareit@planetinternet.be \
/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).