C / C++ / MFC

28-Jul-14 3:30

While migrating VC++ code from VS6 (1998) to VS5(later year) I had to remove __STDC__ from project properties-Predecessors. It fix lot of 'tagVariant' related errors.
if i have __STDC__ in project properties - preprpcessors
I get this
xyz.cpp

c:\program files (x86)\microsoft visual studio 8\vc\atlmfc\include\atlcomcli.h(443) : error C2039: 'vt' : is not a member of 'tagVARIANT'
c:\program files (x86)\microsoft visual studio 8\vc\platformsdk\include\oaidl.h(424) : see declaration of 'tagVARIANT'
c:\program files (x86)\microsoft visual studio 8\vc\atlmfc\include\atlcomcli.h(443) : error C2039: 'vt' : is not a member of 'tagVARIANT'
Next what happened is function definitions were not recognized in many of the project file. so I added #define

C++

__STDC__

in problem files which also took care of many unrecognized function definition related errors.

Now the project is left with only one error in compiling one file which says "Fetal error (1017) invalid integer constant expression in ctype.h" and the code its pointing to line number 362 in ctype.h #define !__STDC__ etc Any ideas - suggestions ? Pls help

I tried to - Remove any #define __STDC__ that I added locally. Also remove __STDC__ from Preprocessor definitions if you haven't done so already. Selected all the .c files in the solution explorer and select properties in the solution explorer context menu. In the properties dialog select /Za for C/C++\Language\Disable Language Extensions property.

Which took me back to -> error C2065: ‘xyz’: undeclared identifier : error C2182: ‘pqr’ : illegal use of type 'void' : error C2065: ‘some variable’ : undeclared identifier : error C2146: syntax error : missing ';' before identifier ‘classname’ : error C2143: syntax error : missing ';' before '*' : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int : error C2040: ‘variable2’ : 'int *' differs in levels of indirection from ''unknown-type'' . . .

Reference : http://social.msdn.microsoft.com/Forums/en-US/e68b0af5-ed25-4953-80e7-e88463149b77/fatal-error-1017-invalid-integer-constant-expression-in-ctypeh-during-migration-from-vs6-to-vs5?forum=vcgeneral

modified 28-Jul-14 9:44am.

Jochen Arndt28-Jul-14 4:03

28-Jul-14 4:03

__STDC__ is defined by the Microsoft compiler when compiling C files with the /Za option. It is never defined when compiling C++ files. You should not define it somewhere in your code or as project global definition, or edit any system header files.

If you have a mixed setup of C and C++ files, you can try to rename the C files to *.cpp to force compilation as C++.

Finally you have to fix all errors in your source code by inspecting them and take the appropiate actions.

Swap928-Jul-14 4:34

28-Jul-14 4:34

I get that - __STDC__ should be there only with .C files.
my application also uses cygwin. I think this C files files were there because of cygwin.
forcing .C files as .CPP will it not cause any problem when application makes use of cygwin ?
Is it okey if in the .C file property i give an option 'Compile as C++ file' ?

Well just an update - It did not work. It gave me tons of syntax errors in my .c/.cpp files.

modified 28-Jul-14 10:59am.

Jochen Arndt28-Jul-14 4:58

28-Jul-14 4:58

In most cases there is no problem when compiling C with the C++ compiler. However, there may be errors or warnings when some C specific syntax is not supported by C++. If the C files contain no C++ code you may let them still compiled as C.

Using Cygwin is just like using any other C library. An example is the standard C library which functions are commonly called from C++ (e.g. all the strXXX functions).

Swap928-Jul-14 5:03

28-Jul-14 5:03

Jochen - thanks for discussing, this is driving me crazy. Shall I try compiling .CPP file as .C files once ?

Jochen Arndt28-Jul-14 5:11

28-Jul-14 5:11

Member 10403830 wrote:
You mean I should try compiling .CPP file as .C files once ?

No.
That won't work. Just compile them first as they are (the MS compilers uses the file extension to select the compiler). If you have problems with C files, try to compile them as C++.

The errors from the C++ files must be solved by you to make the new MS compilers happy. If you get stuck with a specific error, ask here again showing the full error message, the code around the indicated line number, and the definitions of user defined types (e.g. structs and typedefs) if necessary.

