Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 4083428
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 20, 20262026-05-20T18:18:42+00:00 2026-05-20T18:18:42+00:00

I’m doing maintenance on a C++ 6.0 project that uses a .def file to

  • 0

I’m doing maintenance on a C++ 6.0 project that uses a .def file to handle function exports. I had to add a pair of instance methods to a class definition, but I don’t know how to add these methods to the .def file so they get exported. Each line under the EXPORTS section in the .def file looks something like ?MethodName@ClassName@@AStringOfLetters with maybe a @Z tacked on the end for no reason I can fathom. I’m assuming the string of letters corresponds in some way to the prototype of the method, but I can’t find any documentation that describes the encoding. The methods I added don’t have a prototype that exactly matches any of the existing methods.

Let’s say my new method prototypes look like this:

  short ClassName::Foo1(const short, const unsigned int, const short, const unsigned int *);
  short ClassName::Foo2(const short, const unsigned int, short *, unsigned int *);

What do I need to add to the .def file in order to make my linker happy and actually export the methods?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-20T18:18:42+00:00Added an answer on May 20, 2026 at 6:18 pm

    You are exporting the C++ mangled symbols. I would add a __declspec(dllexport) in front of them temporarily and then load the DLL in something like Dependency Walker, or use dumpbin to see what is exported. This will give you the mangled symbol for you new functions and then you can add that to the .def file and remove the __declspec.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

No related questions found

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.