From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org
Subject: Re: Summary of config.h variables and questions.
Date: Thu, 06 Mar 2003 09:57:23 -0600 [thread overview]
Message-ID: <878yvswkrg.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87of4otvb0.fsf@zagadka.ping.de> (Marius Vollmer's message of "06 Mar 2003 15:37:55 +0100")
Marius Vollmer <mvo@zagadka.de> writes:
> Excellent work! Thank a lot for doing this, Rob!
>
> Since this is a major change, we should not be doing it in the 1.6
> series unless there is a real and specific problem with them (as with
> PACKAGE). For 1.7, we can make more sweeping changes to offer better
> alternatives (see below).
Definitely. I'm only working on the 1.7 tree right now.
> We should keep these, since they have a proper name already:
>
>> GUILE_DEBUG_MALLOC
Right. The main question I had about this one was whether it needed
to be public -- it looks like it isn't used in any of our public
headers, but it was visible via scmconfig.h
> We should deprecate-and-keep these:
>
>> DYNAMIC_LINKING
>> GUILE_ISELECT
>> READER_EXTENSIONS
>> STACK_DIRECTION
>> USE_THREADS
>
> Alternatives are
What do you mean by "Alternatives", an alternative to
"deprecate-and-keep"?
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-03-06 15:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-05 5:44 Summary of config.h variables and questions Rob Browning
2003-03-06 14:37 ` Marius Vollmer
2003-03-06 15:57 ` Rob Browning [this message]
2003-03-06 16:21 ` Marius Vollmer
2003-03-06 16:32 ` Rob Browning
2003-03-06 16:34 ` Rob Browning
2003-03-06 16:48 ` Marius Vollmer
2003-03-06 16:49 ` Marius Vollmer
2003-03-06 17:26 ` Mikael Djurfeldt
2003-03-06 18:27 ` Rob Browning
2003-03-06 18:48 ` Marius Vollmer
2003-03-06 22:10 ` Kevin Ryde
2003-03-07 5:24 ` Rob Browning
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=878yvswkrg.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--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).