What is your system for avoiding keyword naming clashes?

Question

Typically languages have keywords that you are unable to use directly with the exact same spelling and case for naming things (variables,functions,classes ...) in your program. Yet sometimes a keyword is the only natural choice for naming something. What is your system for avoiding/getting around this clash in your chosen technology?

Answer 1

I just avoid the name, usually. Either find a different name or change it slightly - e.g. clazz instead of class in C# or Java. In C# you can use the @ prefix, but it's horrible:

int @int = 5; // Ick!

Answer 2

My system is don't use keywords period!

If I have a function/variable/class and it only seems logical to name it with a keyword, I'll use a descriptive word in front of the keyword.

(adjectiveNoun) format. ie: personName instead of Name where "Name" is a keyword.

Answer 3

My system in Java is to capitalize the second letter of the word, so for example:

 int dEfault;
 boolean tRansient;
 Class cLass;

Answer 4

As stated before either change class to clazz in Java/C#, or use some underscore as a prefix, for example

int _int = 0;

Answer 5

I just use a more descriptive name. For instance, 'id' becomes identifier, 'string' becomes 'descriptionString,' and so on.

Answer 6

In Python I usually use proper namespacing on my modules to avoid name clashes.

import re
re.compile()

instead of:

from re import *
compile()

Sometimes, when I can't avoid keyword name clashes I simply drop the last letter off the name of my variable.

for fil in files:
    pass

Answer 7

There should be no reason to use keywords as variable names. Either use a more detailed word or use a thesaraus. Capitalizing certain letters of the word to make it not exactly like the keyword is not going to help much to someone inheriting your code later.

Answer 8

There is nothing intrinsically all-encompassing about a keyword, in that it should stop you from being able to name your variables. Since all names are just generalized instances of some type to one degree or another, you can always go up or down in the abstraction to find another useful name.

For example, if your writing a system that tracks students and you want an object to represent their study in a specific field, i.e. they've taken a "class" in something, if you can't use the term directly, or the plural "classes", or an alternative like "studies", you might find a more "instanced" variation: studentClass, currentClass, etc. or a higher perspective: "courses", "courseClass" or a specfic type attribute: dailyClass, nightClass, etc.

Lots of options, you should just prefer the simplest and most obvious one, that's all.

I always like to listen to the users talk, because the scope of their language helps define the scope of the problem, often if you listen long enough you'll find they have many multiple terms for the same underlying things (with only subtle differences). They usually have the answer ...

Paul.

Answer 9

Happy those with a language without ANY keywords...

But joke apart, I think in the seldom situations where "Yet sometimes a keyword is the only natural choice for naming something." you can get along by prefixing it with "my", "do", "_" or similar.

I honestly can't really think of many such instances where the keyword alone makes a good name ("int", "for" and "if" are definitely bad anyway). The only few in the C-language family which might make sense are "continue" (make it "doContinue"), "break" (how about "breakWhenEOFIsreached" or similar ?) and the already mentioned "class" (how about "classOfThingy" ?).

In other words: make the names more reasonable. And always remember: code is WRITTEN only once, but usualy READ very often.

Answer 10

Typically I follow Hungarian Notation. So if, for whatever reason, I wanted to use 'End' as a variable of type integer I would declare it as 'iEnd'. A string would be 'strEnd', etc. This usually gives me some room as far as variables go.

If I'm working on a particular personal project that other people will only ever look at to see what I did, for example, when making an add-on to a game using the UnrealEngine, I might use my initials somewhere in the name. 'DS_iEnd' perhaps.

Answer 11

I write my own [vim] syntax highlighters for each language, and I give all keywords an obvious colour so that I notice them when I'm coding. Languages like PHP and Perl use $ for variables, making it a non-issue.

Answer 12

Developing in Ruby on Rails I sometime look up this list of reserved words.

Answer 13

In 15 years of programming, I've rarely had this problem.

One place I can immediately think of, is perhaps a css class, and in that case, I'd use a more descriptive name. So instead of 'class', I might use 'targetClass' or something similar.

Answer 14

In python the generally accepted method is to append an '_'

class -> class_
or -> or_
and -> and_

you can see this exemplified in the operator module.

Answer 15

I switched to a language which doesn't restrict identifier names at all.