Timeline for Conflicting Java Styles within a Team
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2012 at 1:27 | vote | accept | daniel gratzer | ||
| Feb 21, 2012 at 1:27 | vote | accept | daniel gratzer | ||
| Feb 21, 2012 at 1:27 | |||||
| Jan 22, 2012 at 14:50 | comment | added | Andres F. | @userunknown You're right. I don't even agree with all of the conventions. But it is a good compromise given the timeframe of the OP. | |
| Jan 22, 2012 at 13:54 | comment | added | user unknown | This is a convention, and might be a reasonable fallback, if you can't find an own agreement, but as the name states, it doesn't dictate - it is a convention. | |
| Jan 22, 2012 at 11:06 | comment | added | user1249 | @MartijnVerburg the limit can prompt refactoring into methods and classes to avoid deep indentation. | |
| Jan 22, 2012 at 9:21 | comment | added | Martijn Verburg | This is a well known std, but don't be afraid to deviate from it where the team agrees. Being restricted to 80 characters in width can be painful for example. | |
| Jan 22, 2012 at 3:49 | vote | accept | daniel gratzer | ||
| Jan 22, 2012 at 3:49 | |||||
| Jan 22, 2012 at 3:29 | history | answered | Andres F. | CC BY-SA 3.0 |