- › IF _WIN32 IS DEFINED ON WINDOWS, WHAT IS DEFINED FOR LINUX OR MAC? CODE
- › IF _WIN32 IS DEFINED ON WINDOWS, WHAT IS DEFINED FOR LINUX OR MAC? WINDOWS
But if so, then you may need to perform the same kind of tricks windows.h does with the TCHAR and TEXT macros. For example, do you intend to support both UNICODE and non-UNICODE systems? If not, you can avoid WCHAR and This is a not-trivial task and frequently involves extensive use of preprocessor directives. You will need to figure out a way to insure that the source is compilable on any system which
› IF _WIN32 IS DEFINED ON WINDOWS, WHAT IS DEFINED FOR LINUX OR MAC? WINDOWS
If yes, then deploying any source that makes use of macros defined in windows.h (or any other Windows or VS unique feature) will definitely cause problems. Integers) will cause problems on a deployed system where the assumption is not valid.
› IF _WIN32 IS DEFINED ON WINDOWS, WHAT IS DEFINED FOR LINUX OR MAC? CODE
However, any assumptions you make in the code (such as the endianness of multi-byte
If no, then the resources (such as headers) required to compile the programs are only needed on your development system, not on the system to which you deploy. So which is it? Do you intend to deploy your source code (either. Not only must the library be compatible with the hardware and operating system as above but both must be compatible with the compiler the user will use. The latter is usually delivered as a library and a header file. If the generated machine code is compatible with the hardware and operating system, it runs. The former is usually delivered as an executable and the deployed site will not care what language or compiler was used to build it. There is a significant difference between deploying a utility that some one will execute and deploying a class that others can incorporate into their code. Thoughts please?Įdit again: Including WinNT.h without windows.h does not work. I am thinking that WinNT.h is the furthest down I should go in order to use WCHAR. I do note that just below that typedef for WCHAR there are several more string definitions that will probably be goot to have, such as Will the use of windows.h or WinNT.h cause any problems or add gobs of extra code that is not desired? Question: I am writing a class that is intended to be able to be run in an application that does not have any windows or dialogs. Typedef unsigned short WCHAR // wc, 16-bit UNICODE characterĮdit, oops, that says: #ifndef MAC, so this is it. some Macintosh compilers don't define wchar_t in a convenient location, or define it as a char
Typedef wchar_t WCHAR // wc, 16-bit UNICODE character But it is not define there.īut I did finally find WinNT.h which has: The first place WCHAR was found is in winbase.h. In windows.h each include file was opened one at a time. Somewhere in the chain started by windows.h, is the WCHAR declaration. Not in winuser.rh, or several other files.
Not in winresrc.h which is included in windows.h. Visual Studio 2008, WCHAR is not found in windows.h on my machine. ~jag77 We need to know what a dragon is before we study its anatomy. But it is sometimes so incredibly difficult to find.) Microsoft provides an incredible wealth of information. Why is this so difficult to find? (A rhetorical question. I used Google and Bing and the phrase: visual studio where is WCHAR definedĭescribes WCHAR but does not say where it is declared.ġ. I used the defaults and the project properties shows: Use Unicode Character Set. Note: C++ does not support default-int e:\code\delete_all_files_in_a_directory\delete_all_files_in_a_directory\delete_all_files_in_a_directory.cpp 12 Delete_All_Files_In_A_Directory The compiler says Error 1 error C4430: missing type specifier - int assumed. I created a console app to assist in testing a short utility.
0 kommentar(er)
