It is quite usual that simple decimal fractions like 0.1 or 0.7 cannot be converted into their internal binary counterparts without a little loss of precision.

See also type juggling.

Upon power on (a.k.a.

For values of other types, the conversion is the same as if the value would have been converted to integer and then to float.

It supports only a small number of atomic data structures such as boolean values, numbers (double precision floating point by default), and strings.

Floating point numbers

She has a heated swimming pool.

He has a heated swimming pool.

The boat was broken by the floating ice.

She has a heated swimming pool.

Is there a swimming pool near your house?

Is there a swimming pool near your house?

He has a heated swimming pool.

To the swimming pool!

The pool is empty.

I fully agree with your point of view.

In my language, the , is called comma, the is called semicolon, is called colon, ... are called ellipsis, and this sentence ends with a period.

Companies with a high percentage of floating rate debt stand to lose the most, Goldman said.

If the instructions inside the function are written with the assumption of receiving an integer value, but the calling code passed a floating point value, then the wrong result will be computed by the invoked function.

The swimming pool is open to the public.

I am going to the swimming pool.

I want a pool.

Let's go to the pool.

Where's the swimming pool?

I want a swimming pool.

I half agree with this view.

She dived into the swimming pool.

Tom dove into the pool.

Tom fell into the pool.

I am going to the swimming pool.

He has a swimming pool.

Tom fell in the swimming pool.

The pool is full of clean water.

I fell in the pool.

I fell in the pool.

She dived into the pool.

Everyone jumped into the pool.

Tom jumped into the pool.

We have a pool.

The children want to go to the pool.

Okay. Let's go to the pool.

Tom has a swimming pool.

Tom dove into the swimming pool.

We've got a pool.

She has a swimming pool.