unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Bruce Korb <bkorb@veritas.com>
Cc: guile-devel@gnu.org
Subject: Re: How do I determine the argument type...
Date: Sun, 18 May 2003 17:34:17 -0700	[thread overview]
Message-ID: <3EC82689.6A652B72@veritas.com> (raw)
In-Reply-To: 87ptmfx0i3.fsf@zip.com.au

Kevin Ryde wrote:
> 
> Marius Vollmer <mvo@zagadka.de> writes:
> >
> > 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.
> 
> The manual still says "int".  Maybe call it a bug fix and put it back
> to that.
> 
> Or making it a macro could hide the variation for plain calls, which
> is presumably most usages.

A macro cannot hide the problem.  You cannot set it back to int without
breaking everyone who adapted to size_t.  The best choice is to just
say, "Oops.  Sorry.  Either reject Guile 1.4 or use this configury macro
to specify the type passed to gh_scm2newstr()."  Or, alternatively,
always pass NULL as the second argument.  Don't go back, though.  Thanks!


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-05-19  0:34 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 [this message]
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=3EC82689.6A652B72@veritas.com \
    --to=bkorb@veritas.com \
    --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).