HealthBase knows how to deal with those damn nips:
HealthBase knows how to deal with those damn nips:
@KattMan said:
Just because the rule exists, doesn't mean that people will follow it.
If nobody follows it, then you can hardly consider it part of the language.
Case in point, when writing out cheques (which is also the proper form, check is that mark you make, not the note, but American English uses it for both) you write 103.50 in the numerical part but then under it you write One hundred three dollars and fifty cents; the and implying the decimal here.
No, the "and" is used to represent addition here; the "dollars" and "cents" are [i]units[/i]; you wouldn't say that with something like "five feet and two inches", for example, the "and" represents the decimal place.
FUCKING EDIT TIME LIMITS
Let's just pretend the forum software isn't utter shit, and this is what my post says now:
@The Real WTF said:
The global statement being after the assignment is a mistake, and Python will warn you of this, like so:
<stdin>:8: SyntaxWarning: name 'interpretedData' is assigned to before global declarationIf the d_list argument is *really* never used, then it can be simplified to this:
def SetData(data):Otherwise, you can't make any other changes without modifying its behavior.
interpretedData[str(data[1])][str(data[0])]=str(data[2])
The global statement being after the assignment is a mistake, and Python will warn you of this, like so:
<stdin>:8: SyntaxWarning: name 'interpretedData' is assigned to before global declaration
If interpretedData is never assigned to a different object and the d_list argument is *really* never used, then it can be simplified to this:
def SetData(data):Otherwise, you can't make any other changes without modifying its behavior.
interpretedData[str(data[1])][str(data[0])]=str(data[2])
@gremlin said:
Actually, the code to do the conditional jump after the comparison would be large enough that you could overwrite it with a nop or an unconditional jump so that your game will run whether you have the CD in the drive or not.
Yes, but where's the fun in such a simple, practical solution?
@Spectre said:
I was lucky. An imaginary Japanese hacker wouldn't be able to patch the executable like I did, since その他 is longer than 5 bytes in every encoding I can think of. Although, he might be able to hack the Windows multimedia library instead 8=].
Actually, the code to do the string comparison would probably be large enough that you could overwrite it with code to just compare the first byte or word or whatever works best.
@PSWorx said:
Unrelated to the WTF, I vote"Technobabble" does not mean "them fancy words I don't understand".Your new adaptive quantization patch results in a corrupt stream when interlaced encoding is activated!for the Technobabble Sentence of the Week.
Oh wow, OGame. That brings back memories. A long time ago, I put a lot of effort into it and ended up as one of the top players in a small but powerful (and rapidly advancing) alliance. Then I realized that, like every other MMO I had played before, it was taking up all of my free time, so I quit. I sort of regret it because except for the soul-sucking that's seemingly inherent to MMOs, it was fun. And not just due to the fact that it was a PvP game and I far overshadowed most of the other players.
[quote user="hk0"]Come to 7chan.org/pr
It's better there.[/quote]That's img.7chan.org/pr/. Also, /g/ = Technology (though it would be more accurate to call it "Technology Flamewars"), and thus /tech/ would be the analogous 7chan board.
Also, /pr/ sucks for requiring images for threads.
Maybe it's just because I didn't sleep at all last night, but I don't really see anything WTF-worthy in this. This:
$message = "Name: $name\n";should be an append, not an assignment, and the use of stripslashes implies that magic quotes are turned on (which is a Bad Thing), and the code style is a bit inconsistent, but, again, no WTFs in sight.
Edit: never used PHP's mail function, but if that's true, then it makes a bit more sense.
Worst I've done is accidentally rm -rf'ing /usr/lib32/. Could've been a lot worse, but it still wasn't fun to fix. I've also done "do-shit foo > foo" or something similar a few times, but I've luckily never lost any important files to that.
And how do you get a password wrong *three* times in a row? I've got a 20-character password for disk encryption that I have to enter at every boot, and two cats who very much like to sit on the keyboard to get my attention, and I've still never gotten it wrong even *twice* in a row.