Examples
User documentation
IMPORTANT NOTE:
- see
BigIntOpsfor basic operations on values of typeBigInt - see
NumTheoryfor more advanced operations
Generalities
The class BigInt is intended to represent integers of practically
unlimited range. CoCoALib relies on an external library for handling big
integers: currently it is based on GMP, the GNU multiple precision
library. This CoCoALib code simply forms the interface to the underlying
big integer library.
Computations with BigInt values do not suffer from overflow, but
they are significantly slower than with machine integers. All
BigInt values are stored on the heap.
It is important not to confuse values of type BigInt with values of type
RingElem which happen to belong to the ring RingZZ. In summary, the
operations available for RingElem are those applicable to elements of
any ordered commutative ring, whereas the range of operations on BigInt
values is wider (since we have explicit knowledge of the type).
See BigRat for representing and handling rational numbers.
The Functions Available For Use
Constructors
A value of type BigInt may be created from:
BigInt()the value is zeroBigInt(n)wherenis a machine integerBigInt(N)whereNis another value of typeBigInt(its value is copied)BigIntFromString(str)wherestra string containing the decimal digits (optionally preceded by a minus sign); leading and trailing whitespace is allowedBigIntFromMPZ(ptr)whereptris a GMPmpz_tvalue
Note that we use pseudo-ctors for constructing from a string or an mpz_t (this is to avoid problems of ambiguity with BigInt(0) since 0 can be viewed in C++ as a null-pointer).
Note: No direct constructor for creating a BigInt from a char* is
provided, however C++ will automatically convert a char* into a
std::string, so you can still use a C-string if you want.
Operations
IMPORTANT NOTE
- see
BigIntOpsfor basic operations on values of typeBigInt - see
NumTheoryfor more advanced operations
- Functions violating encapsulation
mpzref(n)-- this gives a (const) reference to thempz_tvalue inside aBigIntobject. You should use this accessor very sparingly (but it is handy for calling GMP functions directly).
Maintainer Documentation
The implementation is structurally very simple, just rather long and
tedious. The value of a BigInt object is represented as an mpz_t;
this is a private data member, but to facilitate interfacing with code
which uses mpz_t values directly I have supplied the two functions
called mpzref which allow access to this data member.
The output function turned out to be trickier than one might guess.
Part of the problem was wanting to respect the ostream settings.
Of course, input is a mess. Nothing clever here.
Check also the documentation for MachineInt to understand how
that class is used.
Bugs, shortcomings and other ideas
Currently functions which return BigInt values will copy the result (upon
each return) -- an attempt to avoid the waste with proxy classes caused a
problem see test-bug4.C Move semantics in C++11 should solve this.
The official GMP interface (mpz_class) is certainly more efficient;
should CoCoALib eventually switch to using mpz_class?
It seems most unlikely that GMP will be displaced from its
position as the foremost library for big integer arithmetic, so
such explicit dependence on it should not matter.
No bit operations: bit setting and checking, and/or/xor/not.
The code is long, tedious and unilluminating. Are there any volunteers to improve it?
Main changes
2018
- April:
- removed ctors from
stringandmpq_t; replaced them by pseudo-ctors. This means thatBigInt(0)now works as expected (previously it worked thanks to a dodgy hack). - 2012
- removed ctors from
- May (v0.9951):
- moved common operations on
BigIntandMachineInttogether intoIntOperations- 2011
- moved common operations on
- August (v0.9950):