>>>>
>>>>So... the ToString() value actually does exceed the max.
>>>>
>>>>That was fun.
>>>
>>>No it wasn't ! I had to buy a bigger monitor :-}
>>
>>LOL it was a long number.
>>
>>in finishing off that large number lib, I ran into this:
>>
>>C#
>> ? -1000 % 3 = -1
>>
>>VFP
>> ? -1000 % 3 = 2
>>
>>Can anyone explain that one?
>
>
>
>ps:
>>in finishing off that large number lib, I ran into this:
>
>
>You do know that C# 4.0 has a BigInteger value type http://msdn.microsoft.com/en-us/library/system.numerics.biginteger.aspx

Cool, I'd forgotten about that. But I also had no real world use for the code I wrote. It was just something I did for the fun of it. For some reason, the code for it had been bouncing around in my head for years, it was fun to get it out of there. <g>

Interesting to see the similarities in what they did, and what I did. Mine also ended up being an immutable structure with overloaded operators, I also chose to use little-endian order for the arrays. So I suspect internally there are also a lot of similarities. Overall, looking at that class validates a lot of how I did what I did. Nice to know I was on the right track. Tempted to finish mine off and run some head to head performance tests. I strongly suspect BigInteger would win, but I'm curious to see by how much. It would be cool to dig into it and see how they optimized some of it. In writing mine, I saw a number of things that could be better optimized than what I had time to write.

Anyways... I'm rambling, thanks for reminding me about that. And for the link on modulo operators!