actually wats the different between Visual c++ and others C compiler???
is the coding different???
also if im using other compiler, will i be able to use those CFont or Cbitmap classes that is for MFC ??
actually wats the different between Visual c++ and others C compiler???
is the coding different???
also if im using other compiler, will i be able to use those CFont or Cbitmap classes that is for MFC ??
There are several differences. The main difference is that Visual C++ is created by Microsoft and C++-compilers made by others aren't. A difference derived from this fact is that there are Microsoft specific issues build in the Visual C++ compiler. For example the Visual C++ compiler accepts Microsoft specific keywords which will probably not be accepted by other compilers.
MFC is a library, you can use other compilers with MFC. Though I remember that when using Borland C++Builder and MFC, there were some complications because of Microsoft specific issues.
I have a question regarding Visual C++. How do you make it so it does'nt compile source into large .exe's? Do I have to turn debugging of? if so, how? thanks.
no clue. I'm not sure if you can, actually... but don't listen to me, I don't know much
Why do you want to anyways? Are you really that seriously short of HD space?
Just Google It. √
(\ /)
( . .)
c(")(") This is bunny. Copy and paste bunny into your signature to help him gain world domination.
>How do you make it so it does'nt compile source into large .exe's?
When building your project, you usually build the debug version. Which is useful when debugging the applications. When you're sure or think you're sure everything is OK, you can build the release version which is much much smaller.
In Build->Set Active Configuration, you can choose if you want to build the release version or the debug version.
>Why do you want to anyways? Are you really that seriously short of HD space?
If Unregistered considers to distribute the application, it is useful to distribute the small version instead of the large version.
Last edited by Shiro; 05-26-2002 at 01:38 PM.
wats the release version for
is it for other computer to use one ????
On your debug build it adds in a bunch of information for, guess what, debugging. This is useless once you have finished the product (do you ever really, finish?). Anyways, when you have really big projects they can cause massive size differences. Also, in release build the compiler users code optimizations and the code will execute MUCH faster in some cases. Debug build doesn't use any optimizations I don't think.
"...the results are undefined, and we all know what "undefined" means: it means it works during development, it works during testing, and it blows up in your most important customers' faces." --Scott Meyers
Debug contains extra space for well 'debug info'. Also in practice it is easier on memory errors and allows you to use break points without restriction.
Release removes this extra info, links to the release libs and is smaller and faster. But harder to find runtime errors.
ie in debug using more chars than you have allocated a string will cause and exception.
char sBuffer[16]={"opps you should check your strings length"};
In release this will crash the app. This is because in most cases the OOB memory used is just debug info.
"Man alone suffers so excruciatingly in the world that he was compelled to invent laughter."
Friedrich Nietzsche
"I spent a lot of my money on booze, birds and fast cars......the rest I squandered."
George Best
"If you are going through hell....keep going."
Winston Churchill
oic thanks
