On sábado, 24 de agosto de 2013 20:46:31, Guido Seifert wrote: > > > #define private public > > > #include "Foo.h" > > > > Doesn't work with MSVC, since the protection level is encoded in the > > member > > function's name. > > This is interesting. How can this not work? This #define trick is a > preprocessor thing. The compiler never sees a 'private' So how can it know > that a function is in 'reality' private and encode it in the name?
You've exactly described the problem. If it won't encode the "private" in the name, how will it find the function in the library? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
