From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: hanwen@xs4all.nl, guile-devel@gnu.org
Subject: Re: [PATCH] Inlining `scm_is_pair ()'
Date: Mon, 30 Jan 2006 10:06:40 +0100 [thread overview]
Message-ID: <87bqxu3x0f.fsf@laas.fr> (raw)
In-Reply-To: <87bqxwxaz6.fsf@zagadka.de> (Marius Vollmer's message of "Sun, 29 Jan 2006 00:07:41 +0200")
Hi,
Marius Vollmer <mvo@zagadka.de> writes:
> I just put scm_is_pair into inline.h, using our existing inlining
> machinery that should be portable enough. Ok?
Ok, thanks! But (there's always a `but' ;-)) it feels somewhat wrong to
put it in `inline.h' rather than in `pairs.h' just because it's inline.
> This happens to me with and without scm_is_pair being an inline. Our
> default stack limit just seems to be too tight. We could arbitarily
> raise it from 20000 to, say, 30000.
Right, maybe we should do it.
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-01-30 9:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 14:46 [PATCH] Turning `scm_is_pair ()' into a macro Ludovic Courtès
2005-12-14 20:57 ` Kevin Ryde
2005-12-14 23:00 ` Han-Wen Nienhuys
2005-12-14 23:19 ` Marius Vollmer
2005-12-15 9:39 ` Ludovic Courtès
2005-12-16 0:08 ` Han-Wen Nienhuys
2005-12-16 10:01 ` Ludovic Courtès
2006-01-24 8:37 ` [PATCH] Inlining `scm_is_pair ()' Ludovic Courtès
2006-01-24 20:12 ` Kevin Ryde
2006-01-25 9:21 ` Ludovic Courtès
2006-01-26 23:13 ` Kevin Ryde
2006-01-27 9:13 ` Ludovic Courtès
2006-01-28 22:07 ` Marius Vollmer
2006-01-30 9:06 ` Ludovic Courtès [this message]
2006-02-03 23:49 ` Kevin Ryde
2006-02-05 19:10 ` Marius Vollmer
2005-12-16 0:41 ` [PATCH] Turning `scm_is_pair ()' into a macro Kevin Ryde
2005-12-16 20:01 ` 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=87bqxu3x0f.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-devel@gnu.org \
--cc=hanwen@xs4all.nl \
/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).