The c= is the declaration. Since there is no const, let or var, it's declared as a global variable.

Why not?

Michacom, sure, am going to fix it as soon as posible. Do you desire something else? Don't hesitate to ask should you have some suggestions.

yes

That would look more maintainable. Then again, the spec itself isn't best practice. Do one thing, and do it well. Separate zip and makeObject.

Already in the descriptions

We now have a BigNum library. For now, it's still too slow.

Well, I wouldn't say i'm a math-boy but i do intend to fix any problem with algorithms and formulae', not sure how you people are going to react based on my answers!! (fingers crossed) :o

There are two ways to handle IPv4 addresses with leading zeroes in the octetts.
Non-Microsoft way: ignore the leading zero -> this would lead to the testcase being wrong and 123.045.067.089 being a valid address
Microsoft way: a leading zero indicates the entered octett is in base 8 (octal) -> this would mean the test case is correct, because "089" is not a valid octal number

I guess both ways have their place, but it should be defined in the task description

Agreed. I don't understand why that test case is supposed to return false.... 123.045.067.089 => 123.45.67.89 and you could enter each into a computer and have it be valid. So why would we make an algorithm that's supposed to test validity but give it a rule that defines a valid ip as invalid?

I don't understand. That's a valid ip address.

Another problem with this is that some answers really are wildly better than the average. For instance, for many "find the value of the nth term in series" katas, the vast majority of users use loops (O(n) time), and a very few determine the equation to solve the series (constant time). This results in drastically better program time for a few people who would likely be labeled cheaters.