home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!nntp1.radiomail.net!cronos!Metaphor.COM!pstevens
- From: pstevens@Metaphor.COM (Paul Stevens)
- Newsgroups: comp.os.os2.programmer
- Subject: Tracking down DLL incompatibilities
- Message-ID: <2494@cronos.metaphor.com>
- Date: 3 Sep 92 20:17:47 GMT
- Sender: news@cronos.metaphor.com
- Reply-To: pstevens@Metaphor.COM (Paul Stevens)
- Organization: m4
- Lines: 26
-
- We are developing a set of applications that make use of several different
- DLL's to share common code. We frequently encounter problems when one of
- the applications or even a DLL itself has not been linked with the most
- current version of one of these DLL's. When this happens the application
- will terminate silently; no error message, just return to the command prompt.
- You are faced with the problem of figuring our which piece out of all of
- these components is out of sync.
-
- We have even found that if you don't link with the right combination of
- the IBM supplied DLL's, dde4mbs[i] and dde4mbm[i] you can get into
- the same situation.
-
- Can someone explain exactly what fails during image activation that causes
- this "silent" failure?
-
- Is there not some way that a developer can get more information about
- what the incompatibility is? Problems of these sort continually cost
- developers significant amounts of time. It's just one more of the things
- that makes almost all the developers here loathe OS/2 as a development
- environment.
-
- +------------------------------------------------------------------------+
-
- Paul Stevens {apple|decwrl}!metaphor!pstevens
- Metaphor Computer Systems pstevens@metaphor.com
- Mountain View, CA
-