|
Microsoft simply provides certain extensions to the C++ standard.
These extensions are MS specific and will work only with MS compilers and OSs.
Don't worry about learning one over the other. They're almost the same.
«_Superman_»
I love work. It gives me something to do between weekends.
|
|
|
|
|
They are practically the same for almost all purposes.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Thanks.
Though I noticed in MS C++ you cannot use cin/cout, the syntax for #include is different and strings are also handled differenty.
|
|
|
|
|
Megidolaon wrote:
Though I noticed in MS C++ you cannot use cin/cout,
That's not true.
Megidolaon wrote: the syntax for #include is different and strings are also handled differenty.
That is, as well, not true.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
i think cin/cout can be used in ms c++,once i tried.Maybe you didn't include the right head files.or some thing wrong with the name spaces
|
|
|
|
|
You can certainly use any cin/cout in ms c++, .. u have to include iostream.
kamalesh
|
|
|
|
|
Megidolaon wrote:
Though I noticed in MS C++ you cannot use cin/cout, the syntax for #include is different and strings are also handled differenty.
It's not that. In pre-standard C++, it would be like
#include <iostream.h>
After standardization its,
#include <iostream>
Moreover I can say you forgot to include "using namespace std".
|
|
|
|
|
grassrootkit wrote: Moreover I can say you forgot to include "using namespace std".
yeah, but using prepending std:: is generally prefered (the using namespace command can lead to unresovled names and should be used with care...
|
|
|
|
|
When you say "MS" you are potentially targeting windows. It's totally different from standard C++. Though you get the standard C++ from MS compilers, MS C++ (in your terms) or VC++ (the right term) would mean more eg: Win32APIs, MFC etc all platform oriented. All these libraries/Frameworks make things on top of MS C++ compiler.If you develop apps using plain, Standard C++, you will be able to run it on any OS. Just a recompilation would do.
|
|
|
|
|
you are obviously totally confused.
recent Microsoft C++ Compiler (above version 2003) are significantly closer to the standard C++ than previous ones.
so you can write a totally standard C++ Application (say, under vi or notepad, why not), and compile it with any compiler. gcc would handle it, and VC++ as well.
what makes you becoming non-standard C++ is by using compiler-specific commands, or non-portable libraries (such as Win32, MFC)...
but remember that VC++ only provides extensions to the standard, so anything standard should work with a Visual C++ compiler. If it doesn't, you're probably doing it wrong (show your code about cin/cout/#include)...!
However, as an example, the following is 100% standard C++:
<font color="blue">#include</font> <iostream>
<font color="blue">#include</font> <string>
<font color="blue">void</font> main(<font color="blue">void</font>) {
std::string strName = <font color="gray">""</font>;
<font color="green">
std::cout << <font color="gray">"your name: "</font>;
std::cin >> strName;
<font color="green">
std::cout << <font color="gray">"Hello "</font> << strName << <font color="gray">" !"</font> << endl;
}
modified on Monday, February 23, 2009 8:00 AM
|
|
|
|
|
Thanks.
you are obviously totally confused.
Yes, I was, but now I'm not anymore. 
Almost all online tutorials I found were in standard C++ and never mentioned anything about VC++, so I assumed there'd be sigificant differences.
Thus I never found that you need #include <iostream></iostream> to make it work in VC++, I just tried it out and it works fine.
Without that, I always got an error with using std;.
As for other OS, it should be fine if I don't get too much into the MS specific libraries?
|
|
|
|
|
Megidolaon wrote: Thus I never found that you need #include to make it work in VC++, I just tried it out and it works fine.
Without that, I always got an error with using std;.
becasue you probably used it badly.
can you post a code sample of a "not compiling" code, and the associated error ?
We'll tell you what's wrong then...
Megidolaon wrote: As for other OS, it should be fine if I don't get too much into the MS specific libraries?
As far as you do command line applications, everything will be ok.
unfortunately, as soon as you start a windowed application, you'll have to choose a graphical library, which is most of the time OS-specific...
But you know, it's not a bad choice sometimes to move a little from the standard C++ paths, especially for things that are anyway specifics to the OS.
But for the logical layers, all depends on what systems you target, but I personnally prefer staying standard as much as I can...
|
|
|
|
|
https://forum.codejock.com/forum_posts.asp?TID=6186[^]
i have the same problem like above link.
OnCtlColor not working in property sheet and the background of controls not colred.
here one solution is given but i cant understand this.please explain me with example
and please give me any other solution to solve my problem.
thanks in advance.
To accomplish great things, we must not only act, but also dream;
not only plan, but also believe.
|
|
|
|
|
Didn't you ask this question a couple of days ago, and I suggested looking for the WM_CTLCOLOR message (and its cousins) using Spy++ tool? I don't remember you replying to my suggestion.
Iain.
Codeproject MVP for C++, I can't believe it's for my lounge posts...
|
|
|
|
|
Hi All
How can i get Device ID of Removal Device?PLz help me
|
|
|
|
|
You should be able to get that from the lParam parameter of the WM_DEVICECHANGE message when the wParam parameter is DBT_DEVICEREMOVECOMPLETE.
«_Superman_»
I love work. It gives me something to do between weekends.
|
|
|
|
|
|
how to draw transparent rectangle in MFC
I have tried using following code but it does not work.
int nPrevMode = pDC->SetBkMode(TRANSPARENT);
COLORREF bkcolor = pDC->SetBkColor(BLACK);
pDC->Rectangle(rect1.left, rect1.top, rect1.right, rect1.bottom);
thanks
|
|
|
|
|
Use CDC::FrameRect[^] or use CDC::Rectangle[^] with a NULL_BRUSH[^].
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <
|
|
|
|
|
saksp wrote: does not work.
Define what you expected to happen and what actually happened. I suspect your expectation doesn't match what the documentation promises.
The documentation of SetBkMode says this:
The background mix mode is used with text, hatched brushes, and pen styles that are not solid lines.
Are you using any of those three?
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
|
do you mean you need a frame not filled with any clour?
if so,framerect may help you.
|
|
|
|
|
|
Hello,
I am currently trying to run a vbs-Script the same way I'd run an exe from within my MFC app, so I pass the call to my "test.vbs" to CreateProcess, which unfortunately fails (GetLastError returns code 193). What is a safe way to execute a VBS-Script? If I doubleclick the vbs file in Windows explorer, everything works fine.
|
|
|
|
|
You can use ShellExecute to run the vbs file.
ShellExecute(0, "open", "test.vbs", ...
«_Superman_»
I love work. It gives me something to do between weekends.
|
|
|
|
|
Mr Superman's answer is probably what you want, but if you want or need more control over how your VBScript runs than opening it with ShellExecute (for example, should it have a console window or not?), you could construct a command line to execute it like, using cscript or wscript as the executable and pass your vbs file as a parameter.
For example:
wscript a.vbs would run the VB script without a console window.
cscript a.vbs //X would run the VB script with a console window and attached to a debugger (if there is one).
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
