When does code generation occur when using SQLite?

A virtual table in C++ (and its implementation in Android NDK) involves several trade-offs:

• Performance: Slight overhead for each virtual function call due to table lookup and indirect call. This can be noticeable in performance-critical sections.
• Object size: Each object with virtual functions contains a pointer to its virtual table, increasing object size.
• Implementation complexity: Adds a layer of abstraction managed by the compiler and runtime.
• Limited static analysis: The actual function called is determined at runtime via the vtable pointer, limiting compiler optimizations.
• Serialization complexity: Objects with virtual functions require careful handling of type info during serialization.
• Restricted access: No direct access to the vtable in standard C++ for safety and abstraction reasons.
• Not applicable to static functions, constructors, or non-virtual member functions.