• 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
  • entries
    3
  • comments
    10
  • views
    3478

Naming Consistancy

Sign in to follow this  
Followers 0
Saint Retro

761 views

Something that has been bugging me is naming conventions. I see a bit of inconsistency in the book I read. Below is what I feel is right but I am aware that there may not be a global standard as such.int score, playerScore.void DoSomething().class Player, PlayerStats.
Objects is the one I'm on the fence about, it's a variable of sorts so this could be done as: Player john = new Player. The problem here is that when it comes to names like that, grammar dictates that I should capitalise a name, and I often do out of habit.
So Player John = new Player reads 'better' to me but breaks the variable convention.
I feel it may be an exception because when I look at say a message box code: MessageBox.Show(""), this has each word upper case which would be broken if I was calling a method for john such as: john.ShowStats();

What I also find odd in my book is that class fields are capitalised but they are just a variableclass Elephant {public int EarSize;public string Name;public void WhoAmI() {MessageBox.Show("My ears are " + EarSize + " inches tall.",Name + " says...");}}
I need to choose something and stick to it, I'm just wondering what others use. I suppose for what I'm doing it doesn't matter too much as only I'll ever be working on my projects but it's good practice to use something that most others do.
.

0
Sign in to follow this  
Followers 0


7 Comments


I wouldn't say there is a "global standard" but most languages and shops use camal casing with the exception being .Net which uses what you are describing (upper casing the first letter of each word...not even sure what this is called).

 

In the end, it really doesn't matter as long as you are consistent with your naming. Basically though, things starting with upper case letters are classes (models, services etc), so it is easy to identify if you are dealing with a class or a static class.

1

Share this comment


Link to comment

For me it heavily depends on the language.
 
For C++ and C# I do as you describe:

int score
void DoSomething()
class Player

That would be the standard convention for C# anyway.

In C# all public members start with a capital letter (Pascal case), which explains your Elephant class. Had those variables been private then they would start with a lower-case letter (Camel case).

1

Share this comment


Link to comment

Thank you both for your replies.  I suppose the book is correct then, it just didn't explain why it was using this convention.

0

Share this comment


Link to comment

I've come to prefer camel case for functions, methods and variables.

 

looksLikeThis()

 

And initial capitals for type names. You are quite correct that there is no "right" way. It's good to be consistent in a single code base.

 

I jump between different conventions between work and home without too much trouble.

1

Share this comment


Link to comment

For MessageBox.Show, isn't that a static function?  So it's using the <classname>.<functionname> syntax, which goes with the capital for classes, lowercase for instances.

 

And yeah, consistency is good, spellcheck is also good.  

1

Share this comment


Link to comment

(upper casing the first letter of each word...not even sure what this is called).

 

PascalCase?

1

Share this comment


Link to comment

For MessageBox.Show, isn't that a static function?  So it's using the <classname>.<functionname> syntax, which goes with the capital for classes, lowercase for instances.

 

And yeah, consistency is good, spellcheck is also good.  

 

 

Yes you are spot on there, I didn't realize that when I wrote the post smile.png

1

Share this comment


Link to comment

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