Maintenance script: Initial automated import

2016-02-24T18:24:35Z

Initial automated import

New page

{{Template:TI-BASIC:Command
|picture=INT.GIF
|summary=Rounds a value down to the nearest integer.
|syntax=int(''value'')
|location=Press:
# MATH to access the [[TI-BASIC:Math|Math]] menu.
# RIGHT to access the NUM submenu.
# 5 to select int(, or use arrows.
|compatibility=TI-83/84/+/SE
|size=1 byte
}}

int(''value'') is the [http://mathworld.wolfram.com/FloorFunction.html floor function]. It returns the greatest integer less than or equal to ''value''. Also works on complex numbers, lists and matrices.

int(5.32)
5
int(4/5)
0
int(‾5.32)
‾6
int(‾4/5)
‾1

The difference between [[TI-BASIC:Ipart|IPart(]] and int( is subtle, and many people aren't even aware of it, but it exists. Whereas iPart( always truncates its parameters, simply removing the integer part, int( always rounds down. This means that they return the same answers for positive numbers, but int( will return an answer 1 less than iPart( for (non-integer) negative numbers. For example, iPart(-5.32) is -5, while int(-5.32) is -6.

Most of the time, however, you're dealing with only positive numbers anyway. In this case, the decision to use iPart( or int( is mostly a matter of preference - some people only use int( because it is shorter, some people use iPart( when there is a corresponding [[TI-BASIC:Fpart|FPart(]] taken. However, see the Command Timings section.

= Advanced Uses =

int(, along with [[TI-BASIC:Ipart|IPart(]] and [[TI-BASIC:Fpart|FPart(]], can be used for integer [[TI-BASIC:Compression|Compression]].

= Command Timings =

The following table compares the speeds of int and [[TI-BASIC:Ipart|IPart(]]. Each command was timed over 2000 iterations to find a noticeable difference.

{| class="wikitable"
! Format !! Bars !! Pixels !! Total
|-
| iPart(1 || 10 || 1 || 81
|-
| iPart(1.643759 || 10 || 1 || 81
|-
| int(1 || 8 || 7 || 71
|-
| int(1.643759 || 10 || 2 || 82
|}

Conclusion: Unless there are 6 or more decimals, you should consider using int( because of its speed, but with a lot of decimals, iPart( stays the same so it goes faster.

= Related Commands =

* [[TI-BASIC:Ipart|IPart(]]
* [[TI-BASIC:Fpart|FPart(]]
* [[TI-BASIC:Round|Round(]]

= See Also =

* [[TI-BASIC:Compression|Compression]][[Category:TI-BASIC]]
[[Category:TIBD]]

TI-BASIC:Int - Revision history

Maintenance script: Initial automated import