Floating point types (float, double, decimal) in C Sharp (C#) - Step-by-Step Execution

Concept Flow - Floating point types (float, double, decimal)

Declare variable with type

↓

Assign value (literal)

↓

Store value in memory

↓

Use variable in calculations

↓

Observe precision and range

↓

Output or further use

This flow shows how floating point variables are declared, assigned values, stored, used in calculations, and how their precision and range affect results.

Execution Sample

C Sharp (C#)

float f = 1.23456789f;
double d = 1.23456789012345;
decimal m = 1.2345678901234567890123456789m;
Console.WriteLine(f);
Console.WriteLine(d);
Console.WriteLine(m);

This code declares three floating point variables with different types and prints their values to show differences in precision.

Execution Table

Step	Action	Variable	Value Assigned	Precision/Notes	Output
1	Declare and assign float	f	1.23456789f	Approx. 7 digits precision
2	Declare and assign double	d	1.23456789012345	Approx. 15-16 digits precision
3	Declare and assign decimal	m	1.2345678901234567890123456789m	Approx. 28-29 digits precision
4	Print float value	f	1.234568	Rounded to 7 digits	1.234568
5	Print double value	d	1.23456789012345	Shows more digits	1.23456789012345
6	Print decimal value	m	1.2345678901234567890123456789	Full precision shown	1.2345678901234567890123456789
7	End of program

💡 Program ends after printing all three values showing their precision differences.

Variable Tracker

Variable	Start	After Assignment	Final
f	undefined	1.234568 (approx)	1.234568 (stored approx)
d	undefined	1.23456789012345	1.23456789012345
m	undefined	1.2345678901234567890123456789	1.2345678901234567890123456789

Key Moments - 3 Insights

Why does the float variable show fewer digits than the decimal when printed?

Float has about 7 digits of precision, so it rounds the value when stored and printed, as seen in execution_table rows 1 and 4.

Why do we add 'f', 'd', or 'm' after the number when assigning?

These suffixes tell the compiler which floating point type to use. Without them, the number defaults to double (for floating-point literals without suffix) or decimal (with 'm'), as shown in execution_table rows 1-3.

Can decimal store more precise values than double?

Yes, decimal stores about 28-29 digits of precision, more than double's 15-16 digits, which is why the decimal value prints fully in row 6.

Visual Quiz - 3 Questions

Look at the execution_table at step 4. What is the printed value of the float variable 'f'?

A 1.234568

B 1.23456789

C 1.23456789012345

D 1.2345678901234567890123456789

💡 Hint

Check the 'Output' column at step 4 in the execution_table.

At which step does the program assign the variable with the highest precision?

A Step 1 (float)

B Step 2 (double)

C Step 3 (decimal)

D Step 4 (print float)

💡 Hint

Look at the 'Precision/Notes' column in the execution_table for assignment steps.

If we remove the 'f' suffix from the float assignment, what will happen?

A The float will store the value correctly without suffix.

B The code will not compile because the literal is treated as double by default.

C The decimal type will be assigned instead.

D The program will print the same value.

💡 Hint

Refer to key_moments about suffixes and their role in type assignment.

Concept Snapshot

Floating point types in C#:
- float: 32-bit, ~7 digits precision, suffix 'f'
- double: 64-bit, ~15-16 digits precision, default for floating-point literals without suffix
- decimal: 128-bit, ~28-29 digits precision, suffix 'm'
Use suffixes to specify type explicitly.
Precision affects stored and printed values.

Full Transcript

This visual execution shows how floating point types float, double, and decimal work in C#. Variables are declared with their types and assigned values with suffixes to specify type. Float stores about 7 digits precision, double about 15-16, and decimal about 28-29 digits. When printed, float rounds the value, double shows more digits, and decimal shows full precision. Suffixes like 'f' for float and 'm' for decimal are necessary to tell the compiler the intended type. Removing suffixes can cause compilation errors or unintended types. This helps understand how precision and type affect floating point numbers in C#.