Printable View
I have two questions:
1) Does Win32 API use C/C++ standard library or it has it own low level routines?
2) Why should the compiler know the target environment? For example we should clarify "console" or "Win32" by corresponding switches while they both run in Windows platform.
A) There is a windows programming forum.
1) The win32 api is written in C, and therefore follows the rules of C.
2) Because a console program runs in DOS, and a windows program interacts with the windows operating system. A console program and a windows program are drastically different in structure and function. Create one of each and look at the differences. If you want to write a windows program, then you have to play by the rules that MS decided on.
I have written both console and Win32 codes.Quote:
If you want to write a windows program, then you have to play by the rules that MS decided on.
How C/C++ compiler generates different machine code from the same C/C++ source code?
The source code for a console program that displays 'hello world' in a DOS window, and the source code for a windows program that displays 'hello world' in a window are not the same. The windows program is more than 50 lines of source code.Quote:
I have written both console and Win32 codes.
How C/C++ compiler generates different machine code from the same C/C++ source code?
When a win32 console program is run, a console window is created. You don't write the code to display the console window. But For win32 non-console programs, you must create your own windows. You can create a console window if you like, but one is not automatically created.Quote:
2) Why should the compiler know the target environment? For example we should clarify "console" or "Win32" by corresponding switches while they both run in Windows platform.
It was not what I meant. Think you have a 50 lines code for Windows. Once compile it with the _CONSOLE switch and once without it (imagine that it will compile without any linkin' error).Quote:
The source code for a console program that displays 'hello world' in a DOS window, and the source code for a windows program that displays 'hello world' in a window are not the same. The windows program is more than 50 lines of source code.
I know, what I mean is this:Quote:
When a win32 console program is run, a console window is created. You don't write the code to display the console window. But For win32 non-console programs, you must create your own windows. You can create a console window if you like, but one is not automatically created.
There is a C++ code.
There is a C++ compiler.
Then there should be a machine code after compilation.
Why we should use switches to tell the compiler, "This is a Win32 code" or "This is a Win32 console code"?
Do you want it to set up a console window for you or not?
Presumably, so windows knows what to do with the code. As far as I know, that's the way windows was designed, so you have to use the interfaces provided by the designers of the software.Quote:
There is a C++ code.
There is a C++ compiler.
Then there should be a machine code after compilation.
Why we should use switches to tell the compiler, "This is a Win32 code" or "This is a Win32 console code"?
Entry point might be one reason. Should the linker look for main or WinMain?Quote:
Originally Posted by siavoshkc
[edit]Every translator should know into what language to translate.Quote:
Why should the compiler know the target environment?
I thought that main() is the standard entery of all programs in C/C++ language. But it seems that it is not the case in Windows compiler, am I right?Quote:
Entry point might be one reason. Should the linker look for main or WinMain?
Now I make a question that I think it's answer will be the answer of my first question. How can we write a Win32 code, WITHOUT using corresponding switches.
It is not a Windows programming question I think. But it is OK.
I think I solved my problem. This is linker that should know the entery point of program not the compiler and that switches are for linker not the compiler. Thanks for replies, happy to see more.