mycom2andthecolib.docVIP

MyCom2 and the CoLib Component Object Library  Copyright ? Dec 28, 2000 by Ernest Murphy ernie@ For educational use only. All commercial use only by written license. Re-written Dec 28 2000 for the MASM32 package Abstract: -------------------------------------------------------------------------------------------------------------------- A simple COM object is created through a library of reusable functions. The requirements for using this library are discussed. As this is still a work in progress, there will be minimal explanation given for how the lib works. Release version 1.0. IDispatch is fully working. The requirements for using this library will be given. -------------------------------------------------------------------------------------------------------------------- In an earlier article I discussed some code that created the fully functional, albeit very simple COM object MyCom. That may now be used as a guide as to what a server must do. The current project creates MyCom2, which while having an identical set of methods inherits from IDispatch and thus supports a dual interface for either early or late binding. One interesting aspect aspect of this addition is the file sizes. The dll grew from 7168 to 12,288 bytes, a total increase of only 5120 bytes for a significant addition of reusable functionality provided by standard library functions. In writing this library, a simple thought was kept in mind: make it all things to all peoples. Here is a list of the goals of CoLib.lib: By including CoLib.inc and CoLib.lib, not one line of code or byte of data shall be added to a project. Library functions are added by the linker.  Individual library functions may be excluded from use should you wish to customize particular functions without editing the library.  The 5 DLL exports shall be included and reusable.  Multiple objects may be incorporated in a single DLL.  Each object may contain multiple interfaces.  Aggregation is supported.  I