From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: What's the matter?
Date: Tue, 13 Dec 2005 23:02:42 +0200 [thread overview]
Message-ID: <871x0gvhfx.fsf@zagadka.de> (raw)
In-Reply-To: <200512051551.41243.bkorb@gnu.org> (Bruce Korb's message of "Mon, 5 Dec 2005 15:51:41 -0800")
Bruce Korb <bkorb@gnu.org> writes:
> It turns out that in all places where I was using scm_makstr(), I
> was also using SCM_CHARS to access the string memory and then fill
> it in. It *must* be safe to do because I don't call any scheme
> functions before I am done scribbling in the memory.
I would like to reproduce this. Could you give me instructions for
how to do that?
What you describe _ought_ to work. If we can't get SCM_CHARS /
SCM_STRING_CHARS to work we might as well remove it.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-12-13 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 21:26 What's the matter with "scm_string_p()"? Bruce Korb
2005-12-03 23:26 ` Kevin Ryde
2005-12-05 13:57 ` Han-Wen Nienhuys
[not found] ` <200512041615.15333.bkorb@gnu.org>
[not found] ` <87lkyzp4c0.fsf@zip.com.au>
2005-12-05 23:51 ` What's the matter? Bruce Korb
2005-12-13 21:02 ` Marius Vollmer [this message]
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=871x0gvhfx.fsf@zagadka.de \
--to=mvo@zagadka.de \
--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).