A leading zero in a numeric literal means "this is octal". But don't be confused: a leading zero in a string does not. Thus:
$x = 0123; // 83
$y = "0123" + 0 // 123
int は、ℤ = {..., -2, -1, 0, 1, 2, ...} という集合です。
整数 (integer) は、10 進数(基数 10)、16 進数 (基数 16)、8 進数 (基数 8) あるいは 2 進数 (基数 2) 表記で指定可能です。オプションで、符号(-または+)を前に付けることが可能です。
8 進数表記を使用する場合、数の前に 0 (ゼロ)
を付ける必要があります。
PHP 8.1.0 以降では、数の前に
0o や 0O を付けても
8進数を表記できます。
また、16 進数表記を使用するには、数の前に
0x を付ける必要があります。
2 進数表記を使用する場合、数の前に 0b を付ける必要があります。
PHP 7.4.0 以降では、可読性を向上させるために整数リテラルの桁の間にアンダースコア
(_) を含めることができるようになりました。
アンダースコアは PHP の scanner が除去します。
例1 整数リテラル
<?php
$a = 1234; // 10進整数
$a = 0123; // 8進数 (10進数の83と等価)
$a = 0o123; // 8進数 (PHP 8.1.0 以降)
$a = 0x1A; // 16進数 (10進数の26と等価)
$a = 0b11111111; // 2進数 (10進数の255と等価)
$a = 1_234_567; // 10進数 (PHP 7.4.0 以降)
?>
PHP 8.1.0 以降で使用可能な整数リテラルの形式は以下のように定義されています。
(これより前のバージョンでは、8進数のプレフィックス 0o や 0O が許されませんでした。さらに、PHP 7.4.0 より前のバージョンでは、アンダースコアも許されませんでした)
decimal : [1-9][0-9]*(_[0-9]+)*
| 0
hexadecimal : 0[xX][0-9a-fA-F]+(_[0-9a-fA-F]+)*
octal : 0[oO]?[0-7]+(_[0-7]+)*
binary : 0[bB][01]+(_[01]+)*
integer : decimal
| hexadecimal
| octal
| binary
整数のサイズはプラットフォームに依存しますが、
約 20 億 (32 ビット符号付) が一般的な値です。
64 ビットプラットフォームでの通常の最大値は、およそ 9*10^18 (900京) になります。
PHP は符号無し整数をサポートしていません。
整数のサイズは定数 PHP_INT_SIZE で、
整数の最大値は定数 PHP_INT_MAX で、
整数の最小値は定数 PHP_INT_MIN で決まります。
int型の範囲外の数を指定した場合、かわりに floatとして解釈されます。また、結果が int型の範囲外の数となるような計算を行うと floatが代わりに返されます。
例2 32 ビットシステムにおける整数のオーバーフロー
<?php
$large_number = 2147483647;
var_dump($large_number); // int(2147483647)
$large_number = 2147483648;
var_dump($large_number); // float(2147483648)
$million = 1000000;
$large_number = 50000 * $million;
var_dump($large_number); // float(50000000000)
?>例3 64 ビットシステムにおける整数のオーバーフロー
<?php
$large_number = 9223372036854775807;
var_dump($large_number); // int(9223372036854775807)
$large_number = 9223372036854775808;
var_dump($large_number); // float(9.2233720368548E+18)
$million = 1000000;
$large_number = 50000000000000 * $million;
var_dump($large_number); // float(5.0E+19)
?>
PHP には整数の割り算を行う演算子はありません。
整数の割り算を行うには、intdiv() 関数を使って下さい。
1/2 は
float 型の 0.5 になります。
0 に近い方向の整数値に値を丸めるためにキャストを使用することができ、
また、round() 関数を使用することもできます。
<?php
var_dump(25/7); // float(3.5714285714286)
var_dump((int) (25/7)); // int(3)
var_dump(round(25/7)); // float(4)
?>
int に値を明示的に変換するには、キャスト
(int) または (integer)
のどちらかを使用してください。しかし、多くの場合、演算子、関数、制御構造が
int 引数を必要とする場合、値は自動的に変換されるため、
キャストを使用する必要はありません。
関数 intval() を用いて値を整数に変換することも可能です。
resource を int に変換すると、その結果は一意なリソース番号となります。 これは、その resource に対して PHP が実行時に割り当てた番号です。
型の相互変換 を参照ください。
false は、0 (ゼロ) となり、
true は、1 となります。
float から整数に変換する場合、その数はゼロのほうに丸められます。 PHP 8.1.0 以降では、精度を損なうことになる float から int への暗黙の変換は推奨されなくなり、警告が発生します。
<?php
function foo($value): int {
return $value;
}
var_dump(foo(8.1)); // PHP 8.1.0 以降では "Deprecated: Implicit conversion from float 8.1 to int loses precision"
var_dump(foo(8.1)); // PHP 8.1.0 より前のバージョンでは 8
var_dump(foo(8.0)); // PHP 8.1.0 より前でもあとでも、8
var_dump((int)8.1); // PHP 8.1.0 より前でもあとでも、8
var_dump(intval(8.1)); // PHP 8.1.0 より前でもあとでも、8
?>
float が整数の範囲 (通常は、32 ビットプラットフォームでは +/- 2.15e+9 =
2^31、64 ビットプラットフォームでは +/- 9.22e+18 = 2^63
) を越える場合、結果は undefined となります。これは、
その float が正しい整数の結果を得るために十分な精度を得られなかったからです。
この場合、警告も通知も発生しません!
注意:
NaN や無限大を int にキャストした結果は、常にゼロとなります。
未知の端数を int にキャストしないでください。 この場合、予期しない結果となることがあります。
<?php
echo (int) ( (0.1+0.7) * 10 ); // 7が出力されます!
?>より詳細な情報については、 float の精度に関する注意を参照ください。
文字列が
数値形式の文字列
の場合は、対応する整数値に解決されます。
そうでない場合は、ゼロ (0) に変換されます。
null は、常に0に変換されます。
整数への変換の動作は、他の型については定義されません。 現在の動作は、その値がまず 論理値に変換された 場合と同じです。しかし、この動作は予告なく変更されることがありえるので、 これを前提にしてはいけません。
A leading zero in a numeric literal means "this is octal". But don't be confused: a leading zero in a string does not. Thus:
$x = 0123; // 83
$y = "0123" + 0 // 123Here are some tricks to convert from a "dotted" IP address to a LONG int, and backwards. This is very useful because accessing an IP addy in a database table is very much faster if it's stored as a BIGINT rather than in characters.
IP to BIGINT:
<?php
$ipArr = explode('.',$_SERVER['REMOTE_ADDR']);
$ip = $ipArr[0] * 0x1000000
+ $ipArr[1] * 0x10000
+ $ipArr[2] * 0x100
+ $ipArr[3]
;
?>
IP as BIGINT read from db back to dotted form:
Keep in mind, PHP integer operators are INTEGER -- not long. Also, since there is no integer divide in PHP, we save a couple of S-L-O-W floor (<division>)'s by doing bitshifts. We must use floor(/) for $ipArr[0] because though $ipVal is stored as a long value, $ipVal >> 24 will operate on a truncated, integer value of $ipVal! $ipVint is, however, a nice integer, so
we can enjoy the bitshifts.
<?php
$ipVal = $row['client_IP'];
$ipArr = array(0 =>
floor( $ipVal / 0x1000000) );
$ipVint = $ipVal-($ipArr[0]*0x1000000); // for clarity
$ipArr[1] = ($ipVint & 0xFF0000) >> 16;
$ipArr[2] = ($ipVint & 0xFF00 ) >> 8;
$ipArr[3] = $ipVint & 0xFF;
$ipDotted = implode('.', $ipArr);
?>Integer literals may be decimal, octal, hexadecimal or binary, but integer values have single representation;
<?php
var_dump(010); // int(8) NOT int(010)
var_dump(0x10); // int(16) NOT int(0x10)
var_dump(0b10); // int(2) NOT int(0b10)
?>
This is the reason why casting integer to string gives us always a decimal:
<?php
var_dump((string) 010); // string(8) NOT string(010)
var_dump((string) 0x10); // string(16) NOT string(0x10)
var_dump((string) 0b10); // string(2) NOT string(0b10)
?>Be aware of float to int cast overflow
<?php
// You may expected these
var_dump(0x7fffffffffffffff); // int(9223372036854775807)
var_dump(0x7fffffffffffffff + 1); // float(9.2233720368548E+18)
var_dump((int)(0x7fffffffffffffff + 1)); // int(9223372036854775807)
var_dump(0x7fffffffffffffff + 1 > 0); // bool(true)
var_dump((int)(0x7fffffffffffffff + 1) > 0); // bool(true)
var_dump((int)'9223372036854775807'); // int(9223372036854775807)
var_dump(9223372036854775808); // float(9.2233720368548E+18)
var_dump((int)'9223372036854775808'); // int(9223372036854775807)
var_dump((int)9223372036854775808); // int(9223372036854775807)
// But actually, it likes these
var_dump(0x7fffffffffffffff); // int(9223372036854775807)
var_dump(0x7fffffffffffffff + 1); // float(9.2233720368548E+18)
var_dump((int)(0x7fffffffffffffff + 1)); // int(-9223372036854775808) <-----
var_dump(0x7fffffffffffffff + 1 > 0); // bool(true)
var_dump((int)(0x7fffffffffffffff + 1) > 0); // bool(false) <-----
var_dump((int)'9223372036854775807'); // int(9223372036854775807)
var_dump(9223372036854775808); // float(9.2233720368548E+18)
var_dump((int)'9223372036854775808'); // int(9223372036854775807)
var_dump((int)9223372036854775808); // int(-9223372036854775808) <-----
?>
These overflows are dangerous when you try to compare it with zero, or substract it from another value (e.g. money).-------------------------------------------------------------------------
Question :
var_dump((int) 010); //Output 8
var_dump((int) "010"); //output 10
First one is octal notation so the output is correct. But what about the when converting "010" to integer. it should be also output 8 ?
--------------------------------------------------------------------------
Answer :
Casting to an integer using (int) will always cast to the default base, which is 10.
Casting a string to a number this way does not take into account the many ways of formatting an integer value in PHP (leading zero for base 8, leading "0x" for base 16, leading "0b" for base 2). It will simply look at the first characters in a string and convert them to a base 10 integer. Leading zeroes will be stripped off because they have no meaning in numerical values, so you will end up with the decimal value 10 for (int)"010".
Converting an integer value between bases using (int)010 will take into account the various ways of formatting an integer. A leading zero like in 010 means the number is in octal notation, using (int)010 will convert it to the decimal value 8 in base 10.
This is similar to how you use 0x10 to write in hexadecimal (base 16) notation. Using (int)0x10 will convert that to the base 10 decimal value 16, whereas using (int)"0x10" will end up with the decimal value 0: since the "x" is not a numerical value, anything after that will be ignored.
If you want to interpret the string "010" as an octal value, you need to instruct PHP to do so. intval("010", 8) will interpret the number in base 8 instead of the default base 10, and you will end up with the decimal value 8. You could also use octdec("010") to convert the octal string to the decimal value 8. Another option is to use base_convert("010", 8, 10) to explicitly convert the number "010" from base 8 to base 10, however this function will return the string "8" instead of the integer 8.
Casting a string to an integer follows the same the logic used by the intval function:
Returns the integer value of var, using the specified base for the conversion (the default is base 10).
intval allows specifying a different base as the second argument, whereas a straight cast operation does not, so using (int) will always treat a string as being in base 10.
php > var_export((int) "010");
10
php > var_export(intval("010"));
10
php > var_export(intval("010", 8));
8"There is no integer division operator in PHP". But since PHP 7, there is the intdiv function.Converting to an integer works only if the input begins with a number
(int) "5txt" // will output the integer 5
(int) "before5txt" // will output the integer 0
(int) "53txt" // will output the integer 53
(int) "53txt534text" // will output the integer 53<?php
$ipArr = explode('.', $ipString);
$ipVal = ($ipArr[0] << 24)
+ ($ipArr[1] << 16)
+ ($ipArr[2] << 8)
+ $ipArr[3]
;
?>
1. the priority of bit op is lower than '+',so there should be brackets.
2. there is no unsighed int in PHP, if you use 32 bit version，the code above will get negative result when the first position of IP string greater than 127.
3. what the code actually do is calculate the integer value of transformed 32 binary bit from IP string.Be careful with using the modulo operation on big numbers, it will cast a float argument to an int and may return wrong results. For example:
<?php
$i = 6887129852;
echo "i=$i\n";
echo "i%36=".($i%36)."\n";
echo "alternative i%36=".($i-floor($i/36)*36)."\n";
?>
Will output:
i=6.88713E+009
i%36=-24
alternative i%36=20To force the correct usage of 32-bit unsigned integer in some functions, just add '+0' just before processing them.
for example
echo(dechex("2724838310"));
will print '7FFFFFFF'
but it should print 'A269BBA6'
When adding '+0' php will handle the 32bit unsigned integer
correctly
echo(dechex("2724838310"+0));
will print 'A269BBA6'Sometimes you need to parse an unsigned
32 bit integer. Here's a function I 've used:
function parse_unsigned_int($string) {
$x = (float)$string;
if ($x > (float)2147483647)
$x -= (float)"4294967296";
return (int)$x;
}On 64 bits machines max integer value is 0x7fffffffffffffff (9 223 372 036 854 775 807).d_n at NOSPAM dot Loryx dot com
13-Aug-2007 05:33
Here are some tricks to convert from a "dotted" IP address to a LONG int, and backwards. This is very useful because accessing an IP addy in a database table is very much faster if it's stored as a BIGINT rather than in characters.
IP to BIGINT:
<?php
$ipArr = explode('.',$_SERVER['REMOTE_ADDR']);
$ip = $ipArr[0] * 0x1000000
+ $ipArr[1] * 0x10000
+ $ipArr[2] * 0x100
+ $ipArr[3]
;
?>
This can be written in a bit more efficient way:
<?php
$ipArr = explode('.',$_SERVER['REMOTE_ADDR']);
$ip = $ipArr[0]<<24
+ $ipArr[1]<<16
+ $ipArr[2] <<8
+ $ipArr[3]
;
?>
shift is more cheaper.In response to the comment by me at troyswanson dot net:
-2147483648 falls into the range of 32 bit signed integers yet php treats it as a float. However, -2147483647-1 is treated as an integer.
The following code demonstrates:
<?php
var_dump(-2147483648); //float(-2147483648)
var_dump(-2147483647 - 1); //int(-2147483648)
?>
This is probably very similar to the MS C bug which also treats -2147483648 as an UNSIGNED because it thinks it's out of the range of a signed int.
The problem is that the parser does not view "-x" as a single token, but rather as two, "-" and "x". Since "x" is out of the range of an INT, it is promoted to float, even though in this unique case, "-x" is in the range of an int.
The best cure is probably to replace "-2147483648" with "0x80000000", as that is the hexadecimal equivalent of the same number.
Hope that helps explain what's going on
Peace
- Eric / fezPlease also note that the maximum stored in the integer depends on the platform / compilation; on windows xp 32 bits, the following value:
0x5468792130ABCDEF
echoes to:
6.0822444802213E+18 (cast to float)
On a fully 64 bits system, it echoes to:
6082244480221302255$e = 0x8000000000000000;
$e2 = 0b1000000000000000000000000000000000000000000000000000000000000000;
if ($e == $e2){
echo "e==e2<br>";
}else{
echo "e!=e2<br>";
}
pirnt "e!=e2"
----------------------------
echo decbin($e) . "<br>";
echo decbin($e2) . "<br>";
the result is :
1000000000000000000000000000000000000000000000000000000000000000
111111111111111111111111111111111111111111111111111110000000000PHP offers a slew of built-in functions and automatic type-casting routines which can get pretty complicated. But most of the time, you still have to take matters into your own hands and allow PHP to do its thing. In that case, and something that has NOT been mentioned, is how to construct your code. To keep things simple, I divide all my scripts in half. The top half gives my scripts the "capability" they need, and the lower half is the actual code to be "run" or "executed".
<?php
/*
* build the program's capability - define variables and functions...
*/
$item_label = ''; // type string
$item_price = 0.0; // type float
$item_qty = 1; // type integer
$item_total = 0.0; // type float - to set use calculate()
function calculate(){
global $item_price, $item_qty, $item_total;
$item_price = number_format($item_price, 2);
$item_total = number_format(($item_price * $item_qty), 2);
}
function itemToString() {
global $item_label, $item_price, $item_qty, $item_total;
return "$item_label [price=\$$item_price, qty=$item_qty, total=\$$item_total]";
}
/*
* run the program - set data, call methods...
*/
$item_label = "Coffee";
$item_price = 3.89;
$item_qty = 2;
calculate(); // set $item_total
echo itemToString(); // -> Coffee [price=$3.89, qty=2, total=$7.78]
$item_label = "Chicken";
$item_price = .80; // per lb.
$item_qty = 3.5; // lbs.
calculate(); // set $item_total
echo itemToString(); // -> Chicken [price=$0.80, qty=3.5, total=$2.80]
?>
Note: All type-casting is done by PHP's built-in number_format() method. This allows our program to enter any number (float or int) on item price or quantity in the runtime part of our script. Also, if we explicitly cast values to integer in the capability part of our script, then we start getting results that may not be desirable for this program. For example, if in the calculate method we cast item_qty to integer, then we can no longer sell chicken by the pound!Note that the soft-typing of numbers in PHP means that some things become very difficult. For example, efficiently emulating the more common linear congruential generators (LCGs) for fast, deterministic, pseudo-randomness. The naive code to create the next value in a sequence (for power-of-2 values of $m) is:
$seed = ($seed * $a + $c) % $m;
...where $m, $a, and $c are values and data types carefully chosen such that repeating this operation will eventually generate every value in the range $0 to $m, with no repetition.
I can find no good commonly used LCGs which use PHP-compatible values. The LCG values used in by rand() in systems like Borland Delphi, Virtual Pascal, MS Visual/Quick C/C++, VMS's MTH$RANDOM, old versions of glibc, Numerical Recipes, glibc, GCC, ANSI C, Watcom, Digital Mars, CodeWarrior, IBM VisualAge C/C++, java.util.Random, Newlib, MMX... *all* fail when ported, for one of two reasons, and sometimes both:
- In PHP on 32 bit machines and all Windows machines, $m = 2^32 or larger requires UInt or even UInt64, or the result becomes negative.
- Large $a multiplied by an integer seed gets converted to a float64, but the number can be too long for the 53-bit mantissa, and it drops the least significant digits... but the LCG code above requires that the most significant digits should be lost.
These are two classes of problem to beware of when porting integer math to PHP, and I see no clean and efficient way to avoid either one.
So if designing a cross-platform system that must work in PHP, you must select LCG values that fit the following criteria:
$m = 2^31 or less (PHP limitation). Recommend: 2^31.
$a = Less than 2^22 (PHP limitation); $a-1 divisible by all prime factors of $m; $a-1 divisible by 4 if $m is. Recommend: 1+(4*(any prime <= 1048573)).
$c = smaller than (2^53-($m*$a)) (PHP limitation); relatively prime with $m. Recommend: any prime <= 23622320123.Try this one instead:
function iplongtostring($ip)
{
$ip=floatval($ip); // otherwise it is capped at 127.255.255.255
$a=($ip>>24)&255;
$b=($ip>>16)&255;
$c=($ip>>8)&255;
$d=$ip&255;
return "$a.$b.$c.$d";
}