Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!sdd.hp.com!apollo!nelson_p From: nelson_p@apollo.HP.COM (Peter Nelson) Newsgroups: comp.windows.ms Subject: Re: Windows programming in C Message-ID: <4b56e7ea.20b6d@apollo.HP.COM> Date: 2 Jul 90 00:43:00 GMT Sender: root@apollo.HP.COM Distribution: usa Organization: Hewlett-Packard Apollo Division - Chelmsford, MA Lines: 42 From: bchin@wam.umd.edu (Weiyuan W. Chin) :>that's all the functionality I NEED. Memory-management issues and :>multi-tasking and resizing the window, and so forth are not things :>the APPLICATION should have to worry about. They should be invisible :>to the application, as much as possible. ( I realize that DOS apps : :If you don't worry about memory or how the window looks when resized, :who will? I assumed that this was handled by the Windows environment. Look, I've been writing 3D graphics software for years for a living and I don't recall ever having to concern myself with resizing or moving windows. If effect, in a modern graphics programming environment (by which I mean anything post - mid 1980's), applications write to *virtual* displays. The app is layered on top of low-level display libraries, invisible to the app, which map the virtual display to the physical one. Now, it's true that modern workstations are much more powerful than typical PC's, but these concepts date back several years when workstations were much *wimpier* than today's PC's. : You don't have to worry about *how* windows moves memory :or where or when it moves it... you've got the handle and so when you :need it just lock the block down. And remember to unlock it. (for :most apps) Since I'm not a Windows programmer, I don't know what "lock" refers to. Why can't I just malloc the memory I need? The Windows environment should "know" when my process is swapped in and ought to be able to make sure that the space I malloc'ed is mapped. What's the big deal? ---Peter