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: @(#)dig.c 3.5 2005/11/19 */
|
||||
/* SCCS Id: @(#)dig.c 3.5 2006/06/25 */
|
||||
/* Copyright (c) Stichting Mathematisch Centrum, Amsterdam, 1985. */
|
||||
/* NetHack may be freely redistributed. See license for details. */
|
||||
|
||||
@@ -207,7 +207,7 @@ dig_check(madeby, verbose, x, y)
|
||||
}
|
||||
|
||||
STATIC_OVL int
|
||||
dig()
|
||||
dig(VOID_ARGS)
|
||||
{
|
||||
register struct rm *lev;
|
||||
register xchar dpx = context.digging.pos.x, dpy = context.digging.pos.y;
|
||||
|
||||
Reference in New Issue
Block a user