Where did my console output go?

[jacob navia]

Yes, of course.
But (unsurprisingly) when you begin your programme with the GUI entry
points, you get a GUI application with no console. The trick is... wait
for it... to use Standard C...

It is not an entry point stuff. You can write a full GUI application
starting with main() and NOT WinMain, as it was under windows 16 bits.

It is a flag in the executable that tells windows if it should open a
console or not. But even if you compile a console application you
have all the windows API available to you anyway.

 

[CBFalconer]

Is there not a way do get the same effect without using non-
portable constructs? I don't use Windows so I am often amazed at
what people say is needed to get X to work or Y to do the "usual"
thing, but is it really that odd a system? Is there no way to
run a standard C program that reads stdin and writes stdout in a
usable way?



Personally, no. If it means that standard C is not a usable
option for such simple programs, then I think the warning is
topical. Alternatives are not hard to come by if you are a
beginner learning C.

Actually, there is no need to use these off-topic actions. By
executing 'command' or 'cmd' (depending on Windows system) you have
a CL system available to you, and you simply run your program in
it. You can have several such CL windows available if you wish. I
simply launch that window at boot-up, and it is there for use as I
wish. It takes very few resources.