function pointer assignment warnings in VC2005
The latest Micrsoft compilers complain when a function is
assigned to a function pointer, and the function's argument
list does not match the prototype precisely.
It was evem complaining about the difference between this:
int x()
{
[...]
}
and a prototype of
int x(void);
when assigning that function's address to a function pointer.
This quiets those warnings, without suppressing the mismatch
check altogether for more serious mismatches.
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
/* SCCS Id: @(#)lock.c 3.5 2006/01/02 */
|
||||
/* SCCS Id: @(#)lock.c 3.5 2006/06/25 */
|
||||
/* Copyright (c) Stichting Mathematisch Centrum, Amsterdam, 1985. */
|
||||
/* NetHack may be freely redistributed. See license for details. */
|
||||
|
||||
@@ -72,7 +72,7 @@ lock_action()
|
||||
|
||||
STATIC_PTR
|
||||
int
|
||||
picklock() /* try to open/close a lock */
|
||||
picklock(VOID_ARGS) /* try to open/close a lock */
|
||||
{
|
||||
|
||||
if (xlock.box) {
|
||||
@@ -128,7 +128,7 @@ picklock() /* try to open/close a lock */
|
||||
|
||||
STATIC_PTR
|
||||
int
|
||||
forcelock() /* try to force a locked chest */
|
||||
forcelock(VOID_ARGS) /* try to force a locked chest */
|
||||
{
|
||||
|
||||
register struct obj *otmp;
|
||||
|
||||
Reference in New Issue
Block a user