6.2.4. Examining values

While the program is paused, we can view the value of any variable currently in the workspace. Examine values when we want to see whether a line of code has produced the expected result or not.

When a program is paused during debugging, it allows us to take a closer look at the current state of our variables. This is crucial because it helps us validate whether the code we're testing is working as intended. For example, if we suspect that a variable isn’t holding the correct value, we can check it while the program is paused.

Think of this like checking ingredients while you're cooking. If you're unsure if you added the right amount of salt to a dish, you can take a pause, taste the food, and adjust as needed before continuing.

If the result is as expected, step to the next line, and continue running. If the result is not as expected, then that line, or the previous line, contains an error.

After viewing a variable's value, you make a decision: if the value is correct, you proceed to the next line of the program, allowing it to keep executing. However, if the value is incorrect, it indicates that there may be a mistake in the current line or even the one before it, and it requires further inspection.

This is similar to solving a puzzle. If a piece doesn’t fit, you might look at the piece itself and the others surrounding it to determine where the mix-up is happening. You then correct it before moving on.

When we run a program, the current workspace is shown in the Stack field. Use who or whos to list the variables in the current workspace.

While debugging, understanding the context of your variables is vital. The workspace contains all the variables defined at that point in your program. Using commands like who or whos, you can list all active variables and their properties, allowing you to make informed decisions regarding what to examine or change.

Imagine trying to organize a closet while also keeping track of all the clothing items you have available. Knowing what’s in the closet (the workspace) helps you decide what to wear or what might need adjusting.

First, we position the cursor to the left of a variable on that line. Its current value appears. This is called a datatip, which is like a tooltip for data.

Datatips are a handy feature in the debugging process. By hovering over variables, you can instantly see their current values during execution. This provides a quick way to verify information without needing to type commands in the console.

Think of datatips as having an interactive label on a folder where you can see what’s inside without opening it. It provides you with valuable information instantly.

If you have trouble getting the datatip to appear, click in the line and then move the cursor next to the variable.

Sometimes, datatips may not show up as expected. In these cases, by clicking the line and adjusting your cursor's location, you can trigger the datatip to appear. This ensures you can access crucial variable information when needed.

This can be compared to trying to see a notification on your phone. If you tap the screen and reposition your finger, that alert may pop up, allowing you to check important details.

--