From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: Marius Vollmer <mvo@zagadka.de>
Subject: Re: Summary of config.h variables and questions.
Date: Thu, 06 Mar 2003 18:26:30 +0100 [thread overview]
Message-ID: <xy78yvsfltl.fsf@nada.kth.se> (raw)
In-Reply-To: <878yvswkrg.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 06 Mar 2003 09:57:23 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
>>> 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
It doesn't need to be visible publicly. It is only used to compile in
some extra code in order to provide the memory debugging function
`malloc-stats'.
Probably it should be renamed according to the new style for debug
options (SCM_DEBUG_XXX).
_______________________________________________
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 17:26 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
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 [this message]
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=xy78yvsfltl.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
--cc=mvo@zagadka.de \
/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).