Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!karl From: karl@ficc.ferranti.com (Karl Lehenbauer) Newsgroups: comp.windows.ms.programmer Subject: Re: Open letter to Microsoft re: SDK and C6.0 (long) Message-ID: Date: 29 Nov 90 14:40:05 GMT References: <5880@crash.cts.com> <1990Nov28.125836.10515@watserv1.waterloo.edu> Reply-To: karl@ficc.ferranti.com (Karl Lehenbauer) Organization: Ferranti International Controls Corporation Lines: 21 In article <1990Nov28.125836.10515@watserv1.waterloo.edu> tom@mims-iris.waterloo.edu (Tom Haapanen) writes: >Take a look at tty/wstdio.c in the sample sources --- there is source >right there! It doesn't work right with large model, at least for me, and there are bugs in the scrolling optimization stuff where you can lose lines, but it served as an starting point for making one that works. >There are good reasons for not including standard i/o in >Windows --- and Windows apps shouldn't be doing that kind of thing anyway! Hmm, you can do stdio in DOS windows... Come on, it's very useful for debugging, and there are applications that need to have scrolling text, like terminal programs. Who says every application should have to have a graphical user interface? Maybe for the least sophisticated end-users, but it's nice to be able to quickly port a stdio-style program and not worry about doing a GUI front- end, at least right away (cf. xterm, the Amiga CLI, the amount of time you spend developing running under COMMAND.COM). -- -- uunet!sugar!ficc!karl (wk), "Any excuse will serve a tyrant." -- Aesop uunet!sugar!karl (hm)