member-functions

In c++ is there any way to get the real address of member function, or the index in vTable ? Updated: I don't know the INDEX in vTable and I don't know the address Here's why I want to know this: I want to hook the function ID3DXFont->DrawText of DirectX. If I know the index of the DrawText in the vTable, I can replace it to do the hook. But how to get the index? If it's able to get the the real address, I can search it in the vTable to get the index. And not particularly ID3DXFont->DrawText , maybe some other functions in the future, so I'm trying to write a generic hook function. Here's what

bool SomeClass::Function( bool thankYou = true ) { static bool justAbool = false; // Do something with justAbool; ... } I have searched around but I can't find anything about this except globals vars or member functions itself. What does the above do, i.e. what happens, does justAbool keep its value after leaving the scope? Or does it 'remember' the value when it re-enters the scope? static when applied to a local variable gives that variable static storage duration . This means that the justAbool 's lifetime lasts to the end of the program rather than to the end of the invocation of the

The following C++ code compiles with Visual C++ and g++: struct S { static void foo(); }; extern "C" void S::foo() {} struct T { static void foo(); }; extern "C" void T::foo() {} auto main() -> int { S().foo(); T().foo(); } Is it valid? If it's valid, since the implementation may be in a separate translation unit, does that imply that a static member function always has the same calling convention as a C function (and if not, how does it not imply that)? C++11 7.5/4 "Linkage specifications" A C language linkage is ignored in determining the language linkage of the names of class members and

This compiles fine in clang 3.3: template <typename T> struct M; template <typename R, typename C, typename... A> struct M <R (C::*)(A...)> { }; template <typename R, typename C, typename... A> struct M <R (C::*)(A...) &> { }; but fails in gcc 4.8.1: [...] error: redefinition of ‘struct M <R (C::*)(A ...)>’ struct M <R (C::*)(A...) &> { }; ^ [...] error: previous definition of ‘struct M <R (C::*)(A ...)>’ struct M <R (C::*)(A...)> { }; ^ When used in different contexts, this results in all sorts of unexpected compiler behaviour like crashing or internal compiler errors. I understand ref

This question already has answers here : Closed 4 years ago . Meaning of 'const' last in a function declaration of a class? (9 answers) In C++ sometimes I see declarations like below: return_type function_name( datatype parameter1, datatype parameter2 ) const { /*................*/} What does this const type qualifier exact do in this case? $9.3.1/3 states- "A nonstatic member function may be declared const, volatile, or const volatile. These cvqualifiers affect the type of the this pointer (9.3.2). They also affect the function type (8.3.5) of the member function; a member function declared

I understand that template member functions are only generated if used. This is convenient if not all used types support such a function. However, this does not appear to work for functions with trailing return type specification. Below is a small experiment: // helper function for case A workaround template <typename A, typename T> auto F(T&& x) -> decltype(x.template f <A>()) { return x.template f <A>(); } // helper function for case B workaround template <typename A, typename T> auto G(T&& x) -> decltype(x.g()) { return x.g(); } template <typename T> struct S { // case A: not ok in GCC +

While implementing a class for creating/updating boxes on the screen, I wanted to add a static member function that makes sure no currently visible boxes overlap (taking its information from a static pointer array to all currently visible boxes) My initial code had the following structure: class Box { public: // ... static void arrangeOverlappingBoxes(); }; static void Box::arrangeOverlappingBoxes() { // ... } I was quite surprised that this generated an error C2724: 'static' should not be used on member functions defined at file scope. With some trial, google and error, I figured out that my