• 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.

Archived

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

mickey

pls answer this... A class that has a protected constructor:

11 posts in this topic

a. cannot be used as a base class b. results in read-only objects c. must have a virtual destructor d. none of the above which letter is correct? thanks!
0

Share this post


Link to post
Share on other sites
c or d.

AFAIK there is no rule in the C++ language that says "If Thou Maketh A Class With A Protected Constructor, Thine Destructor Must Be Virtual", but since a class with a protected constructor is most likely an ADT from which you are deriving other useful classes, it is probably a good idea.
0

Share this post


Link to post
Share on other sites
Well it''s a crap question. There is no requirement in the C++ language that a class with a protected constructor should have a virtual destructor, but in 99% of cases it is common sense. (off the top of my head, I can''t think of any cases where it isn''t common sense, can anyone else?)

So the correct answer depends on your teacher. If he is

a) a tosser who learnt C++ from ''Teach Yourself C++ in 21 days'' and is giving you questions directly out of the book, then the answer is probably c.

or

b) a tosser who actually knows and understands the syntax, but wants to ask you a trick question. In this case, the answer is d.

I''d put my money on c, even though technically d is the correct answer.
0

Share this post


Link to post
Share on other sites
There''s nothing wrong with TYSC++I21D - it just has a bad title.

Once there was a time when all people believed in God and the church ruled. This time is called the Dark Ages.
0

Share this post


Link to post
Share on other sites
quote:
Original post by MadKeithV
How about

e) Is used to create Singleton classes.





Surely you would make the constructor private, unless you were planning to derive classes from it.....

....in which case you would probably want a virtual destructor.

0

Share this post


Link to post
Share on other sites
Hahah sandman, yes, indeed!

DEFINATELY any class that is not 100% certain to never be derived should have a virtual destructor. I''ve seen some really nasty bugs with that one, from code that was "tried and true" according to other people. Ick!

People might not remember what you said, or what you did, but they will always remember how you made them feel.
0

Share this post


Link to post
Share on other sites