THC posted:

last summer I worked at a C# shop which swears by K&R style. but nobody could figure out how to stop ReSharper autocorrecting to Allman style. So every time I checked in code I had to K&R-ize it first

prefect posted:

i see it in the resharper options, languages > c# > formatting style > braces layout

Bloody posted:

keep in mind this is a shop dumb enough to not use allman so they cant exactly be expected to be able to navigate menus

Doc Block posted:

And what, pray tell, is the Shaggar-approved brace style?

Doc Block posted:

real men use the K&R One True Brace Style

code:

int main(int argc, char *argv[])
{
    if(yourmom == laffo) {
        gb2gbs();
    } else {
        yospos_bitch();
    }

    return 0;
}

Shaggar posted:

cool ugly unreadable crap

Doc Block posted:

real men use the K&R One True Brace Style

code:

int main(int argc, char *argv[])
{
    if(yourmom == laffo) {
        gb2gbs();
    } else {
        yospos_bitch();
    }

    return 0;
}

Tiny Bug Child posted:

this is almost correct, but opening braces never go on their own line

Tiny Bug Child posted:

this is almost correct, but opening braces never go on their own line

GNU Order posted:

I never had to use braces, perfectteeth crew represent

prefect posted:

nrook posted:

code:

using System.Diagnostics; {
}

This isn't what that means, but it'd be way cooler

prefect posted:

why, in order to run some external program, do i have to get involved with something in "system.diagnostics"? that seems like the wrong place for "i want to execute something"

Shaggar posted:

well yes if you're a terrible developer that happens, sure. but if you cant properly deal w/ checked exceptions ur a huge idiot.

Tiny Bug Child posted:

this is almost correct, but opening braces never go on their own line

Hellsworn Barn posted:

there is literally no way to "properly deal with checked exceptions." the key to safe exception handling is centralization. every process/app domain/whatever should have a centralized handler responsible for managing control flow based on exception type/data/context. the good part about checked exceptions is that they provide information regarding what exceptions may be thrown, which helps get the logic in your centralized handler right the first time. the bad part about checked exceptions is that it encourages bad exception handling practices by forcing you to deal with exceptions throughout your code. the good is greatly outweighed by the bad since proper design all but eliminates the need for conditional logic based on exception type.

tef posted:

you're not forced to handle exceptions though, the whole point is that any line can throw one so you don't have to be explicit which one.

checked exceptions are a poor implementation of option types.

Shaggar posted:

checked exceptions ensure that developers deal with them instead of ignoring them.

prefect posted:

i see it in the resharper options, languages > c# > formatting style > braces layout

tef posted:

even the java library doesn't make effective use of them

tef posted:

oh I forgot shaggar wants checked exceptions and not option types because he's anti union

Shaggar posted:

handles it lazily

JewKiller 3000 posted:

close thread, a better post than this cannot be made