All of lore.kernel.org
 help / color / mirror / Atom feed
From: ultraptr@pacbell.net
To: Xen Development List <xen-devel@lists.sourceforge.net>
Cc: xen-changelog@lists.sourceforge.net
Subject: Re: [Xen-changelog] Some functions aren't static and could be (damn C language!).
Date: Tue, 8 Feb 2005 09:15:10 -0800	[thread overview]
Message-ID: <20050208171510.GA14169@dront> (raw)
In-Reply-To: <E1CyXq2-0006Zf-3I@moria.surriel.com>

On Tue, Feb 08, 2005 at 03:43:01PM +0000, BitKeeper Bot wrote:
> ChangeSet 1.1550.1.180, 2005/02/08 15:43:01+00:00, iap10@freefall.cl.cam.ac.uk
> 
> 	Some functions aren't static and could be (damn C language!).
> 	
> 	I tried turning on -Wmissing-prototypes: unfortunately gives warnings
> 	for functions used in asm, which means introducing gratuitous prototypes
> 	for them.  Not sure it's worth it.
> 	
> 	1) keyhandler.c: keypress_softirq() and do_task_queues() can be static.
> 	2) physdev.c: pcidev_dom0_hidden() can be static.
> 	3) resource.c/resource.h: check_region is deprecated (racy): remove.
> 	4) sched_bvt.c: lots of things can be static.
> 	5) pci/compat.c: not required for Xen.
> 	
> 	Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (authored)
> 	Signed-off-by: ian.pratt@cl.cam.ac.uk
> 
> 

gah, that is not C language problem. that's lame.
you forced compiler to check prototypes so do add them. just add prototypes
even in the same .c file if you don't want to pollute your include files.
but if function is used anywhere outside file scope it is proper to describe it
in include file.

or don't use -Wmissing-prototypes.




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

           reply	other threads:[~2005-02-08 17:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <E1CyXq2-0006Zf-3I@moria.surriel.com>]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050208171510.GA14169@dront \
    --to=ultraptr@pacbell.net \
    --cc=xen-changelog@lists.sourceforge.net \
    --cc=xen-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.