- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
It's probably easier for the submitter than for us to understand these comments, but some seem to be humoristic. The final one might be some kind of prank on newbies: senior tells junior to turn that flag on, junior sees comments, hilarity ensues.
Admin
Sounds like my kind of commenting style. Trying to figure out convoluted things, be they code, config files or a textbook can be made a lot less dreary and thus a lot more efficient (your attention lapses when you are bored) with a sprinkling of humor.
Like, if you are adding some test code to your branch just to see what happens you could comment it as "Do not commit. Test code." or you could say "Test code. If you commit this you go strait to hell, no trial." One is more fun.
Edit Admin
The obvious reason is that you'll eventually have to migrate to IPv6, where UDP checksums are mandatory. And there's mostly no point in turning it off, since these days network cards are almost all capable of doing it for you.
Oh, and it's worth remembering that for "endianness" reasons, "Internet" checksums are the last volume-use bastion of the abomination called "one's complement". If the "true" calculated checksum is 0x0000, we send "negative zero" (0xFFFF) instead, reserving a "true" value of 0x0000 to mean "no checksum provided". Which is banned in UDP-over-IPv6 packets.