Well, bigint has been there for a long, long time (emacs has it built in, even my calculator works with up to 512-bit bigints).
It's useful when you don't care too much about the execution speed of the program. If you're using Java, you probably don't. But MMORPG engine programmers definitely should make sure their systems don't get slow when many users are connected. After all, how often do you need a billion hitpoints?
On a side note: Windows64 (*), which runs on AMD64 in 64-bit mode, has 'long' still only 32-bit, so that old i386 applications don't break after being recompiled. Rather ugly, ain't it?
(*) - which will be about 40 years late, considering Microsoft product naming scheme
Surprisingly enough, no. A long on a 32-bit architecture is 32-bit, the same size as an int. That's because on most architectures the size of a long is the same as of a pointer. For 64-bit numbers you need a 'long long' or "uint64_t".
It's interesting that the story says that the
beast had 100 billion hitpoints. This wouldn't
fit into a 'long' on a 32-bit architecture. So
either is EQ using more than 32-bit numbers for
hitpoint counting, or it was something like
2147483647 (2^31, two billion) hitpoints and they actually managed to underflow the counter...
... it was two different grounds. One from the computer (and thus from the power outlet), and the other from a common antenna outlet that carries radio and TV for the whole house. Although the grounds are connected at the roof, with me living on the first floor they're not acting like connected for high frequencies anymore. I solved the problem by disconnecting the stereo from the common antenna and using my own antenna to receive radio. Conclusion: Always use one ground only. Star/tree topology is a must for grounding. Never create loops.
This looks like a group speed of interfering waves - while this can be greater than c, it cannot be used to transfer information, and thus this all is a nice albeit quite useless experiment.
See any basic electromagnetic field theory for a better explanation.
Why talk about athlon optimizations? GCC already supports the x86-64 arch, and Linux runs on it, see http://www.x86-64.org
Way to stop spam? More like to make money ...
on
Haiku vs Spam
·
· Score: 1
Excerpt from the news article: ----- Individuals and Internet service providers canlicense and use the mark for free, while businesses and *bulk*e-mail*companies* will pay to use it. ----- So they're probably not as innocent as they try to appear.
The slashdot headline misses the important part of the story, the fact that they compiled C# using MCS on *Linux*, using the Linux runtime, as opposed to doing this on Windows, which was done about two months ago.
Slashdot Mirror
Well, bigint has been there for a long, long time (emacs has it built in, even my calculator works with up to 512-bit bigints).
It's useful when you don't care too much about the execution speed of the program. If you're using Java, you probably don't. But MMORPG engine programmers definitely should make sure their systems don't get slow when many users are connected. After all, how often do you need a billion hitpoints?
On a side note: Windows64 (*), which runs on AMD64 in 64-bit mode, has 'long' still only 32-bit, so that old i386 applications don't break after being recompiled. Rather ugly, ain't it?
(*) - which will be about 40 years late, considering Microsoft product naming scheme
Surprisingly enough, no. A long on a 32-bit architecture is 32-bit, the same size as an int. That's because on most architectures the size of a long is the same as of a pointer. For 64-bit numbers you need a 'long long' or "uint64_t".
It's interesting that the story says that the beast had 100 billion hitpoints. This wouldn't fit into a 'long' on a 32-bit architecture. So either is EQ using more than 32-bit numbers for hitpoint counting, or it was something like 2147483647 (2^31, two billion) hitpoints and they actually managed to underflow the counter ...
-- Vojtech Pavlik, SUSE Labs
... it was two different grounds. One from the computer (and thus from the power outlet), and the other from a common antenna outlet that carries radio and TV for the whole house. Although the grounds are connected at the roof, with me living on the first floor they're not acting like connected for high frequencies anymore.
I solved the problem by disconnecting the stereo from the common antenna and using my own antenna to receive radio.
Conclusion: Always use one ground only. Star/tree topology is a must for grounding. Never create loops.
See any basic electromagnetic field theory for a better explanation.
Why talk about athlon optimizations? GCC already supports the x86-64 arch, and Linux runs on it, see http://www.x86-64.org
Excerpt from the news article:
-----
Individuals and Internet service providers canlicense and use the mark for free, while
businesses and *bulk*e-mail*companies* will pay to use it.
-----
So they're probably not as innocent as they try to appear.
The slashdot headline misses the important part
of the story, the fact that they compiled C# using MCS on *Linux*, using the Linux runtime, as opposed to doing this on Windows, which was done
about two months ago.