l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2006 Jun 02 13:00

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] gcc and quieting warnings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] gcc and quieting warnings

On Fri, Jun 02, 2006 at 11:53:43AM -0400, Peter Jay Salzman wrote:
> I always use -W -Wall when I compile code.  However, sometimes, I want gcc
> to ignore certain instances of a warning.  For example, in something like a
> stub function, or a signal callback, or even an API function that doesn't
> use all the parameters, like:
>    Java_HelloWorld_print( JNIEnv *env, jobject obj )

It may be sufficient to simply not NAME the variables, e.g.:

  Java_HelloWorld_print(JNIEnv*, jobject)

> gcc of course complains about unused parameters.  Of course, I *could*
> simply not use -W -Wall, but I don't want to NOT use -W -Wall just
> because I haven't gotten around to finishing a stub function.  Besides,
> active development is the best time to turn on compiler warnings.

The other alternative is to actually use the variables, but it's kind of
klugey.  Like:

  obj = obj;  /* NUL OP ;) */

Good luck!

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.