From: Mikael Djurfeldt <mdj@kvast.blakulla.net>
Cc: guile-user@gnu.org
Subject: Re: Stack Size?
Date: 09 Aug 2002 15:48:22 +0200 [thread overview]
Message-ID: <xy77kj0rvmh.fsf@kvast.blakulla.net> (raw)
In-Reply-To: <m31y999g29.fsf@latakia.dyndns.org>
ruhl@4dv.net (Robert Uhl <ruhl@4dv.net>) writes:
> Neil Jerram <neil@ossau.uklinux.net> writes:
> >
> > > I've re-written the function, but it seems to me that it'd perhaps
> > > make more sense for Guile to simply grow the stack until it runs
> > > out of memory. Is there a technical reason this doesn't happen?
> >
> > No idea, I'm afraid. Perhaps it's considered a good thing for a
> > language to allow applications to have a grip on their stack usage?
Guile is supposed to be "nice" towards novice users. Infinite
recursions is a very common error. Without a stack check, the effect
is that the machine freezes due to excessive swapping, preventing the
novice user from even examining what has happened.
> It seems to me somewhat broken that one must set a debug option
> explicitly off. Sort of a command-line switch --behave-yourself, when
> that should be the default behaviour. Certainly, stack size checks
> may be _very_ useful when testing code. But just as certainly, in
> production those same checks are a nuisance, and can cause code to
> break.
It's probably a bad idea to use large stacks in production code and,
if not, it's rather easy to set the option to whatever one wants.
Maybe the correct setting is a very large stack?
M
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-08-09 13:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-05 9:27 Stack Size? Robert Uhl <ruhl@4dv.net>
2002-08-05 15:08 ` Joshua Judson Rosen
2002-08-05 18:55 ` Neil Jerram
2002-08-05 19:09 ` Robert Uhl <ruhl@4dv.net>
2002-08-08 21:28 ` Neil Jerram
2002-08-08 21:49 ` Robert Uhl <ruhl@4dv.net>
2002-08-09 13:48 ` Mikael Djurfeldt
2002-08-09 13:48 ` Mikael Djurfeldt
2002-08-09 13:48 ` Mikael Djurfeldt [this message]
2002-08-11 22:07 ` Robert Uhl <ruhl@4dv.net>
2002-09-01 17:13 ` Rob Browning
2002-09-01 19:08 ` Lynn Winebarger
2002-09-03 16:00 ` Paul Jarc
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=xy77kj0rvmh.fsf@kvast.blakulla.net \
--to=mdj@kvast.blakulla.net \
--cc=djurfeldt@nada.kth.se \
--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).