unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Bad deprecation warnings in numbers.c
Date: 01 Apr 2002 16:10:09 +0100	[thread overview]
Message-ID: <m3k7rrwj3i.fsf@laruns.ossau.uklinux.net> (raw)

There is a group of deprecation warnings in (stable) numbers.c that
say, for example:

  scm_c_issue_deprecation_warning ("`scm_mkbig' is deprecated. "
                                   "Use `scm_i_mkbig' instead.");

No!!!!!

This directly contradicts our aim of using `scm_i_' to mark Guile
internals, which libguile users shouldn't use _at all_!

What's the right thing here?  Could we do it before 1.6?

        Neil


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile


             reply	other threads:[~2002-04-01 15:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-01 15:10 Neil Jerram [this message]
2002-04-02 19:16 ` Bad deprecation warnings in numbers.c Dirk Herrmann
2002-04-13 12:44   ` Neil Jerram
2002-04-15 21:42     ` Dirk Herrmann
2002-04-14  5:11   ` Rob Browning
2002-04-15 21:44     ` Dirk Herrmann

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=m3k7rrwj3i.fsf@laruns.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    /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).