Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!uw-june!roper
From: roper@june.cs.washington.edu (Michael Roper)
Newsgroups: comp.windows.ms
Subject: Re: game of tetris for MS-WINDOWS
Message-ID: <8748@june.cs.washington.edu>
Date: 18 Jul 89 23:45:15 GMT
References: <30033@ucbvax.BERKELEY.EDU> <8736@june.cs.washington.edu> <3204@rtech.rtech.com>
Distribution: usa
Organization: U of Washington, Computer Science, Seattle
Lines: 19

> Could you expound on this a bit? What is "retail windows?"  Is there
> some special "non-retail" version of the SDK? Or that people who
> don't use the debugging version inevitably write buggy programs?

Retail Windows is what you buy at Egghead.  Debugging Windows is
what you build with retail Windows and the special libraries 
provided with the SDK.

And yes, it is certainly much easier to write poor and/or dangerous 
code if you don't use debugging Windows for development and testing.

I have a question for developers that don't use debugging Windows:
For the RIPs supported by retail Windows, how do you find the problem
with no stack trace?  As far as I'm concerned, the debug support 
offered by debugging Windows is indispensible and I can't imagine
trying to develop code without it.

Michael Roper
hDC Computer Corp.