unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <mvo@zagadka.de>
Cc: guile development <guile-devel@gnu.org>
Subject: Re: How do I determine the argument type...
Date: 17 May 2003 22:14:04 +0200	[thread overview]
Message-ID: <874r3t5o1f.fsf@zagadka.ping.de> (raw)
In-Reply-To: <3EBC71BF.B2264C7@veritas.com>

Bruce Korb <bkorb@veritas.com> writes:

> The problem is with gh_scm2newstr:
> 
>     size_t  len;
>     char*   pz = gh_scm2newstr( str, &len );
> 
> This is a problem on a platform where the argument is actually
> int* and the platform is I32LP64.  i.e., the size_t is 64 bits.
> Since other versions of the library use size_t, I think I'm
> pretty much hosed without using an scm2newstr_size_t :-(

I don't understand.  Bothe 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?

-- 
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


  parent reply	other threads:[~2003-05-17 20:14 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 [this message]
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

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=874r3t5o1f.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).