From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: guile-devel@gnu.org
Subject: Re: port-for-each vs lazy sweep
Date: Sun, 26 Aug 2007 14:16:18 -0300 [thread overview]
Message-ID: <46D1B562.5030104@xs4all.nl> (raw)
In-Reply-To: <8764328bxq.fsf@chbouib.org>
Ludovic Courtès escreveu:
>> @@ -472,6 +480,7 @@ scm_i_init_guile (SCM_STACKITEM *base)
>> scm_init_backtrace (); /* Requires fluids */
>> scm_init_fports ();
>> scm_init_strports ();
>> + scm_init_ports ();
>> scm_init_gdbint (); /* Requires strports */
>> scm_init_hash ();
>> scm_init_hashtab ();
>> @@ -490,7 +499,6 @@ scm_i_init_guile (SCM_STACKITEM *base)
>> scm_init_numbers ();
>> scm_init_options ();
>> scm_init_pairs ();
>> - scm_init_ports ();
>
> Why does it need to be moved?
because gdb instantiates a port; I forgot why it used to work
though.
>> - SCM_SETPTAB_ENTRY (port, pt);
>> + SCM_SETPTAB_ENTRY(port, pt);
>
> Please follow GNU style.
I have the impression that GUILE isn't really consistent
[lilydev@haring libguile]$ grep '[A-Z](' *c|grep -v define|wc
394 2037 24632
[lilydev@haring libguile]$ grep '[a-z](' *c|grep -v define|wc
490 3038 28008
time for a grand search & replace patch?
>> -#ifdef GUILE_DEBUG
>> /* Functions for debugging. */
>
> Why remove the `#ifdef'?
oops.
>
>> --- a/m4/gnulib-cache.m4
>> +++ b/m4/gnulib-cache.m4
>> @@ -23,6 +23,7 @@ gl_MODULES([alloca strcase])
>> gl_AVOID([])
>> gl_SOURCE_BASE([lib])
>> gl_M4_BASE([m4])
>> +gl_PO_BASE([])
>
> This is unrelated.
yes, I know. Too lazy to strip this from the output. But won't apply to CVS.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-08-26 17:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-19 1:22 port-for-each vs lazy sweep Kevin Ryde
2007-08-20 8:42 ` Ludovic Courtès
2007-08-21 0:30 ` Kevin Ryde
2007-08-23 0:32 ` Kevin Ryde
2007-08-23 7:25 ` Ludovic Courtès
2007-08-25 18:57 ` Han-Wen Nienhuys
2007-08-25 22:20 ` Han-Wen Nienhuys
2007-08-26 17:04 ` Ludovic Courtès
2007-08-26 17:16 ` Han-Wen Nienhuys [this message]
2007-08-26 17:36 ` Ludovic Courtès
2007-08-26 18:06 ` Han-Wen Nienhuys
2007-09-03 17:20 ` Ludovic Courtès
2007-09-03 19:34 ` Han-Wen Nienhuys
2007-09-04 9:08 ` Ludovic Courtès
2007-10-01 20:23 ` Ludovic Courtès
2007-10-27 15:07 ` Ludovic Courtès
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=46D1B562.5030104@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=guile-devel@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).