Should Equality be commutative within a Class Hierachy?
It is easy to define the Equals operation in ways that are not commutative. When providing equality against other types, there are obviously situations (in most languages) were equality not being commutative is unavoidable. However, within one’s own inheritance hierarchy where the root base class defines an equality member, a programmer has more control.
Why should one use a single-use temporary variable?
Let’s say we have a class called ‘Automobile’ and we have an instance of that class called ‘myCar’. I would like to ask why do we need to put the values that our methods return in a variable? Why don’t we just call the method?
Naming conventions for newtype deconstructors (destructors?)
Looking into Haskell’s standard library we can see:
Where to find common database abbreviations in Spanish [closed]
Closed 9 years ago.
Long lines of text in source code [duplicate]
Possible Duplicate:
Is the 80 character limit still relevant in times of widescreen monitors?
Established coding standards for pl/pgsql code
I need to standardize coding practices for project that compromises, among others, of pl/pgsql database, that has some amount of nontrivial code.
Vocabulary: Should I call this apply or map? [closed]
Closed 9 years ago.
Are there well-known PowerShell coding conventions?
Are there any well-defined conventions when programming in PowerShell?
Should comments say WHY the program is doing what it is doing? (opinion on a dictum by the inventor of Forth) [duplicate]
Use comments sparingly! (I bet that’s welcome.) Remember that program
you looked through – the one with all the comments? How helpful were
all those comments? How soon did you quit reading them? Programs are
self-documenting, even assembler programs, with a modicum of help from
mnemonics. It does no good to say:
What package name to choose for a small, open-source Java project? [closed]
Closed 8 years ago.