| Author |
Thread Statistics | Show CCP posts - 5 post(s) |
|
kieron
   |
Posted - 2006.08.31 17:32:00 -
[1]
Yes, I know I promosed to publish Tuxford's Dev Blog today, but that one needs to wait until tomorrow. Not to fear, I have a different blog to publish, and one that is pertinent to the delay of the patch that was supposed to be deployed this morning.
So, what is the Birthday Paradox and just how does it relate to 32-bit code? Mathematicians and cryptographers should be able to figure that out without batting an eye. For those of us who aren't as well versed in math or code, check out Porkbelly's Dev Blog.
kieron
Community Manager,
EVE Online |
|
|
kieron
|
Posted - 2006.08.31 17:38:00 -
[2]
Yes, the blog is saying the issue with the German localization will be fixed with Tuesday's patch.
kieron
Community Manager,
EVE Online |
|
|
Oveur
|
Posted - 2006.08.31 17:42:00 -
[3]
 Originally by: kieron
Yes, the blog is saying the issue with the German localization will be fixed with Tuesday's patch.
Or more correctly, we've been adding so much stuff that the german language pack tilted the scales. So this would have happened sooner or later, no need to blame the german language directly 
Senior Producer
EVE Online
|
|
|
Suvetar
Forum Moderator
Interstellar Services Department
|
Posted - 2006.08.31 17:49:00 -
[4]
I'll ask nicely that people don't start smack talking about the German language, please.
|
|
|
porkbelly
|
Posted - 2006.09.01 09:50:00 -
[5]
Edited by: porkbelly on 01/09/2006 09:51:54
Edited by: porkbelly on 01/09/2006 09:51:02
Originally by: Jean Perrau
Are you saying that your hash table code did not handle collisions ? Wow 
Indeed. We have a good excuse though: At the time this was written, the set of resources was largely static. Also, we were only looking up files that we knew were already in there. Thus, any collisions would be noticed and acted on at build time. The overhead of storing the actual filenames wasn't needed.
What has changed is that not only do we have more resources, we are also querying for possibly non-existant resource files (to see if localized versions exist), and this can create hash collisions at run time.
Anyway, it's one of those things that happens when you write code with certain assumptions, and then go ahead and violate them.
What it is! |
|
| |
|