b25fa62003-04-12Martin Nilsson #pike __REAL_VERSION__ //! Returns the parity of the integer @[value]. If the //! parity is odd 1 is returned. If it is even 0 is //! returned. int(0..1) parity(int(0..) value) {
fe6bcb2003-08-07Martin Nilsson  if(value<0) error("Parity can not determined for negative values.\n"); return Gmp.mpz(value)->popcount()&1;
b25fa62003-04-12Martin Nilsson }
a63b362003-11-07Martin Stjernholm  constant NATIVE_MIN = __builtin.NATIVE_INT_MIN; constant NATIVE_MAX = __builtin.NATIVE_INT_MAX; //! The limits for using the native representation of integers on the //! current architecture. Any integer that is outside this range uses //! a more complex and slower representation. Also, some builtin //! functions that don't expect very large integers might start to //! complain about invalid argument type when given values outside //! this range (they typically say something like "Expected integer, //! got object"). //!
4495092003-11-08Martin Stjernholm //! @[NATIVE_MIN] is not greater than @expr{-2147483648@} //! (@expr{-0x80000000@}). //! //! @[NATIVE_MAX] is not less than @expr{2147483647@} //! (@expr{0x7fffffff@}). //!
a63b362003-11-07Martin Stjernholm //! @note //! The size of the native integers can be controlled when Pike is //! compiled with the configure flags @expr{--with-int-int@}, //! @expr{--with-long-int@}, and @expr{--with-long-long-int@}. The //! default is to use the longest available integer type that fits //! inside a pointer, which typically means that it's 64 bit on "true" //! 64 bit architectures. //! //! @note //! If Pike is compiled with the configure flag //! @expr{--without-bignum@} (which is discouraged), then all //! arithmetic operations will instead silently wrap around at these //! limits.