[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 384
  • Last Modified:

'.c' vs '.cpp'

I have a program called 'app.c' that opens a dialog box. However when I rename the file to 'app.cpp' I get an error.

The line that gives the error is:
DialogBox ( hinstance, "SelWND", hwnd, WndDialogProc) ;
and the error message is:
error C2664: 'DialogBoxParamA' : cannot convert parameter 4 from 'int (void *,unsigned int,unsigned int,long)' to 'int (__stdcall *)(void)'

Declaration for WndDialogProc is :
BOOL    CALLBACK WndDialogProc (HWND, UINT, WPARAM, LPARAM) ;

Why does this error happen? I wanted to use classes/C++ without using MFC.
0
vsinha
Asked:
vsinha
  • 3
  • 2
  • 2
1 Solution
 
alexoCommented:
Because C++ does not implicitly convert between pointers to different function types while C does.

Your dialog procedure should be declared as:
BOOL CALLBACK WndDialogProc(HWND hwndDlg, UINT uMsg, WPARAM wParam, LPARAM lParam);

And
  #define STRICT
before you
  #include <windows.h>

0
 
vsinhaAuthor Commented:
I was missing the following line:
#define STRICT

why is it needed? what does it mean?
0
 
RONSLOWCommented:
You need to #define STRICT, which means to do strict type checking

It ensures that handle types and function prototypes much match exactly.  With C it helps catch errors, with C++ it makes code compile (as C++ already checks that function pointers match ok)

When STRICT is on, DLGPROC is defined as

typedef BOOL (CALLBACK* DLGPROC)(HWND, UINT, WPARAM, LPARAM);

When it is off it is just

typedef FARPROC DLGPROC;

where FARPROC is just typedef int (FAR WINAPI *FARPROC)();

This won't match with your WndDialogProc function in C++.  This is because in C the () in a function pointer declaration means there could be any args at all, and so arg type checking isn't done.  In C++ arg type checking is always done and () means no args at all - the same as (void).

In general is is a good idea to always use #define STRICT for both C and C++.  But it is almsot ESSENTIAL for C++. (C may compile without it, but C++ won't).

I hope this clears things up for you.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
vsinhaAuthor Commented:
Thank a lot!

btw, what is the advantage of not having #define STRICT ? or, in other words why does it exist, it seems to me that all programs should always use it.
0
 
alexoCommented:
For compatibility with code that was (poorly) ported from Win3.x.
0
 
RONSLOWCommented:
Shame I didn't get offered any points for my lucid explanation .. that's life I guess :-(
0
 
vsinhaAuthor Commented:
Ronslow, check Q.10048982
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now