From: Kevin Ryde <user42@zip.com.au>
Subject: Re: How do I determine the argument type...
Date: Thu, 12 Jun 2003 08:33:13 +1000 [thread overview]
Message-ID: <87r860nt1y.fsf@zip.com.au> (raw)
In-Reply-To: <874r39prgm.fsf@zagadka.ping.de> (Marius Vollmer's message of "01 Jun 2003 20:45:13 +0200")
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
Marius Vollmer <mvo@zagadka.de> writes:
>
> Hmm, no, I prefer changing the docs. "size_t" is the right type, and
> not many people seem to be affected by the int -> size_t change, so we
> chould leave it at size_t.
Not that it's much to do with me, but while I'm working on the docs I
made this change.
* gh.texi (Scheme to C): In gh_scm2newstr, lenp is size_t* not int*.
This changed in guile 1.6, the docs weren't updated.
Dunno if the manual itself needs a compatibility note. If no-one else
has tripped over it and the interface itself is considered obsolete
then hardly worth worrying.
[-- Attachment #2: gh.texi.gh_scm2newstr.diff --]
[-- Type: text/plain, Size: 524 bytes --]
--- gh.texi.~1.6.~ 2003-04-05 16:47:18.000000000 +1000
+++ gh.texi 2003-06-10 16:47:40.000000000 +1000
@@ -433,7 +433,7 @@
These routines convert the Scheme object to the given C type.
@end deftypefun
-@deftypefun char *gh_scm2newstr (SCM @var{str}, int *@var{lenp})
+@deftypefun char *gh_scm2newstr (SCM @var{str}, size_t *@var{lenp})
Given a Scheme string @var{str}, return a pointer to a new copy of its
contents, followed by a null byte. If @var{lenp} is non-null, set
@code{*@var{lenp}} to the string's length.
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-06-11 22:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 3:27 How do I determine the argument type Bruce Korb
2003-05-10 3:31 ` Bruce Korb
2003-05-17 20:14 ` Marius Vollmer
2003-05-17 21:16 ` Bruce Korb
2003-05-18 1:57 ` Marius Vollmer
2003-05-18 2:59 ` Bruce Korb
2003-05-19 0:07 ` Kevin Ryde
2003-05-19 0:34 ` Bruce Korb
2003-05-19 0:47 ` Kevin Ryde
2003-05-19 1:44 ` Bruce Korb
2003-06-01 18:45 ` Marius Vollmer
2003-06-01 20:07 ` Bruce Korb
2003-06-11 22:33 ` Kevin Ryde [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=87r860nt1y.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).