• 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.
Sign in to follow this  
Followers 0
MilchoPenchev

Eight, Nine, Ten...

32 posts in this topic

why someone (sane) would use #define for numbers is beyond me... blink.png

C tradition, mostly.


things like (in the past):
static const int FOO=...;

tending to result in the compilers creating actual variables, and loading the values from them, to access their constants, as well as hindering compile-time expression evaluation, ... (newer compilers have generally at least gotten a little smarter here). (and, if you forgot the 'static', the linker would complain about multiple definitions, ...)

...
0

Share this post


Link to post
Share on other sites

Yeah that thing was always annoying in C. It wont even let you do this:

static const int size=16;
static const int buffer[size];

That const makes it really a constant and not a variable with a constant value is one of those little things you dont even notice until they are not working which C++ added, together with inline functions, function name overloading, new and delete that avoid the manual NULL check, references, ...

Btw., did this start with someone seeing

#define NULL (0)

and then adding

#define ONE (1)
#define TWO (2)
...

?tongue.png

0

Share this post


Link to post
Share on other sites


why someone (sane) would use #define for numbers is beyond me... blink.png

C tradition, mostly.

things like (in the past):
static const int FOO=...;
...
#define FOO _SIZE 42
is one thing, but
#define FOURTY_TWO 42
is a whole different kettle of fish.
0

Share this post


Link to post
Share on other sites

Fun fact: We use octal a lot more than we realize.

From the C/C++ parser’s viewpoint a number beginning with a 0 is octal.

 

What is the most common number that begins with 0?

 

0!

 

Every time you use a 0 in your code it is seen by the compiler as an octal number.

 

And macro’ing names of numbers is just silly.

 

 

L. Spiro

1

Share this post


Link to post
Share on other sites

What is the most common number that begins with 0?



0!

 

I almost questioned why you are using 0! (aka. zero-bang, aka. 0 factorial). :D

0

Share this post


Link to post
Share on other sites


What is the most common number that begins with 0?



0!

 
I almost questioned why you are using 0! (aka. zero-bang, aka. 0 factorial). biggrin.png


but 0!=!0...


random trivia...
not being content with just having NULL, I have a number of other values in the same area:
UNDEFINED //like NULL but not NULL (*3)
BGBDY_TRUE //when you need a boolean TRUE value as a pointer (*3)
BGBDY_FALSE //likewise, but FALSE
AUXNULL //for when you need to express a NULL but NULL and UNDEFINED are already busy (*1)
BGBGC_NULLEND //for when your NULL should really be a 'void' (and a thread has just terminated, *2)
...

*1: AUXNULL==NULL except when AUXNULL!=NULL... yes, sometimes actually useful...
*2: generally to save the cost of keeping around the state to hold a NULL that wont actually be referenced (basically, because you can't "join()" a thread which returns 'void').

*3: UNDEFINED is TRUE for "if()" whereas NULL is FALSE, but sometimes also needed is a FALSE/TRUE that are distinct from NULL/UNDEFINED.


as for naming numbers:
actually, surprisingly, there are people who seem to think this practice is a good idea.

apparently especially off in the land of a certain language unnamed here...
0

Share this post


Link to post
Share on other sites

Could be binary coded decimal... [snip]

 

That sounds so convoluted it requires its own thread. 

Unfortunately that wasn't the case here - this code, according to a colleague who originally fixed it - caused a fatal crash in the software. 

 

BCD was pretty common once, there are even x86 assembler instructions that work with BCD numbers!

But I guess that wasn't what was intended here :)

0

Share this post


Link to post
Share on other sites

When I was around 18 or so I used to hack around the memory of my PSX games with a gameshark (the kind that plugged into the back and allowed memory/debug access - now considered illegal). I remember coming across BCD in some game when I was searching for the address of the HP values or something similar and when I finally realized what was happening I laughed for a solid five minutes at how crazy it seemed. I wish I could remember what game it was.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0