Hacker News new | comments | show | ask | jobs | submit login

No, because error variables have extremely limited scope and the length of a variable name should be proportional to its scope.



Heh, I always use longer name variables for broader scope somewhat naturally, but only after reading your comment realized that.


    if theErrorReturnedByThePreviousFunction != nil {
         panic(theErrorReturnedByThePreviousFunction)
    }


A real brogrammer can write COBOL in any language.


From which it follows that you should use the most terse names possible, in order to make it harder to write too-long functions.

(I am only half trolling).


I figure it's probably proportional to its importance and difficulty of understanding, as a longer more descriptive name aids in understanding, but things with broader scope tend to be more important.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: