Talk:Arbitrary-precision integers (included): Difference between revisions

First of all, the task should be redefined to ''enforce computations during the run time'', because 5**(4**(3**2)) can be precomputed or computed in a compile time (esp. in HaskelHaskell-like). Secondly, there is no need to say "do not submit an implementation of arbitrary precision arithmetic". Program MUST use some kind "arbitrary precision arithmetic" (20 digits at least) - either an internal feature or an external module/library. Finally, see "pure C solution" - it is ''ugly, but it SOLVE'' the problem. - andTherefore the note "this example is incorrect" is not justified.