unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: compilation warnings
Date: Fri, 04 Jul 2003 00:36:26 -0400	[thread overview]
Message-ID: <m3d6gqx5zz.fsf@multivac.cwru.edu> (raw)

If I use the "-Wwrite-strings -Wshadow" options for gcc while
compiling an extension, I get some warnings that I think could be
silenced:

.../smob.h:149: warning: declaration of `free' shadows a global declaration
.../smob.h:170: warning: declaration of `free' shadows a global declaration
.../smob.h:176: warning: declaration of `free' shadows a global declaration
.../ports.h:233: warning: declaration of `free' shadows a global declaration
.../numbers.h:258: warning: declaration of `div' shadows a global declaration
.../libguile-ldap.c:169: warning: passing arg 1 of `scm_make_smob_type' discards qualifiers from pointer target type

Is there some reason why scm_make_smob_type's first argument is char*
instead of char const*?  Should I submit a patch to silence these
warnings?


paul


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


             reply	other threads:[~2003-07-04  4:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-04  4:36 Paul Jarc [this message]
2003-07-27 16:56 ` compilation warnings Marius Vollmer
2003-07-28 22:37   ` Kevin Ryde
2003-09-22 21:58   ` Paul Jarc
2003-09-23  4:22     ` Rob Browning
2003-09-23 16:19       ` Paul Jarc
2003-09-24  6:11         ` Rob Browning
2003-10-07 16:00     ` Marius Vollmer

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=m3d6gqx5zz.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).