From: Marius Vollmer <mvo@zagadka.de>
Cc: guile development <guile-devel@gnu.org>
Subject: Re: How do I determine the argument type...
Date: 18 May 2003 03:57:51 +0200 [thread overview]
Message-ID: <87of213tk0.fsf@zagadka.ping.de> (raw)
In-Reply-To: <3EC6A6CA.94855664@veritas.com>
Bruce Korb <bkorb@veritas.com> writes:
> > I don't understand. Both 1.6 and 1.7 have this prototype for
> > gh_scm2newstr:
> >
> > char *gh_scm2newstr (SCM str, size_t *lenp);
> >
> > On what platform is the argument actually an "int*"? Can you give a
> > specific example that must fail?
>
> $ guile --version
> Guile 1.4
> Copyright (c) 1995, 1996, 1997, 2000 Free Software Foundation
> ...
> $ fgrep gh_scm2newstr /opt/TWWfsw/guile14/include/guile/gh.h
> char *gh_scm2newstr(SCM str, int *lenp);
> $ uname -a
> HP-UX kibo B.11.00 A 9000/800 1596730518 two-user license
Ahh, I see. Yes, it was not a good thing to change gh_new2str that
way. I'm not sure what to do about this. Changing this back is just
as bad as the original change from int to size_t.
Personally, I would stop supporting Guile 1.4 and just require Guile
1.6 for newer versions of your code...
I dirty workaround, in this particular case, might be to always pass
NULL as lenp and get the length via scm_string_length (or strlen if
you don't care about '\0' characters in the middle of the string).
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-18 1:57 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 [this message]
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
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=87of213tk0.fsf@zagadka.ping.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).