Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:Dumb question, but where should we store them? (Score 1) 112

The way that I deal with idiotic requirements like this is to append a four digit date in MMYY format to the end of the PW, and just update to the current date. So if I am required to update a PW this month, the new PW will be clownhorsepenisstaple0916.


Comment Re:Both. (Score 1) 391

Ah. I mis-remembered. Thank you for the correction. Yes, I encountered some code once that a coworker had written which had indentation like 0x09 0x09 0x09 0x09 0x20 0x20 0x20 0x20. I wanted to pour coffee on his keyboard. God, that shit is awful to deal with. Spaces are for alignment, not indentation.

Comment Re:Tabs are redundant these days (Score 1) 391

Back then, the term mibibyte hadn't been invented, but yes, when they were referred to as 4.8 it was a binary and not a decimal unit.

I believe you mean mebibyte, not mibibyte.

When? The disks I'm thinking of came as a removable platter with a published capacity of initially 2.4 MB (or what would now be called mibibytes), increasing with later models to 4.8 MB.

I was confused. I was thinking of machines like the IBM 305 RAMAC, which stored 5 million 6-bit characters (which is only about 3.75 MB).

Comment Re:Both. (Score 1) 391

Bzzzzzt. Combining tabs and spaces to make up a single indent level is BRAIN DEAD.

Actually no. Indenting w/just tabs is brain dead and indenting w/just spaces is counter-productive. Your low UID aside, I'll stack my 30 years of experience using Emacs like that against that any day.

Actually, yes. Mixing tabs and spaces to make a single indent level (e.g., 0x09 0x20 0x20 0x20 0x20 0x09 0x20 0x20 0x20 0x20) is about the most braindead, stupid, foolish, retarded, dumb thing you could ever do in a text file. It ruins things for everyone.

Comment Re:problems, lol (Score 2) 232

An assertion should just be the evaluation of a boolean expression.

Assertions can be anything you want them to be. There is no (nor should there be) requirement that they be a boolean expression.

Sometimes it is sensible to say assert(foo_is_valid(foo)); on some object foo, and the foo_is_valid() call might need to do a lot of work.

Or... In an arbitrary precision integer arithmetic library, if you compute the quotient and remainder q and r of a divided by b, it is sensible right before returning to assert that b times q plus r equals a, which obviously incurs a significant speed penalty and should not be part of the production code if the math library needs to be as performant as possible.

I write assertions to document state and to help catch errors. I don't care how fast or slow they run. They are meant to be compiled out.

Slashdot Top Deals