Re: [RFC] Big Integer Support

From: Date: Sat, 11 Oct 2014 09:13:53 +0000
Subject: Re: [RFC] Big Integer Support
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-77876@lists.php.net to get a copy of this message
On 11/10/14 01:18, Andrea Faulds wrote: >>> >> What you want is 64-bit data handling. This is arbitrary-bit data handling. >>> >> It’s not a “wrong approach”. >> > >> > So BIGINT on 32 bit platforms will be different to BIGINT on 64 bit >> > platforms? BIGINT is a fix length number not a variable one … > “Bigints” typically refer to arbitrary-size integers, that is, their size is bounded only > by the amount of RAM available. > > I don’t know what you think a “bigint” is, but it’s different to everyone else. PLEASE rename the page name for this and stop using BIGINT for it ... BIGINT is the SQL99-compliant 64-bit signed integer type http://www.firebirdsql.org/refdocs/langrefupd25-bigint.html http://www.postgresql.org/docs/9.1/static/datatype-numeric.html http://dev.mysql.com/doc/refman/5.5/en/integer-types.html BIGINT is very much an 8 byte data value which we have been struggling with on PHP for some time. Now that it's available in 64bit builds, we need a simple transparent way to maintain that in 32bit builds ... If you are proposing BigInteger that is something else http://docs.oracle.com/javase/7/docs/api/java/math/BigInteger.html and GMP already provides that. Miking it up with the BIGINT standard which is something we DO need is the problem here ... -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk

« previous php.internals (#77876) next »