unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: <dsmich@roadrunner.com>
To: guile-devel <guile-devel@gnu.org>,
	Guile User <guile-user@gnu.org>,
	 Neil Jerram <neiljerram@googlemail.com>
Subject: Re: Killing off scm_init_guile for Guile 2.0 ?
Date: Fri, 16 Jan 2009 16:32:14 -0500	[thread overview]
Message-ID: <20090116213215.YITDV.179685.root@cdptpa-web09-z02> (raw)
In-Reply-To: <49dd78620901151530o66a2641ax47e526d15fc09faf@mail.gmail.com>

---- Neil Jerram <neiljerram@googlemail.com> wrote: 
> scm_init_guile has always been a bit problematic, as it requires lots
> of heuristic and OS-dependent code to try to determine where the base
> of the stack is.  It's never been formally deprecated, but we have
> always advised people to use scm_boot_guile or scm_with_guile if they
> can, and the manual says:
> 
>      The function `scm_init_guile' might not be available on all
>      platforms since it requires some stack-bounds-finding magic that
>      might not have been ported to all platforms that Guile runs on.
>      Thus, if you can, it is better to use `scm_with_guile' or its
>      variation `scm_boot_guile' instead of this function.

[ ... ]

> Thoughts?  On the other hand, does moving to BDW-GC take a lot of this
> out of our hands anyway?  In any case, it would be interesting to hear
> whether people think that scm_init_guile is really needed.


Iirc, scm_init_guile is mainly used when you do not have access to main(), for example writing a module for apache.  Generally, when you want to add Guile to an already existing application that has plugins or extension modules via .so's.

-Dale







  parent reply	other threads:[~2009-01-16 21:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 23:30 Killing off scm_init_guile for Guile 2.0 ? Neil Jerram
2009-01-15 23:48 ` Neil Jerram
2009-01-16 14:57   ` Ludovic Courtès
2009-01-16  3:59 ` Linas Vepstas
2009-01-16 15:00   ` Ludovic Courtès
2009-01-16 15:41     ` Bill Schottstaedt
2009-01-23  1:49   ` Neil Jerram
2009-01-16 21:32 ` dsmich [this message]
2009-01-17  1:36   ` Linas Vepstas
2009-01-21 21:52     ` Zeeshan Ali (Khattak)
2009-01-23  2:02     ` Neil Jerram
2009-01-23  6:13       ` Clinton Ebadi
2009-01-23 16:23         ` Ludovic Courtès
2009-01-23 16:21       ` Ludovic Courtès
     [not found] <cmu-lmtpd-4567-1232125596-3@mail-imap1.uio.no>
2009-01-16 17:20 ` Kjetil S. Matheussen
2009-01-23  1:44   ` Neil Jerram
2009-01-23  9:12     ` Kjetil S. Matheussen

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=20090116213215.YITDV.179685.root@cdptpa-web09-z02 \
    --to=dsmich@roadrunner.com \
    --cc=guile-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=neiljerram@googlemail.com \
    /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).