ITGFanatic wrote: By testing for when an unsigned variable becomes negative, it becomes stuck in an infinite loop. I don't see any other plausible reason for such a simple change to break code. Accessing memory beyond that which was allocated for the string.

strstreambuf ()

Nope, you gotta do it the old fashioned way. Find/Replace. My guess why DevStudio doesn't have this feature is that it may be difficult to do accurately every time. They'd rather avoid the risk of renaming something inappropriately. Regards, Alvaro Well done is better than well said. -- Benjamin Franklin (I actually prefer medium-well.)

There are two basic ways to expose a secondary interface: a) local classes (MFC does that, including some dirty tricks to make this effective) b) multile inheritance (ATL does that) b) is IMO much cleaner, only you can get into problems with method name clashes Some pseudocode for the latter: class CCoImpl : public IFun, public ITest { HRESULT QueryInterface() { if (iid == IUnknown) { // always return the same pointer when specifically asked for IUnk; which one doesn't matter addref, return static_cast(this); } if (iid == IFun) { addref, return static_cast(this); } if (iid == ITest) { addref, return static_cast(this); } return E_NOINTERFACE; } // IFun methods: HRESULT GoShopping() { ... } HRESULT GoRocking() { ... } // ITest Methods HRESULT TestCountShoes(....) { ... } }; you get the idea... Neither way you can expose two dispatch (or dual) interfaces - you can only have obe dispatch-based interface per object. If I could find a souvenir / just to prove the world was here   [sighist]

Cool, it works for me too. Thanks

If you want to guarantee that the base class version will be called, rather than a virtual one from a derived class, you can do the following: class A { protected: virtual int f() { return -1; }; public: void DoFunc() { printf("\nValue: %d",A::f()); }; }; Software Zen: delete this;

You should have a new public (not private or protected) member function in class B, inside which you would call A's DoFunc() function... There are no failures; there are only extended learning opportunities.