Path: utzoo!attcan!uunet!cs.utexas.edu!texbell!merch!cpe!hal6000!trsvax!reyn
From: reyn@trsvax.UUCP
Newsgroups: comp.windows.ms
Subject: Debuggers and DLLs
Message-ID: <292600020@trsvax>
Date: 29 Jun 90 16:00:00 GMT
Lines: 26
Nf-ID: #N:trsvax:292600020:000:1236
Nf-From: trsvax.UUCP!reyn    Jun 29 10:00:00 1990


For those who have already developed applications for Windows 3.0 ...
   prefereably for those who have also developed a DLL ...

Which debugger do you find the most useful for development ( CodeView,
Turbo Debugger, Periscope, Symdeb, etc. )

I have no experience with Windows, but in the DeskMate environment most
debuggers just didn't cut it when developing DLLs ( DeskMate calls them
resources ).  When debugging the code in the DLL it is necessary to load (
or switch to ) a seperate symbol table from the one which you need to debug
the app itself.  CodeView can't ( I should say couldn't ) do this,
Periscope and Symdeb can.

I am also currious about the availability of the API's for various
MicroSoft DLLs.  For instance, WinWord comes with a nifty spell checker and
thesaurus, both of which appear to be DLLs.  I know it would be improper to
distribute these DLLs, but it should be reasonable for someone who has
bought WinWord to run an application which uses WinWord's DLLs. This goes
for any DLL by the way, not just MicroSoft's.

Forgive me if these topics are covered in the Windows 3.0 SDK, as of yet
they are not available in my area.  Hopefully they'll be here soon.

					   John Reynolds
Standard Disclaimers Apply