unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Bruce Korb" <bkorb@gnu.org>
Subject: Re: Unnecessary warnings
Date: Mon, 25 Sep 2006 07:43:50 -0700	[thread overview]
Message-ID: <668c430c0609250743y6a5249caqae229d91f6c29ccb@mail.gmail.com> (raw)
In-Reply-To: <87mz8o2w9x.fsf@laas.fr>

On 9/25/06, Ludovic Courtès <ludovic.courtes@laas.fr> wrote:
> Hi,
>
> Bruce Korb <bkorb@gnu.org> writes:
>
> > /usr/local/gnu/include/libguile/smob.h:149: warning: declaration of 'free' shadows a global declaration
> > /usr/local/gnu/include/libguile/filesys.h:75: warning: declaration of 'dirname' shadows a global declaration
> > /usr/local/gnu/include/libguile/ports.h:233: warning: declaration of 'write' shadows a global declaration
> > /usr/local/gnu/include/libguile/ports.h:254: warning: declaration of 'truncate' shadows a global declaration
> > /usr/local/gnu/include/libguile/numbers.h:258: warning: declaration of 'div' shadows a global declaration
> > /usr/local/gnu/include/libguile/stime.h:55: warning: declaration of 'time' shadows a global declaration
> > /usr/include/iso/time_iso.h:91: warning: shadowed declaration is here
> > /usr/local/gnu/include/libguile/stime.h:56: warning: declaration of 'time' shadows a global declaration
> > /usr/include/iso/time_iso.h:91: warning: shadowed declaration is here
> > /usr/local/gnu/include/libguile/stime.h:60: warning: declaration of 'stime' shadows a global declaration
> >
> > These are all due to argument names in prototype declarations.
>
> What compiler issues those messages?  To me, it looks like the compiler
> is kind of broken, because there's no reason (AFAIK) there can be name
> clashes between argument names and global declarations.

GCC on Solaris.  I agree that it is just a documentation name and serves
no other purpose, but there it is.  I do like -Wshadow, but it is not so useful
if cluttered up with these spurious messages.  As for the "function is not
a prototype" messages, having a typedef for the particular procedure profile
being passed around allows for better profile matching in the calling code
anyway.  It also cleans up the appearance of your prototype.

Thanks! - Bruce


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


  reply	other threads:[~2006-09-25 14:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-24 15:42 Unnecessary warnings Bruce Korb
2006-09-25  8:19 ` Ludovic Courtès
2006-09-25 14:43   ` Bruce Korb [this message]
2006-09-25 14:53     ` Ludovic Courtès
2006-09-25 14:59       ` Bruce Korb
2006-09-25 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=668c430c0609250743y6a5249caqae229d91f6c29ccb@mail.gmail.com \
    --to=bkorb@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).