Oh thats exactly why they were created
put it this way tho:
you get hired by a company working on a huge x86 emulator.. theres over a million lines of code and all the
class files are labelled along the lines of:
"Class1.m" and the variables inside it go along these lines:
Code:
int a, b, c;
char *str1 = "hello world";
char *str = "blah";
BOOL flag;
and imagine you had to read thru all 300 class files so you can know which file to focus on to implement the feature your boss told you to add. How many days do you think it would take you to go thru all the code and find what you are looking for as compared to a project that has good naming conventions, reusable classes, etc ?
Also in the case of apple.. if they made their table views not be reusable we would all be doomed and would have to write our own table view classes.. wouldn't that suck ? =P
Overall if you are the only one who will be working with your code and you know where everything is at and you feel you'll remember where everything is 2 years from now then get crazy with it as long as you release your product on time.
Quote:
Originally Posted by myersn024
I'm sure coding standards were created by people who were forced to figure out someone else's coding style LOL!
|
