Ah, I see. You're just changing the visibility of the classes. The vtable layout doesn't change (I misread the code -- sorry!).
Mike [EMAIL PROTECTED] wrote: > > Now, who said they were incompatible?? All we're doing is exposing some > additional symbols to allow debugging. This are just declarations, no > executable code, no change in object layouts, vtables, inlines, etc. We > just need to get this stuff seen by the modules that use DOMString.hpp so > the debugger can calculate the correct offset to the underlying character > array. I challenge anyone to demonstrate incompatibility, or even give a > convincing hand-waving argument. > > I think the greater danger is having a DOM (and therefore a Xalan/C++) that > can't be debugged. > > -Rob > > Mike Pogue wrote: > > >Ooooh. A Debug build that's binary incompatible with the Release > >version of the same build. This sounds like a dangerous idea to me. > >Alarm bells are going off in my head (or maybe I forgot to take my > >Prozac today? :-)
