Re:Announcing .NET Framework 4.6
by hvs on Tuesday July 21, 2015 @11:16AM
(#9922793)
I really like the .NET Framework, so this is firmly tongue-in-cheek, but I found this amusing:
[ Parent
| on HN ]
Yikes, that's horrible. Both for it's length and the double-negative.
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;
}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.
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.
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.
Disable or suppress would work fine.