🚀 go-pugleaf

> EnumWindows(EnumProc,0);  // this call causes the error
>
> [C++ Error] App.cpp(91): E2034 Cannot convert 'int (__stdcall *)(void 
> *,long)' to 'int (__stdcall *)()'
> [C++ Error] App.cpp(91): E2342 Type mismatch in parameter 'lpEnumFunc' 
> (wanted 'int (__stdcall *)()', got 'int (__stdcall *)(void *,long)')
> ...
> !!What on Earth is going on ??

I think that is due to differences in the Windows header files.

Long ago when MS only supported pre-ANSI standard C compiles did not support 
type checking of calling arguments.  Functions were prototyped without 
calling arguments.  Later they added C++ which requires that ability but it 
broke builds of old, legacy code.  To handle that they added the macro 
STRICT to cause function prototypes to be more strictly interpreted.  Since 
Borland must license the MS header files this facility to support a problem 
from 16 bit Windows continues to this day.

Try putting this on the first line of the source code file:
#define STRICT

.  Ed

> David wrote in message
> news:44954617$1@newsgroups.borland.com...
>
> When I use the same module in one project I get the following errors when 
> I call EnumProc as though it is expecting a different type of function 
> pointer. But in other projects it is OK. If I cast the function pointer 
> too what it thinks it expects then things are OK but I shouldn't have to 
> do this !!What on Earth is going on ??
>
> Thanks in advance
> David
>
> BOOL CALLBACK EnumProc(HWND h, LPARAM lp)
> {
>  ........
> }
>
> EnumWindows(EnumProc,0);  // this call causes the error
>
> [C++ Error] App.cpp(91): E2034 Cannot convert 'int (__stdcall *)(void 
> *,long)' to 'int (__stdcall *)()'
> [C++ Error] App.cpp(91): E2342 Type mismatch in parameter 'lpEnumFunc' 
> (wanted 'int (__stdcall *)()', got 'int (__stdcall *)(void *,long)')