fixed

in C#

I've been doing this for quite a long time and never stumbled across it. A quick survey of my entire develpment team, and not one of them were aware that hexadecimal fractions were a thing.

Yes, and there are more things in the world you, or I, don't know. So what's your point? Google is a thing, you know? I'm not supposed to be spoon-feeding something just because someone in the world doesn't know about it, as that's a lost cause.

"Hexadecimal fraction" itself is already more than enough to let you find out what that means. "Binary fraction" is used everywhere related to floating points too. It's not like didn't put anything.

The example is very unclear in regards to this specifically. For instance, there is zero disambiguation between literals and strings. As stated previously, it appears as if the 0. is simply prepended to the beginning of a hex string.

Again, your point? Writing hexadecimal fractions as 0.db9318c2259923d0 is the proper terminology, just like 0.1 binary decimals is 0.000110011001100.... I'm not responsible for people not reading the correct terminology and then proceed to complain about it being unclear.

my point was that if you are going to explicitly list out all of the other steps, then you should at least mention it as being one of the steps. It is not only an omited step

What omitted step? The description already says and convert them back to base 10. If you're asking to me detail how the conversion is done, nope, because it's basically asking for me to explain how MD5 is calculated.

it is also very esoteric considering that the language being tested doesn't even recognize hex fractions as being valid.

So you're saying something is esoteric just because the language doesn't support it on the fly? What kind of reasoning is that? Some languages don't have MD5 built-in either. So is MD5 "esoteric" now?

I don't understand what you mean by this?

Just because you failed to use parseInt to do the conversion directly doesn't mean it's my fault for that. The ball is at your court, so don't throw it at me.

In any case, I'm taking your issue as "you didn't mention what is hexadecimal fraction and how to convert it to decimal fraction", which I'm responding with "I've already provided more than enough information and I'm not responsible for you being dumb and takes a long time figuring out something from a description that already provides all the necessary information". If you're feeling salty, go calm down somewhere else; don't speak as if there are problems with the kata and it's my fault.

I've already answered about this below. If you know what decimal fraction is, you should know what a hexadecimal fraction is. I also did not invent the concept, as you already said there. And there's already an example given. There are more than enough information. Do I really have to outright explain every step how to derive a hexadecimal fraction?

The fact that your brain farted up for some time is not an issue to the kata itself. The fact that you can't just take a parseInt shortcut is not an issue either ;-)

Now all works, thanks.

Missed a whole block, I'll blame it on being the morning. Should be good to go.

Sure, sample tests are ok now, final tests (at least for me) still have assertSimilar and don't pass. Could you check it? I'll try later again and if it works, mark it as resolved.

Thanks Chrono, should work now? Would you like to test then mark this issue as resolved. Cheers.

assertSimilar is used (you can see the sample tests), it turns both objects to strings and that's why it fails. assertDeepEquals should be used instead. You can define your keys in the expected order too in the meantime.

I'm sorry, I see the suggestion just now, because I didn't receive a reminder.

Thanks for your suggestion, but I can't modify this kata now, according to the rules of CW, if a Kata solution is more than 500, will not be modified ;-)

How did you figure out it was calling say_hello()?

I finally got it working.

You should use range instead of xrange and then this Python translation will work for both versions of Python (instead of only 2.7.6 currently).