• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.


This topic is now archived and is closed to further replies.

PsyCHo puNk

Object Oriented DLL Problem

2 posts in this topic

Hi I made a post about this problem a while back but still haven''t found a solution so I''m here with a much better explaination of whats wrong. I am trying to package a reusable class library in a win32 dll however I have run into a problem, Class B and B2 derive from class A, heres the simplified code: class __declspec( dllexport ) A { public: A(); virtual ~A(); virtual void SomeFunc(void) = 0; }; class __declspec( dllexport ) B : public A { public: B(); virtual ~B(); void SomeFunc(void); }; class __declspec( dllexport ) B2 : public A { public: B2(); virtual ~B2(); void SomeFunc(void); }; A::A() { cout << "A constructor." << endl; } A::~A() { cout << "A destructor." << endl; } B::B() { cout << "B constructor." << endl; } B::~B() { cout << "B destructor." << endl; } void B::SomeFunc(void) { cout << "B::SomeFunc()" << endl; } B2::B2() { cout << "B2 constructor." << endl; } B2::~B2() { cout << "B2 destructor." << endl; } void B2::SomeFunc(void) { cout << "B2::SomeFunc()" << endl; } This compiles into a DLL without any problems. However when I attempt to use it (I have linked to the .lib and put the .dll in the executable directory) using the following code: #include "A.h" #include "B.h" #include "B2.h" int main(void) { A* test = NULL; test = new B(); test->SomeFunc(); delete test; return 0; } I get the output as expected: A constructor. B constructor. B::SomeFunc() B destructor. A destructor. But then a nasty debug assertion failure: Debug Asserion Failed. File: dbgheap.c Expression: _pFirstBlock == pHead Oddly enough, if I comment out delete test; the assertion failure does not occur, but I dont want memory leaks in my programs. I know that converting it too a COM dll and using interfaces would problably be the best solution, however I want to first learn how to create normal dlls before I mess with making them COM compliant.

Share this post

Link to post
Share on other sites
This is a long shot but lets try it any way:
When ever I use:__declspec( dllexport ) to export a class I also use __declspec( dllimport ) to import it. the way to do it is:
in the class definition write something like this:

#ifdef _Win32DLLTrgt
#define EXPORT_FLAG __declspec( dllexport )
#define EXPORT_FLAG __declspec( dllimport )

virtual ~A();

if the project that creates the dll add to the setting -D_Win32DLLTrgt (you can do it is the setting with out the /D option )
Hope this is clear
-- Gilad

Share this post

Link to post
Share on other sites
My best guess is that problem here is that the main application and the dll are using separate heaps. Chances are in your class it is allocating some memory on the dll heap, but attempting to free it on the main application heap, or vice version.

There are two main ways to tackle this:

1) Change the run time library to be Debug Multithreaded DLL and Multithreaded DLL, for debug and release mode respetively.

2) Or, add in a detroy() or deleteThis() to a common base class, which simply calls "delete this;" so it ensures the dll cleans up its memory.

Option 1 would be my best bet, as you wont have to make sure that memory newed in one place is deleted in the same place.

Phillip Martin

Share this post

Link to post
Share on other sites