Good catch! I fixed it.

Thanks you guys! It's nice to have this finished finally!

Just curious about the random tests: if they expect the output of the function, what purpose do they serve? Isn't it like saying expectEqual(1, 1) or am I missing something?

Right. Based on feedback I changed one of the tests so now all the old ones from years ago are invalid. :*(

Hmm. just curious, how do I get the attention of a moderator for approval?

I think matt c is probably correct.

I got too frustrated with this conversation and gave up. But I'm back! here's where I settled on the and thing.

• The word 'and' is used to separate the tens space from the hundreds space in each period
  • 111 -> Good: "one hundred and eleven" - Bad: "one hundred eleven"
  • 101,101,101 Good: "one hundred and one million one hundred and one thousand one hundred and one" - Bad: "one hundred one million one hundred one thousand one hundred one"
• ...also the word 'and' is used to separate the tens and ones space from the lowest number the left of the tens place for numbers over 1000.
  • 1,001 -> Good: "one thousand and one" - Bad: "one thousand one"
  • 1,000,001 -> Good: "one million and one" - Bad: "one million one"
  • 1,000,011 -> Good: "one million and eleven" - Bad: "one million eleven"
  • 1,000,111 -> Good: "one million one hundred and eleven" - Bad: "one million and one hundred and eleven"
  • 1,011,011 -> Good: "one million eleven thousand and eleven" Bad: "one million and eleven thousand and eleven"

Hi remember me? I went back after a couple of years and finalized the code. If you're not happy with the "and" rules, i'm afraid that's too bad :-D
Hopefully this will get things back on track for approval.

I frankly got too frustrated with the "and" argument to finish fixing it to everyone's liking. But I will go back and review.

I guess I kinda gave up on trying to impliment this suggestion.

fixed.

Thanks. Good catch.

For some reason, the line "The first index should always be smaller than the second index." made me think the prices of items in the array were always in order from cheapest to most expensive. Perhaps, "The indeces in your answer should be ordered from lowest to highest."

That sounds like what I had originally. But do we add a special case for

640,000,000 - Expected: six hundred forty million, instead got: six hundred and forty million

I told you it was difficult to define for the spec!

OK. I went and did it. This still sounds wrong to my ear but I don't know. I think it's probably weird hearing huge, strange numbers.

These sound weird to me...
"one hundred million and twenty-three thousand nine hundred and ninety-nine"
"one million and one thousand and one"

i don't mind :)