Exporting C++ Classes with Virtual Functions Selectively

Question

0.00/5 (No votes)

See more:

I would like to reduce the number of C++ class methods exported from a DLL that show up in the list of exported symbols with mangled names. This is an effort to reduce the size of C++ assemblies. Virtual functions implemented/overriden in a derived class can be accessed from a reference to it's base class. I was wondering if it's possible to selectively export/import all non-virtual constructors and methods, stripping away the virtual methods to reduce the number of exported symbols? So far, I get linker errors when attempting to import such classes. Exporting the entire class exports all virtual methods, thus bloating the assembly. It also exports the vpftable, which doesn't get exported otherwise, but this is the only method that works. I understand providing a factory method can achieve this from a reference to a base class, but those objects are strictly allocated on the heap and forgos stack allocation. Stack allocation us is a must for us because of performance reasons. From what I can tell this is not possible, but I'm hoping someone can shine a light my way and make me happy.

Posted 18-Nov-12 21:51pm

mcrawley

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Eugen Podsypalnikov · Answer 1 · 2012-11-18T22:16:00

Maybe it would be possible to export only some interfaces
(with needed functionality-aggregation(s) by (smart-)pointers) ? :)

C++

// Header to be "exported" :)

class CInsideClass; // public CInsiderBase, public ...
typedef std::auto_ptr<CInsideClass> CSafeInsider;

class (exp_decoration_here) IExpInterface
{
  CSafeInsider m_cInsider;
  
public:
  // Implement the constructor in the CPP-part to allocate the aggregation
  IExpInterface(..);

  // Define access to the desired Insider-functions here
  // ...
};