That was my point - it doesn't matter how portable we wait for a key to be
pressed. When we develop a console application, we normally don't want to
leave that code in the release - if a user run a console application from
the command line, they don't want to have to press a key to get back the
command line.
As long as it's just for testing, any whatever code that waits is fine.
And as long as the command works on the environment the IDE is running on,
that is portable enough.
/Per W
On Sun, 17 Aug 2003, xRxIxPx wrote:
> At 13:32 8/17/2003 +0200, Per Westermark wrote:
> >Why bother about the most portable single-line solution?
> >
> >When I develop a console app, I want it to behave as a console app, i.e.
> >not require some extra input in the end.
> >
> >I add the system("pause"); command during testing, just to allow the
> >program to be run from the editor. When I stop compiling with debug, I
> >don't want the pause anymore.
> >
> >For a portable solution, the code should try and figu
>
> I think that would be some kind of overkill, because few applications will
> need that feature after development.
> I'd rather prefer that devcpp creates a console, then runs the app, then
> runs pause and then frees the console. This even could be done by calling a
> batch file using comspec command line.
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www23.brinkster.com/noicys/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>
|