Object-Oriented Coding – A Class Named Class?

coding-stylenamingobject-oriented

This is more of a style question, but it is something I am currently pondering for a project of mine.

Assume that you're creating an application which is modeling a school. So there are entities like Student, School, etc. Now this is all fine and intuitive until you get down to Class, as (in most languages) Class is a reserved word. So, given that Class is a reserved keyword, what would you call such an entity that models a school class?

Best Answer

I'd pick another term because the word Class can be ambiguous.

Does class refer to:

The group of students taking a course?
The whole course for this semester?
The abstract course taught in multiple semesters?
The group of students expected to graduate at a specific time?
Some other classification of students, i.e. Advanced Class, Special Needs class.
A specific lecture

And that's without even leaving the academic realm. Chances are you can find a better word to fit whatever you are trying to model. Class will only lead to some confusion.

Related Solutions

Java – Is throwing an exception an anti-pattern here

Yes, your colleague is right: that is bad code. If an error can be handled locally, then it should be handled immediately. An exception should not be thrown and then handled immediately.

This is much cleaner then your version (the getValueByKey() method is removed) :

public String getByKey(String key) {
    if (valuesFromDatabase.containsKey(key)) {
        return valuesFromDatabase.get(key);
    } else {
        String defaultValue = defaultValues.get(key);
        valuesFromDatabase.put(key, defaultvalue);
        return defaultValue;
    }
}

An exception should be thrown only if you do not know how to resolve the error locally.

OpenGL – Abstraction of VAOs, VBOs, and Models

I've had bad experiences with too much abstracted rendering in the past. OpenGL is still very procedural at it's core, and the whole state management is very difficult to debug and extend if you apply a nice modern OO filter and make lots of small objects.

In addition, writing optimized rendering code often forces you to take a global view because the different steps to render a frame and even just the content management/preloading don't map nicely to the approaches used in other parts of an engine.

Therefore, I would separate the functionalities into layers as well as possible, so you can live in a 'looser' OO world with longer methods that deal with OpenGL state, and a nice clean world where you can work in a more abstracted, nice OO context. There's an link to DDD here, with seperate domains designed according to the needs of the domain.

Best Answer

Related Solutions

Java – Is throwing an exception an anti-pattern here

OpenGL – Abstraction of VAOs, VBOs, and Models

Related Topic