From: Lynn Winebarger <owinebar@free-expression.org>
Cc: Guile-user@gnu.org
Subject: Re: Guile library behaviour
Date: Mon, 29 Apr 2002 23:29:09 -0500 [thread overview]
Message-ID: <0204292329090J.10649@locke.free-expression.org> (raw)
In-Reply-To: <87bscifjo0.fsf@raven.i.defaultvalue.org>
On Wednesday 17 April 2002 10:07, Rob Browning wrote:
> The original reason for this is just as Lynn explained it -- this used
> to be the only way guile could portably find the bottom of the stack.
> Also note that as things stand now, you can only run one copy of guile
> inside any given app.
>
> In general, if you're the one designing the app, the requirement that
> guile be handed your real main function isn't a big deal, but in some
> cases this isn't possible. Fortunately, in more recent versions of
> guile, clever people have figured out a fairly portable way to find
> the bottom of the stack, and so on those platforms, you can use
> scm_init_guile, which will return, and then you can go do whatever
> else you want in your code.
Mea culpa. They are clever, that's for sure. The heuristic that
crawls up the stack until it causes a segmentation fault or bus error
- that's the good stuff.
Lynn
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2002-04-30 4:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-17 8:15 Guile library behaviour Daniel CAUNE
2002-04-17 12:14 ` Lynn Winebarger
2002-04-17 15:07 ` Rob Browning
2002-04-17 15:19 ` Daniel CAUNE
2002-04-17 15:21 ` Daniel CAUNE
2002-04-17 15:35 ` Daniel CAUNE
2002-04-30 4:29 ` Lynn Winebarger [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
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=0204292329090J.10649@locke.free-expression.org \
--to=owinebar@free-expression.org \
--cc=Guile-user@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).