Note that the errors may be also located in lines before the indicated one. Therefore always have also a look at the previous lines (especially the one before).

Swap928-Jul-14 11:25

28-Jul-14 11:25

Jochen, If you have a moment can you please have a look at this thread at msdn :
http://social.msdn.microsoft.com/Forums/en-US/e68b0af5-ed25-4953-80e7-e88463149b77/fatal-error-1017-invalid-integer-constant-expression-in-ctypeh-during-migration-from-vs6-to-vs5?forum=vcgeneral[^]

I tried that.Error from .cpp files are in thousands...they are of type
: error C2065: ‘xyz’: undeclared identifier
: error C2182: ‘pqr’ : illegal use of type 'void'
: error C2065: ‘some variable’ : undeclared identifier
: error C2146: syntax error : missing ';' before identifier ‘classname’
: error C2143: syntax error : missing ';' before '*'
: error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
: error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
: error C2040: ‘variable2’ : 'int *' differs in levels of indirection from ''unknown-type''

Removing them is manually one by one is the only way ? I am jsut trying to compile the code from visual studio 6 to visual studio 2006.

Jochen Arndt28-Jul-14 21:16

28-Jul-14 21:16

Don't panic.
Most of the errors are sourced by previous ones. If you resolve one many other will vanish. So start always with the very first error for a source file and try to locate the reason. After fixing some errors you may discover that other errors are similar to the already fixed ones. So the work is not as much as expected at first glance.

If you don't get an error fixed post the relevant information here as said above.

Swap929-Jul-14 3:36

29-Jul-14 3:36

Jochen - to start with small fix at a time i took one .cpp file which has few errors. I removed __STDC__ as you said it should never be used with .CPP file. Without __STDC__ I got this error : cpp(53) : error C3646: 'DWORD' : unknown override specifier
xyz.cpp(53) : error C2143: syntax error : missing ';' before '__stdcall'
xyzcpp(53) : error C2065: 'somevariable' : undeclared identifier
xyz.cpp(54) : warning C4229: anachronism used : modifiers on data are ignored
xyz.cpp(54) : error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
xyz.cpp(54) : error C2365: 'abc_process' : redefinition; previous definition was 'function'
xyz.cpp(54) : error C2146: syntax error : missing ';' before identifier 'LPVOID'
.
.
These errors i tried to remove by adding relevant header files : #include <stdlib.h>,#include <windows.h>,#include <stdlib.h> None of them seems to have any effect on the Output , also tried to refer to these header files with the help of setting the path variable. will you please suggest if it needs any other settings or any other work around.

Jochen Arndt29-Jul-14 4:01

29-Jul-14 4:01

As already mentioned: Focus on the very first error and ignore all others.

The first three errors are in line number 53 of the file xyz.cpp. So you should show us the content of that line and the previous line(s) (at least the line before containing code skipping empty and comment only lines) together with the real error messages (or is 'somevariable' really used there?).

To solve the error it may be also helpful to show us the declarations of any functions and types used in that lines that are not in the Windows header files (those decalred in your own or third party header files).

Swap929-Jul-14 4:26

29-Jul-14 4:26

It points to this code in XYZ.cpp :

#ifdef __STDC__
DWORD WINAPI process( LPVOID Var1)
#else
DWORD WINAPI process( Var1)
LPVOID Var1;
#endif

Jochen Arndt29-Jul-14 4:44

Hi Jochen, Need help again

29-Jul-14 4:44

Then blame the one who has written the code. What you need is

C++

DWORD WINAPI process( LPVOID Var1)

That is valid C++ and C (including ANSI C). The second block is old style K&R C which is not used anymore since about 30 years.

If such conditions are used all over your source files, you must remove the conditions and the second block.

Swap931-Jul-14 23:14

31-Jul-14 23:14

how can i get rid of lot of the below mentioned warnings :
warning C4113: 'int (__cdecl *)()' differs in parameter lists from 'VAR1' ?
Are they serious ?

Jochen Arndt31-Jul-14 23:35

31-Jul-14 23:35

To get rid of the warning ensure that the parameter lists of the functions agree.

