|
I usecode:
|
# ? Jul 9, 2013 16:20 |
|
|
# ? Jun 5, 2024 09:34 |
|
Otto Skorzeny posted:I never got annoyed until I had to finish a product's firmware that had been done in Whitesmith's style. Couldn't tell what lined up with what for the life of me. Had the same problem last time I hosed around with Common Lisp - the parens were fine (my editor did some rainbow thing with em, which was surprising), the indentation just threw me for a loop. Say what you want about indentation style, I think we can all agree Whitesmith is wrong
|
# ? Jul 9, 2013 16:24 |
|
But not as wrong as GNU.
|
# ? Jul 9, 2013 16:36 |
|
Eastern Polish Christmas Tree Notation: http://www.kuro5hin.org/story/2004/6/1/43942/41236
|
# ? Jul 9, 2013 17:42 |
|
The Something Awful Forums > Discussion > Serious Hardware / Software Crap > The Cavern of COBOL > Coding horrors: post the indentation style that makes you laugh (or cry)
|
# ? Jul 9, 2013 17:49 |
|
I knew full well what would happen if I so much as mentioned coding styles in this thread, but I did it anyway
|
# ? Jul 9, 2013 18:10 |
|
Bunny Cuddlin posted:Are you people loving serious This has to happen every few months. Extremist pedantry comes with the job.
|
# ? Jul 9, 2013 18:24 |
|
Munkeymon posted:This has to happen every few months. Extremist pedantry comes with the job. Extremist pedantry is the job considering how literal computers are and how many bugs boil down to sloppy thinking about the problem.
|
# ? Jul 9, 2013 18:31 |
|
none of this would happen if y'all wouldn't be using languages with C-derived syntaxes.
|
# ? Jul 9, 2013 19:22 |
|
MononcQc posted:none of this would happen if y'all wouldn't be using languages with C-derived syntaxes. right, with python that argument is gone, which leaves room for the more important tabs vs spaces and 4 space vs 8 space indent (spaces, 4, btw)
|
# ? Jul 9, 2013 19:31 |
|
Pilsner posted:Can we at least agree that people who indent with spaces instead of tabs are objectively wrong? It fucks up diff'ing. We can agree that all tabs should be expanded to N spaces in your editor of choice so that people who use tabs and spaces get the same code
|
# ? Jul 9, 2013 20:21 |
|
No agreement can be made about abominable practices.
|
# ? Jul 9, 2013 20:41 |
|
Ronald Raiden posted:right, with python that argument is gone, which leaves room for the more important tabs vs spaces and 4 space vs 8 space indent (spaces, 4, btw) And every single thing listed in PEP-8. Wherein Python discovered that indentation is not the only whitespace issue.
|
# ? Jul 9, 2013 20:55 |
|
there are always more code formatting practices to argue about.
|
# ? Jul 9, 2013 21:35 |
|
Ronald Raiden posted:there are always more code formatting practices to argue about. just as there are always more assholes to gaze into
|
# ? Jul 9, 2013 22:03 |
|
Is this where I ask about "EmployeeID" vs. "EmployeeId" vs. "Employee_ID" vs. Employee_Id" vs. "Employee_id" ?
|
# ? Jul 9, 2013 23:34 |
|
Obviously uint32_ei
|
# ? Jul 9, 2013 23:44 |
|
Che Delilas posted:Is this where I ask about "EmployeeID" vs. "EmployeeId" vs. "Employee_ID" vs. Employee_Id" vs. "Employee_id" ? employeeID and I dare anyone to tell me otherwise
|
# ? Jul 10, 2013 00:31 |
|
i'm tracking milliliters in my camelCase code, should it be targetML, targetmL, targetMl, or targetml???
|
# ? Jul 10, 2013 00:37 |
|
Embedded NBSP characters. Why have them as valid characters in the source code if they're not useful.
|
# ? Jul 10, 2013 00:40 |
|
Volmarias posted:employeeID and I dare anyone to tell me otherwise code:
|
# ? Jul 10, 2013 01:12 |
|
Terrible coding/indentation styles don't bother me nearly as much as inconsistent ones. Last week I took I project I maintain that had over the years accumulated a mix of files with 2, 3, 4, and 8 column indents using spaces, tabs, or both, and automatically reformatted it all to a consistent style. Sent the reviewers a 150K diff consisting entirely of whitespace changes.
|
# ? Jul 10, 2013 01:20 |
|
Obviously the solution is to only exchange tokenized grammar tree files that can be rendered into readable text instantly with whatever display style you choose. That idea is probably dumb enough that it has already been tried and failed spectacularly.
|
# ? Jul 10, 2013 01:28 |
|
JawnV6 posted:i'm tracking milliliters in my camelCase code, should it be targetML, targetmL, targetMl, or targetml??? targetMillis
|
# ? Jul 10, 2013 01:38 |
|
RoadCrewWorker posted:Obviously the solution is to only exchange tokenized grammar tree files that can be rendered into readable text instantly with whatever display style you choose. QuakeScript
|
# ? Jul 10, 2013 01:38 |
|
Volmarias posted:employeeID and I dare anyone to tell me otherwise But would this be the same if it were a class? A member? A function?
|
# ? Jul 10, 2013 01:57 |
|
ToxicFrog posted:Terrible coding/indentation styles don't bother me nearly as much as inconsistent ones. git diff -w
|
# ? Jul 10, 2013 01:58 |
|
Kilson posted:No agreement can be made about abominable practices. The abominable practice being the use of tabs in code, since it really can gently caress up any language that uses white space; expanding tabs into whitespace is good, of course
|
# ? Jul 10, 2013 02:43 |
|
Strong Sauce posted:git diff -w Well, yeah, but then the diff is empty and there's nothing for them to review
|
# ? Jul 10, 2013 02:56 |
|
Che Delilas posted:Is this where I ask about "EmployeeID" vs. "EmployeeId" vs. "Employee_ID" vs. Employee_Id" vs. "Employee_id" ? pfft, everyone who's had to touch PeopleSoft knows it's EMPLID
|
# ? Jul 10, 2013 03:03 |
|
My favorite response to the whitespace wars is F#, which forbids any tab characters in its source files.
|
# ? Jul 10, 2013 03:14 |
|
RoadCrewWorker posted:Obviously the solution is to only exchange tokenized grammar tree files that can be rendered into readable text instantly with whatever display style you choose.
|
# ? Jul 10, 2013 03:15 |
|
Lumpy posted:
I don't know but maybe you can help me with mine???? code:
|
# ? Jul 10, 2013 04:45 |
|
That reminds me:code:
|
# ? Jul 10, 2013 05:39 |
|
kitten smoothie posted:pfft, everyone who's had to touch PeopleSoft knows it's EMPLID oh man I did that. Peoplesoft sucks.
|
# ? Jul 10, 2013 07:41 |
|
Ronald Raiden posted:oh man I did that. Peoplesoft sucks. You came back from Peoplesoft? I'd heard rumors before, but no one that I have met has actually claimed to have done so. I thought it was a black hole from which no IT personnel could escape.
|
# ? Jul 10, 2013 08:49 |
|
RoadCrewWorker posted:Obviously the solution is to only exchange tokenized grammar tree files that can be rendered into readable text instantly with whatever display style you choose. The simplest way would be to store everything in normal files with a fixed whitespace style, and use version control hooks to adjust it depending on the user's preference whenever it's checked in or out.
|
# ? Jul 10, 2013 09:20 |
|
Rottbott posted:I've always wished for this. I don't understand why it isn't a thing, it seems obvious to let everyone view the files however they prefer, and avoid whitespace changes polluting the version control logs. It seems "obvious" to store your source code in a binary format that needs its own, special editor (or at the very least editor plugin) and source control toolchain?
|
# ? Jul 10, 2013 09:47 |
|
The obvious way is to have a mandatory, tool-enforced coding style, and anyone who wants to use something different can write their own tool to convert back and forth on checkout and checkin. In fact you could do this now if you want, and it wouldn't require any of your coworkers to do anything different if there already is a consistent coding style being enforced in your source control.
|
# ? Jul 10, 2013 12:58 |
|
|
# ? Jun 5, 2024 09:34 |
|
the obvious way is to basically kill anyone who has an opinion on "brace/formatting", because it's basically programmers arguing over their favourite colour.
|
# ? Jul 10, 2013 13:12 |