News for hackers. Stuff that matters.
Re:Announcing .NET Framework 4.6 by s_kilk on Tuesday July 21, 2015 @11:25AM (#9922863)
Yikes, that's horrible. Both for it's length and the double-negative.
Re:Announcing .NET Framework 4.6 by CmonDev on Tuesday July 21, 2015 @12:44PM (#9923595)
Really? Stay away from Java then :):

HasThisTypePatternTriedToSneakInSomeGenericOrParameterizedTypePatternMatchingStuffAnywhereVisitor

http://grepcode.com/file/repository.springsource.com/org.asp...

Re:Announcing .NET Framework 4.6 by Lawtonfogle on Tuesday July 21, 2015 @04:44PM (#9925652)
You forgot the best part.

  public boolean wellHasItThen/*?*/() {
    return ohYesItHas;
  }
Re:Announcing .NET Framework 4.6 by hobarrera on Wednesday July 22, 2015 @04:09AM (#9928287)
I honestly though you and gp were just making it up exaggerating. This is even more absurd than made-up examples I've seen. And it's real.

I'm unsure if I should laugh or cry.

Re:Announcing .NET Framework 4.6 by tragic on Tuesday July 21, 2015 @01:42PM (#9924167)
Damn, that must have been a long day at the office.
Re:Announcing .NET Framework 4.6 by bitmapbrother on Tuesday July 21, 2015 @02:10PM (#9924408)
That's from a 3rd party library, though.
Re:Announcing .NET Framework 4.6 by moogly on Tuesday July 21, 2015 @12:11PM (#9923286)
Well, what's the alternative? The length at least is descriptive, there's no question about what it does. Double negatives are unfortunate, but that all depends on what the default value previously was (in the event that there actually was no flag like this, it definitely makes sense to make the default false, and then the language follows).

But sure, maybe PreventApply... would've been better. Then again, PreventApply... sounds weird, and should probably be PreventApplying..., but, ehh, naming is hard.

Re:Announcing .NET Framework 4.6 by caskance on Tuesday July 21, 2015 @12:16PM (#9923321)
Disable or suppress would work fine.
Re:Announcing .NET Framework 4.6 by nhebb on Tuesday July 21, 2015 @04:31PM (#9925565)
> the double-negative

Just speculating, but this might be a fail safe since bool's default to false in .NET.