migration from Visual studio 6
-
Then blame the one who has written the code. What you need is
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.
-
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 ?
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.
-
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.
below given code in file 'some.c' --------------------------------
#ifdef __STDC__
static int fun1 ( struct1_inlistfile membervar1, void_pointerinlist_file membervar2 )
#elsestatic 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.
-
below given code in file 'some.c' --------------------------------
#ifdef __STDC__
static int fun1 ( struct1_inlistfile membervar1, void_pointerinlist_file membervar2 )
#elsestatic 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.
So you did not get the warning when removing the
__STDC__stuff? Then its should be OK. To resolve the error check the declaration ofsearch_functionand the correspondingRECORDstructinlistheaderstructure member (structure definition in some header file). -
So you did not get the warning when removing the
__STDC__stuff? Then its should be OK. To resolve the error check the declaration ofsearch_functionand the correspondingRECORDstructinlistheaderstructure member (structure definition in some header file).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 ?
typedef int (*p)(void *, void *);
typedef void *P;
typedef void* P;
typedef void* (*p)();
-
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 ?
typedef int (*p)(void *, void *);
typedef void *P;
typedef void* P;
typedef void* (*p)();
Swap9 wrote:
right no warnings when removing __STDC__ stuff.
Then don't care about it.
// 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)(); -
Swap9 wrote:
right no warnings when removing __STDC__ stuff.
Then don't care about it.
// 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)(); -
So you did not get the warning when removing the
__STDC__stuff? Then its should be OK. To resolve the error check the declaration ofsearch_functionand the correspondingRECORDstructinlistheaderstructure member (structure definition in some header file). -
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 ?
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). -
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).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[^]
-
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[^]
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.
-
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.