Re^5: PBP: Code Layout

We're just talking about code formatting, don't we? Taking care of formatting - if it's not the same I got used to in the last 24 years - is most certainly a hindrance to me and I believe to anyone with long programming history.

So if your goal is to have nice looking code and not to have good code, then maybe you're right and I really wouldn't fit into such a team.

If we're not talking about code formatting but what to use for programming, which module or even which language, it's another story. For example: I still don't like Java. But our programm is written in Java and I have written a big part of it. With my own code layout of course ;-)

The funny part about my Java is: A colleague said, that my Java code still looks like Perl. But that's just because one method he uses consists of 5 or so regular expressions, I think.

s$$([},&%#}/&/]+}%&{})*;#$&&s&&$^X.($'^"%]=\&(|?*{%
+.+=%;.#_}\&"^"-+%*).}%:##%}={~=~:.")&e&&s""`$''`"e

Comment on Re^5: PBP: Code Layout Select or Download Code

Replies are listed 'Best First'.
Re^6: PBP: Code Layout by chromatic (Archbishop) on Oct 20, 2005 at 06:53 UTC
So if your goal is to have nice looking code and not to have good code... It's not. My goal is to have people on the team who really want to work as a team for the good of the team, not merely as a collection of individuals who happen to have similar jobs. If expressing yourself through your formatting is more important than writing clear code (and if you truly will not adapt to the team's guidelines about where to put your braces, why should we hope that you follow the important guidelines?), there are plenty of other places that will have you.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.