[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Guile library behaviour
From: |
Lynn Winebarger |
Subject: |
Re: Guile library behaviour |
Date: |
Mon, 29 Apr 2002 23:29:09 -0500 |
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