pike.git / lib / modules / Int.pmod

version» Context lines:

pike.git/lib/modules/Int.pmod:11:   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").   //! + //! @[NATIVE_MIN] is not greater than @expr{-2147483648@} + //! (@expr{-0x80000000@}). + //! + //! @[NATIVE_MAX] is not less than @expr{2147483647@} + //! (@expr{0x7fffffff@}). + //!   //! @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.