Re: ambiguous operator on Visual Studio 2010
On Jun 9, 9:51 pm, "Alf P. Steinbach /Usenet" <alf.p.steinbach
+use...@gmail.com> wrote:
* Tiib, on 09.06.2011 13:52:
If there has to be interactive GUI then i somehow prefer Qt to
MS GUI and OpenGL to DirectX. Compiles and works with MSVC. Also
friendly i(something) and Linux addicts are lot happier with my
code. ;)
That sort of misses the point. You still need to ask for GUI subsystem wh=
en you
build that app for Windows. Unless you want a console window popping up..=
..
Yes, i may want it to be there (popping up can be avoided by hiding
it), because without console the cin, cerr and cout go to god knows
where in Windows. Actually I have seen (portable to Linux and Mac)
code that has gone full round:
int main( int argc, char *argv[] ) {
Configuration::Load( argc, argv );
#if defined(_MSC_VER)
BOOL ok = ::AllocConsole();
// ... mess with screen buffers of console
// ... redirect std streams to console
#endif
return Session::run( argc, argv );
}
"Full round" in sense that they had /subsystem:windows and they had
int main() and now what was missing was console. Also the solution to
their issue was not as stupid as it feels. It sort of supports your
point, sort of argues with it and sort of misses it too. ;) The real
reasons behind the mess are in Windows architecture, the MS compiler
team feels to consist of decent specialists.