If this is serious depends on the assignment. It is just a warning and the code will be compiled. But your application may crash when passing incompatible parameters.

You should show the assignment and the definitions.

Swap91-Aug-14 0:46

1-Aug-14 0:46

below given code in file 'some.c'
--------------------------------

C++

#ifdef __STDC__
  static int fun1 ( struct1_inlistfile membervar1,  void_pointerinlist_file membervar2 )
#else

  static int fun1 (membervar1,  membervar2)

  struct1_inlistfile       membervar1;  
  void_pointerinlist_file  membervar2;

#endif

if the code is as above - I get this warning C4113: 'int (__cdecl *)()' differs in parameter lists from 'RECORDstructinlistheader' file
if i comment the above code like you showed the other day the warning goes away.

.h file has record defination in the form off struct.

the 'some.c' file has another list class defination

static RECORDstructinlistheader Listclass = {

sizeof(RECORD),
sizeof(element in record),
add function ,
search function, /*This is the line where warning is pointed to */
pointer set,
.
.
.

I am afraid I am confusing, but I am giving much details to understand it correctly.
pls help.

Jochen Arndt1-Aug-14 1:12

1-Aug-14 1:12

So you did not get the warning when removing the __STDC__ stuff?
Then its should be OK.

To resolve the error check the declaration of search_function and the corresponding RECORDstructinlistheader structure member (structure definition in some header file).

Swap91-Aug-14 2:46

1-Aug-14 2:46

right no warnings when removing __STDC__ stuff.

I am trying to resolve where is that disagreement happening - but I am confused looking what is the meaning of these four statement ?

C++

typedef int   (*p)(void *, void *);

typedef void *P;                         

typedef void* P; 

typedef void* (*p)();

Jochen Arndt1-Aug-14 3:00

1-Aug-14 3:00

Swap9 wrote:
right no warnings when removing __STDC__ stuff.

Then don't care about it.

C++

// A pointer to a function returning an int and accepting to parameters of type void*
typedef int   (*p)(void *, void *);
// Use it this way:
//  int some_func(void *p1, void *p2);
//  p my_func = some_func;
// Then you can call the function
//  int nRet = my_func(param1, param2);

// A pointer to an unspecified object
typedef void *P;

// A pointer to a function returning void*
typedef void* (*p)();
// With the preceeding typedef it can be also written as
typedef P (*p)();

Swap91-Aug-14 3:14

1-Aug-14 3:14

Thank you so much !

Swap91-Aug-14 3:34

1-Aug-14 3:34

I also have another issue - posted at
http://www.codeproject.com/Messages/4873177/How-can-I-display-Japanese-characters-in-an-applic.aspx[^]

Will be able to help please ?

Jochen Arndt1-Aug-14 3:49

1-Aug-14 3:49

I saw that post but thought it was (partially) solved. When the application uses Japanese Multi Byte characters, support for this characters must be installed in Windows.

The best approach would be converting the application to Unicode. But that might be a lot of work (all char and string literals must be manually rewritten by enclosing them using the _T() macro and the resource strings must be also updated).

Swap91-Aug-14 4:37

1-Aug-14 4:37

Ok thats another approach - but if its easy I can do it. Will you be able to show me a simple example of it ? can I compile and execute it in Japanese just by adding _T() on the Japanese windows ?

I had another expert suggesting me this option, but that looked like another proj on its own
http://social.msdn.microsoft.com/Forums/vstudio/en-US/d3b75db1-3646-4591-84c5-924cd5ec3065/how-to-change-the-application-to-display-gui-screens-captions-etc-in-both-the-languages-japanese?forum=vcgeneral#a4ff216a-fd6c-419f-a8a5-81b40b08e4b8[^]

Jochen Arndt3-Aug-14 21:17

3-Aug-14 21:17

I'm sorry but I can't really help you with the language issues due to lack of experience with multi byte projects. Your link seems to describe the problem.

Porting an appplication to Unicode is a lot of work (more than I told you before; I forget to mention additional tasks). If you decide to port your application take special care when reading and writing text file. You may want to let those still use ANSI rather than Unicode.

Swap93-Aug-14 22:11