Comments

• MFC .DLL Tutorial

  Posted by Legacy on 05/14/2002 12:00am

  Originally posted by: Olga Pautova

  The articles are great and they were very helpful to me. Thank you for them! I wish we had more articles like that on codeguru for other complex parts of MFC.

  Reply

• Interface Class?

  Posted by Legacy on 04/24/2002 12:00am

  Originally posted by: rad

  "Creating a separate interface class avoids some compiler incompatibility problems and most recompile problems." ...

  What if I have to change the return type in the FunctionA - in CMyClass? In this case, I will have to change the return of the FunctionA in the CMyInterface, right, to be able to propagate the result of calling CMyClass.FunctionA().

  Do I have a compile problem now, since a function - member of CMyInterface - has a different return type?

  thanks
  

  Reply

• Some C++ Dll Page

  Posted by Legacy on 12/27/2001 12:00am

  Originally posted by: Some Guy

  SIMPLY u Guys ROCK !!!!
  
  When Its time to slide gracefully into .NET & C#
  
  I know where to start 
  
  CodeGuru !!!
  

  Reply

• Thank you very much.

  Posted by Legacy on 09/04/2001 12:00am

  Originally posted by: Horace Chan

  This is a clear, easy-to-understand and inspiring article about DLL!

  Reply

• modifying .dlls without recompiling clients

  Posted by Legacy on 07/16/2001 12:00am

  Originally posted by: Jim Buck

  If new data members were added to a class but were added *after* the other members in the .h file (thereby not changing the offset locations of the other members), couldn't you still just recompile the .dll and not recompile the client with the new .lib file and still have everything work a-ok since the client will not be using the newer data members?

  Also, adding functions to an interface class will still keep everything kosher with the virtual tables in the client without recompiling the client?
  

  Reply